Publish prepared content without breaking each channel's rules.

RostrumPost turns prepared text and media into native variants, checks every platform, and publishes only where the connection allows.

Start free Read the API

Every connector is built. None of them pretends to be ready.

Connector built Provider gate pending

All seven are implemented against the real platform APIs, and every one stays fail-closed until its own app, permission, and canary gates clear. Prepare, preflight, and schedule the whole flow today on safe mock providers.

X 280 chars · text, media Built Canary pending
LinkedIn text, image Built Canary pending
Facebook Pages text, image, Reel · review-gated Built Review pending
YouTube Shorts video upload Built Direct
Threads text, image · review-gated Built Review pending
Instagram 2200 chars · image, Reel Built Review pending
TikTok video · draft or Direct Post Built Review pending
Shown upfront
no surprise failures

From one source to published, in four steps.

The same path whether a person clicks through it or an agent drives it over the API.

1

Source

Bring prepared text and media, or pull from your content studio over the API.

text, media, API

2

Native variants

RostrumPost adapts the message to each platform's format, length, and media rules.

per channel

3

Preflight

Every variant is checked for length, media, duplicates, and connection capability.

before publish

4

Publish or schedule

Publish where the connection allows, schedule the rest, hand off the assisted ones.

direct, scheduled, assisted

Preflight

Know before you publish.

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.

Length and title limits

Captions and titles are validated against each platform's limits before they reach the queue.

Media readiness

Required media, formats, and video for Shorts are confirmed, not assumed.

Connection capability

Direct, assisted, or pending platform review is shown per channel, so nothing fails by surprise.

Duplicates and account limits

Duplicate content and one-account-per-platform limits become actions, not errors after the fact.

Transport ready, rollout pending

X transport ready; app, balance, and canary pending
LinkedIn transport ready; app and canary pending
Bluesky transport ready; controlled account and canary pending

Needs a fix

YouTube Shorts attach a video to continue
Instagram waiting on platform review

Native finish

Threads prepared here, finish in the app

Approvals without the back and forth.

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.

Public link, no login

Reviewers open one URL and see the real per-platform variants.

Superseded on edit

Editing a variant marks the previous approval as superseded automatically.

app.rostrumpost.com/approval/9f3a8c2
X variant · draft

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.

Agents propose. Humans approve.

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 cli 
$ rostrum post --caption "Launch copy" --platforms x,linkedin
> preflight: 2 transport-ready, customer canary pending
> variants ready: x, linkedin

$ rostrum publish preview <variant_id>
> status: ready
> requires scopes: jobs:write + publish:write
> awaiting human confirmation

Scoped keys

Grant only the scopes a workflow needs, from read-only to publish.

Draft-only mode

Agents can compose and preflight without the ability to publish.

Approval required

Gate publishing behind human approval per workspace.

Audit log

Every key, run, and mutation is recorded and exportable.

A calendar that behaves like a queue.

Scheduled, published, failed, and needs-native-finish are distinct states, not one ambiguous status. Filter, retry, reschedule, or cancel in bulk.

Mon
09:00
Tue
sent
14:30
Wed
finish
Thu
retry
YouTube 18:00
Fri
11:15
Sat
Sun
sent
Scheduled Published Needs native finish Failed, ready to retry
Pricing

Plans that match real usage.

Start on a free local workspace with safe mock providers. Move to a paid plan when you connect real channels and publish at volume.

Starter

For solo founders

Freeto start

Preflight, approvals, and controlled provider rollout for one workspace.

  • YouTube, X, and LinkedIn direct-activation lane with readiness gates
  • Preflight and variant repair
  • Calendar and queue
  • API and CLI access
Start free
Growth

For active teams

Freeto start

Assisted handoff, approvals, and higher limits.

  • Everything in Starter
  • Instagram, Facebook, Threads, and TikTok external-review gates
  • Approvals and public portal
  • Webhooks and analytics sync
Start free
Agency

For client work

Freeto start

Multiple client workspaces and scoped agent access.

  • Everything in Growth
  • Multiple client workspaces
  • Agent keys with scoped access
  • Audit log export
Start free

Straight answers about platform limits.

Can RostrumPost publish to every platform automatically?
RostrumPost requests public distribution for new publications and never treats a private fallback as success. The core launch covers Instagram, Facebook Pages, Threads, TikTok, YouTube, X, and LinkedIn member profiles. Each destination must pass its own app, permission, approval, external-user, and public-receipt gates. Preflight shows the exact blocker before anything is sent.
What does assisted handoff mean?
The native variant is built and validated here, then you complete the final step in the platform when its API does not allow direct publishing. Nothing fails silently in the queue.
Are my platform credentials stored safely?
Credentials live in an encrypted vault, and external publishing stays off until you enable it per provider. By default the product runs with safe mock providers, so you can try the full flow without sending anything live.
Can I drive RostrumPost from code or an agent?
Yes. The REST API, CLI, MCP server, and agent Skill share one scoped authorization model, with draft-only keys and approval gates. Publishing and scheduling require explicit scopes plus human confirmation.
Is there a free way to try it?
Yes. Run a local workspace with mock providers at no cost, connect a real channel when you are ready, and move to a paid plan when you publish at volume.

Publish with fewer surprises.

Turn prepared content into native variants, preflight every channel, and publish only where the connection allows.

Start free Read the API