Write once. Get proof everywhere it goes.
Draft the idea once, tailor what each network needs, and get a separate result for every selected brand, client, or location account.
Our spring collection lands this Thursday. Three new colorways, same everyday carry — early access opens for the newsletter first.
Spring drop incoming — three new colorways hit the shelf Thursday. Newsletter readers get first pick.
Write once, tailor every voice.
The core message stays one draft. Captions, tags & first comments adapt per network — with live previews & each platform’s real limits enforced before you hit schedule.
- Per-network caption variants
- Media rules checked before scheduling
- First comments & platform settings
What it does today.
These are working parts of Publishly, not roadmap promises.
Every format in one draft
Compose images, video, carousels & per-network captions in one draft. First comments, thumbnails & platform settings appear only where a network supports them.
- 1 draft, 10 possible destinations
- Controls gated by network capability
No failures the composer could foresee
Character limits, attachment counts, MIME types, file sizes & provider settings are checked before a job ever enters the schedule.
- Checked against each provider’s real limits
- Problems surface before anything queues
Each destination delivers on its own
Each selected account gets its own result. A failed network retries alone while the rest stay published.
- Honest failure reporting
- Conservative retries, never blind re-posts
The same reliability everywhere.
No matter where a post starts, Publishly applies the same delivery checks, failure reasons, safe retries, and account protections.
Every post gets a delivery receipt
A post is only marked successful after Publishly confirms it is live. The receipt stores the result and the live link, separately for every account you chose.
Every failure gets a reason and an alert
You see what happened, what needs fixing, and whether Publishly will try again. Developers can send the same alert straight into their own software through a signed webhook.
Retries that never double-post
Short platform problems are retried safely. If Publishly cannot prove what happened, it stops and asks you to check instead of risking the same post appearing twice.
Expiring and disconnected accounts are caught early
Warnings start before a known connection expiry. If a connection dies, Publishly flags it, stops sending posts to that account, and keeps the rest of your calendar moving.
Tokens encrypted before they’re stored
Your social account credentials are locked with industry-standard authenticated encryption before they are stored.
Every connection through the platform’s own front door
Nine of the ten featured networks use the platform’s official connect and permission screens. Bluesky uses a separate app password you create and revoke inside Bluesky — never your account password. Publishly does not automate a browser login.
API keys you can limit and revoke
Give each key only the access it needs and revoke it at any time. A full key is shown once and is never stored in a form Publishly can reveal later.
An audit trail that answers questions
Team invitations, channel changes, key management & bulk operations are recorded per workspace — who, what, when, from where.
Client isolation by design
Workspaces keep every brand’s accounts, tokens, media & history separate — a client’s data leaves with them, cleanly.
The source, on offer
Built on the open-source Postiz engine (AGPL-3.0). The corresponding source of the running service is available to every user.
A post sent to six selected brand accounts gets six results. One can fail and retry while the other five stay published.
Connect an account and schedule one real post.
Keep the receipt. Start free with no credit card.