Reliable publishing to every account you connect
A scheduler that misses a post is worthless. Health checks, automatic retries, failure alerts and per-network versions mean the post you approved is the post that goes live.
Built to publish on the first attempt, with a plan for the rest
Before a post leaves the queue we verify tokens, permissions and rate limits. If the platform still rejects it, the publisher retries with backoff and, only when it truly cannot go through, surfaces the reason with a one-click retry.
- Pre-flight health checks catch expired tokens and missing permissions
- Automatic retries with widening delays on transient failures
- Failed posts stay on the calendar in red, never vanish
Write once, formatted correctly for each channel
A Bluesky thread, a LinkedIn post and a Telegram announcement are different. The composer keeps a version per network, from character limits to links and media, so nothing looks pasted.
- Per-channel copy and media in one editor
- Character limits and link previews checked per network
- Direct API publishing to every connected account
Publishing built like infrastructure
Every capability here exists to make sure a post you approved actually reaches your audience, on time.
Health checks before every post
Tokens, permissions and rate limits are verified ahead of time, so a post never fails at the last second for a reason we could have caught.
Retries with backoff
A transient failure is retried automatically with a widening delay, instead of quietly dropping the post on the floor.
One-click republish
When a platform rejects a post for good, you get the reason and a single button to fix and send again. Nothing disappears silently.
Per-network formatting
Character limits, threads, link cards, images and alt text handled per channel, with a version per network from one composer.
Failure alerts
When a post cannot go out, the right people hear about it by email and webhook, with the reason attached, before anyone asks.
A calendar that never lies
Every post carries a live status: scheduled, publishing, published, retrying or failed. What you see is what actually happened.
Publish where your audience already is
Core channels: Bluesky, Mastodon, LinkedIn, Telegram and Discord (LinkedIn personal profiles). Connectors for Instagram professional accounts, Facebook Pages, YouTube and X are built; availability depends on provider access and configuration. Reddit requires written approval for customer publishing. TikTok, Pinterest, Threads and Google Business Profile are not available yet.
The Facebook Pages connector is built. Customer access depends on Meta permissions and deployment configuration.
The Instagram professional-account connector is built. Customer access depends on Meta approval and deployment configuration.
Threads
Threads publishing is coming soon. It arrives once Meta's app review passes; until then, use this guide to plan.
LinkedIn personal profiles are available. Company Page support is implemented, subject to the access granted to the app.
Bluesky
Bluesky publishing is live: schedule posts and threads from the same calendar as every other account.
X
The X connector is built and uses your workspace’s X app credentials. The planned $9/mo add-on is not available yet.
TikTok
TikTok publishing is coming soon. It arrives once TikTok's app review passes; until then, use this guide to plan.
YouTube
The YouTube connector is built. Customer access depends on Google permissions and deployment configuration.
Google My Business
Google Business Profile publishing is coming soon. It arrives once Google's app review passes.
Customer publishing requires Reddit’s written approval and is unavailable.
Telegram
Publish channel and group messages through your own Telegram bot.
Discord
Post announcements to your server channels through a Discord webhook.
Slack
Send messages through a Slack incoming webhook. Access depends on your workspace setup.
Pinterest publishing is coming soon. It arrives once Pinterest's app review passes; until then, use this guide to plan.
Dribbble
Publishing to Dribbble is coming soon.
Mastodon
Publish to your Mastodon account with an access token from your instance.
Whop
Publishing to Whop is coming soon.
Twitch
Publishing to Twitch is coming soon.
Skool
Publishing to Skool is coming soon.
Kick
Publishing to Kick is coming soon.
Warpcast
Publishing to Warpcast is coming soon.
VK
Publishing to VK is coming soon.
Lemmy
Publishing to Lemmy is coming soon.
MeWe
Publishing to MeWe is coming soon.
Nostr
Publishing to Nostr is coming soon.
Listmonk
Publishing to Listmonk is coming soon.
WordPress
Publishing to WordPress is coming soon.
Medium
Publishing to Medium is coming soon.
Hashnode
Publishing to Hashnode is coming soon.
Dev.to
Publishing to Dev.to is coming soon.
Reliable publishing pairs with a visual calendar and queue, approvals in collaboration, and reporting in analytics.
Questions about going live
What happens when a publish fails?
The publisher retries with backoff. If the platform still rejects the post, you get a notification with the reason and a one-click retry. Failed posts never disappear silently; they stay on the calendar with a red status.
Which platforms can I publish to?
Bluesky, Mastodon, LinkedIn, Telegram and Discord are the core channels, with LinkedIn personal profiles. Connectors for Instagram professional accounts, Facebook Pages, YouTube and X are built; availability depends on provider access and configuration. Reddit requires written approval for customer publishing. TikTok, Pinterest, Threads and Google Business Profile are not available yet.
Why is Reddit unavailable?
Reddit requires written approval before a commercial app can publish on behalf of customers. Its connector is not available for customer publishing yet.
Approve a week. We publish it, reliably.
Start a 7-day trial and watch your first week publish on your own channels, or book a walkthrough with the team building it.