Real platform numbers. No invented gaps.
Compare brand and client accounts using numbers the social networks actually provide. If a metric is unavailable, Publishly says so instead of estimating it.
Illustrative demo series sourced in the product from Meta Graph API. Thu Aug 6: 920; Fri Aug 7: 1,140; Sat Aug 8: 1,020; Sun Aug 9: 1,360; Mon Aug 10: 1,240; Tue Aug 11: 1,510; Wed Aug 12: 1,430.
Connect an account to replace this demo with its live provider data.
Numbers with their sources attached.
Every metric comes from an account you authorized. Publishly saves regular snapshots so useful history can outlast a platform’s short reporting window. Where a network reports nothing, the chart says so.
- Platform-reported values only
- Snapshot history per channel
- Gaps labelled, not filled in
What it does today.
These are working parts of Publishly, not roadmap promises.
Comparisons the data can support
Compare date ranges, platforms, accounts & best posts wherever provider data allows the comparison.
History beyond platform lookback windows
Refresh-time snapshots preserve history beyond short API lookback windows, where platform terms permit storage.
When a number is missing, it says so
Reach, saves, follower trends & other metrics read as unavailable when a connected platform doesn’t expose them.
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.
If a platform does not report a number, the dashboard does not invent one. Missing stays missing — labelled, never estimated.
Connect an account and schedule one real post.
Keep the receipt. Start free with no credit card.