Reply from one place where the network allows it.
Bring supported Facebook and Instagram comments into one place and reply as the account you authorized. Unsupported networks say so clearly.
Do these ship to the EU?
Is there a tutorial for this?
Reply as the account that was addressed.
Comments from supported accounts arrive in one feed. Replies leave through the same authorized Facebook or Instagram connection.
- Comments kept inside the right workspace
- Replies through official permissions
- Unsupported networks say so
What it does today.
These are working parts of Publishly, not roadmap promises.
Every supported comment in one feed
Filter supported comments by connected account and platform in one inbox.
Replies leave as the authorized account
Facebook & Instagram adapters send replies through their official Graph API permissions — the same authorization that connected the account.
Only real controls, per network
Networks without an implemented comments API read as unavailable rather than showing a control that cannot work.
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.
No scraped inboxes, no ghost sessions. Where a network offers no comments API, the inbox says so instead of faking a control.
Connect an account and schedule one real post.
Keep the receipt. Start free with no credit card.