Source
Bring prepared text and media, or pull from your content studio over the API.
text, media, API
RostrumPost turns prepared text and media into native variants, checks every platform, and publishes only where the connection allows.
The same path whether a person clicks through it or an agent drives it over the API.
Bring prepared text and media, or pull from your content studio over the API.
text, media, API
RostrumPost adapts the message to each platform's format, length, and media rules.
per channel
Every variant is checked for length, media, duplicates, and connection capability.
before publish
Publish where the connection allows, schedule the rest, hand off the assisted ones.
direct, scheduled, assisted
Most tools let you queue a post and find out it failed later. RostrumPost checks each platform's real requirements first, then shows what is ready, what needs a fix, and what needs a native finish.
Captions and titles are validated against each platform's limits before they reach the queue.
Required media, formats, and video for Shorts are confirmed, not assumed.
Direct, assisted, or pending platform review is shown per channel, so nothing fails by surprise.
Duplicate content and one-account-per-platform limits become actions, not errors after the fact.
Ready
Needs a fix
Native finish
Send a public approval link to a client or teammate. They review the exact native variants, approve or request changes, and the record stays in sync with internal review.
Reviewers open one URL and see the real per-platform variants.
Editing a variant marks the previous approval as superseded automatically.
New release notes are live. Prepared once, adapted per channel, checked before anything goes out. Which platform would you adapt first?
Internal review and the public portal share one record.
A REST API, a CLI, an MCP server, and an agent Skill share one authorization model. Give an agent a draft-only key, require approval before anything publishes, and read every action in the audit log.
$ rostrum post --caption "Launch copy" --platforms x,linkedin
> preflight: 2 direct, 0 blocking
> variants ready: x, linkedin
$ rostrum publish preview <variant_id>
> status: ready
> requires scopes: jobs:write + publish:write
> awaiting human confirmation
Grant only the scopes a workflow needs, from read-only to publish.
Agents can compose and preflight without the ability to publish.
Gate publishing behind human approval per workspace.
Every key, run, and mutation is recorded and exportable.
Scheduled, published, failed, and needs-native-finish are distinct states, not one ambiguous status. Filter, retry, reschedule, or cancel in bulk.
Start on a free local workspace with safe mock providers. Move to a paid plan when you connect real channels and publish at volume.
Direct publishing and preflight for one workspace.
Assisted handoff, approvals, and higher limits.
Multiple client workspaces and scoped agent access.
Turn prepared content into native variants, preflight every channel, and publish only where the connection allows.