Which platforms can it actually publish to?
Three, through the official APIs: your LinkedIn profile, your Facebook Pages, and the Instagram professional accounts linked to those Pages. Five more are one-click hand-offs — a LinkedIn Company Page, a Facebook profile, WhatsApp, X and Threads: Studio copies the finished post and opens the composer, you paste and press Post. That is eight destinations from a single draft. TikTok draft-to-inbox is built and waiting on its app credentials. There is no X, Threads, Bluesky, Mastodon or YouTube publisher, and we are not putting a date on one.
Does anything go out without me?
Only a post you scheduled yourself, at the minute you chose. Everything the engine produces is a draft: Pollinate drafts, auto-seed drafts, the generated package, the newsletter. Auto-seed is off for every brand until you switch it on, caps at four drafts per run, and seeds a given hit into a given brand once ever. The overnight run ships disabled with auto-publish set to false.
Is this safe for my accounts?
It is built to be. Publishing goes through each platform's own documented API, from an account you connected yourself, with permissions you granted and can revoke. There is no headless browser anywhere in the product and nothing logs in as you. We never automate actions against other people's accounts. Where a platform does not open an API, we stop at the Post button and hand you the composer rather than working around the rule. Nobody can promise a platform's decisions — but we build on the documented side and cut what does not fit there.
What does it cost?
Nothing, and there is nothing to pay with: no checkout, no card, no plan tier in the software. Publishing, scheduling, the calendar, quote cards, carousels, watermarks, Hits, the six-hourly refresh and every draft Pollinate or auto-seed creates all cost nothing to run, so they cost nothing to use. One thing will ever be metered — an AI rewrite of a post for another brand — and that meter is built but not switched on. The prices we intend to charge are on this page already, marked as planned.
Will it sound like me?
Your voice is measured, not described: length, how many hard figures, how many proper nouns, how you open and how you close, taken from your own published posts and handed to the writer as targets. A brand rewrite is grounded in the brief you wrote for that brand plus the last five posts that brand actually published — never a generic house voice. A new workspace starts neutral on purpose: nobody inherits somebody else's name, employer or audience.
Can it post the same thing twice?
We will not give you an absolute, so here is the mechanism. Studio claims the post atomically before it sends and writes down the platform's own share id the instant the platform accepts. A retry, a crash or two workers racing reconcile to 'already published' rather than sending again, and a destination that already went is skipped. Where the outcome was ambiguous — a timeout, a 5xx — the scheduler deliberately does not retry, because the platform may already have committed the share.
What can I do on day one, and what needs history?
Writing and publishing work immediately: draft, tick your destinations, publish or schedule. Hits and Pollinate need results to read. A brand needs at least three published publications on a platform before Studio will rank it, because below that there is no honest median — and it says 'too few to rank' instead of inventing a position. Facebook and Instagram counts arrive by themselves every six hours; LinkedIn counts come from your own posts through the Studio browser extension.
How do I sign in?
Today, with Facebook. The Google, Microsoft and email buttons are built and appear the moment this server is configured for them — the sign-in page states which are available rather than offering a button that fails. If two sign-ins end up belonging to you, they land in the same account only when the provider says the email is verified; an unverified address never links and never creates.
Exactly which permissions do you ask for?
LinkedIn: openid, profile, email and w_member_social — sign in, and post as you. Facebook and Instagram ride one connection and ask for six: pages_show_list, pages_manage_posts, pages_read_engagement, business_management, instagram_basic and instagram_content_publish. That is the whole list. Nothing reads your inbox, your friends or anyone else's account.
I run accounts for other people. Is that actually separated?
Separation is in the database, not in the application: twenty-seven tables carry row-level security with FORCE on, and every /api request resolves to one workspace at a single chokepoint that fails closed — unresolved means 401, never a default tenant. Each workspace holds its own LinkedIn and Facebook tokens with no fallback to anyone else's. Setting up an extra workspace is still an operator step we do with you, not a button you press.