Prepare
Media is uploaded once and each destination gets its own settings. Nothing is shared between platforms by accident.
Most scheduling tools imply a certainty they do not have. Here is exactly what happens between the moment you queue a post and the moment a platform accepts it, including where it can go wrong.
Launch updates only. No spam. Privacy policy
Readiness runs per destination before anything is queued, so a platform rule blocks the post at the point you can still fix it.
Every destination is checked before you schedule, so a platform rule stops the post here rather than at the publish time you were counting on.
/w/[workspaceId]/composerPublishing through official APIs means a platform is always the final authority. The design decision here is to say so at every step.
Media is uploaded once and each destination gets its own settings. Nothing is shared between platforms by accident.
Every destination is validated: connection health, account eligibility, required choices, and media requirements.
A scheduled post holds a time and a set of settings. It is not a promise the platform will accept it at that time.
At the scheduled time Selfpost calls the platform and waits for confirmation. A post is only marked published once the platform says so.
Publishing is idempotent: a worker retrying after a failure uses stored state and platform identifiers to avoid publishing the same post twice.
Selfpost is not open for signups yet. Leave your address and we will email you the moment it is. Or walk the whole publishing flow right now in the demo, no account needed.
Launch updates only. No spam. Privacy policy