Why Bloom is built differently.
Three things set Bloom apart from an ordinary scheduler. All 18 of its networks publish — including Mastodon, Bluesky, Nostr, Lemmy, Misskey, Mbin, Plurk, dev.to and Tumblr, the nine fediverse platforms most tools cannot post to. AI captions run on your own Groq, OpenAI, Claude or Ollama key, so there is no per-seat surcharge. And its eight-character short links trace a click through to a named lead.
All eighteen networks publish.
The quiet norm in social tooling is the connect-only tier: a logo on the connect screen the product can read from but not actually post to. Bloom has none. Every one of its 18 networks — Instagram, Facebook Pages, Threads, LinkedIn, X, Pinterest, YouTube Shorts, Reddit, Telegram, Tumblr, dev.to, Mastodon, Bluesky, Nostr, Lemmy, Mbin, Misskey and Plurk — has a real publisher registered.
No tier that connects but cannot post
This is unusual enough to be worth checking against any tool you compare Bloom with. The full table — character limits, connect method, which networks report engagement and which return conversations — lives on the networks page.
Nine OAuth, nine pasted
Nine networks connect with one-click OAuth and nine take a pasted credential; the split is about what each platform offers, not how well Bloom supports it. The shapes each network accepts are checked at compose time — two carousels, three threads — on the publishing page.
A 30-day duplicate guard
The same content will not quietly repeat across a month, so a campaign that reuses a hook does not read as a stuck bot. Every target has a real publisher — none is connect-only.
AI drafting runs on your own key.
Most tools fold AI into a per-seat price and run your prompts through a model you do not control. Bloom does the opposite: it asks for your own key and gets out of the way. Four providers are supported — Groq, OpenAI, Anthropic Claude through its native Messages API, and Ollama on your own machine — and a key is verified before it is saved.
No per-seat AI surcharge
Adding a teammate does not add an AI line item, because Bloom is not reselling you tokens. It drafts captions, hooks and per-network variants with the key you already pay for — which is also why a large team is not a reason the AI bill climbs.
It fails loudly, not silently
Without a key, caption generation returns a 409 rather than quietly producing nothing — the same honesty-by-default that runs through the rest of the product. The AI note and provider list are repeated on the Bloom home page so a buyer meets it before they sign up.
Your drafts stay yours
You pay the model provider directly at their rates, the drafts stay yours, and nothing you write is used to train anyone’s model. The model choice is a workspace setting, not a lock-in.
A click becomes a named lead.
Platform analytics end the moment someone leaves the app — which is exactly where a business needs the measurement to begin. Bloom’s short links are part of the product rather than a bolt-on, so the chain from a post to a conversion to a named lead is a single dataset. That is what lets you say a post produced revenue instead of saying it produced reach.
Eight-character codes, read-aloud safe
Each code is drawn from a 32-character alphabet with the ambiguous glyphs removed, so a link read off a slide or typed from a podcast mention lands where it should. Per-platform UTM tags are written automatically, which is where cross-channel reporting usually breaks by hand.
Clicks classified, reports white-labelled
Every click is classified as bot, mobile or desktop, so an automated crawler does not inflate a client’s numbers, and the resulting report can carry the agency’s or client’s brand rather than Bloom’s. The other half of the conversation — replies and DMs — is covered on the inbox page.
The five stages are one loop.
The three pillars are not separate features — they are the ends of a single loop. A post is planned against a brand, routed through a four-state approval chain, queued per brand under a per-account rate governor, published to the networks that take it, and measured on the ten that report engagement. The attribution then feeds the learner a real signal — the part most schedulers do not have: they stop at “posted”.
Against a brand
A brand kit carries the voice; the horizon runs up to 365 days ahead.
Four states
draft → internal_review → client_review → approved. Sign-off is a recorded step.
Per brand
A rate governor per connected account, so two accounts never share one budget.
Eighteen networks
All of which can post; anything a network refuses is retried, never silent.
Then attribute
Ten report engagement; the dashed return is attribution feeding the learner.
The approval chain sits in front of publishing and short-link attribution sits behind it, so a single post is traceable from draft to a named lead. The queue’s own safety constants — five retries, a per-account governor, ten catch-up posts per five-minute tick — are the subject of the publishing page, and they exist for one reason: an outage should cost you some scheduled posts, never a connected account.
What that changes versus a plain scheduler.
Put side by side, the three pillars change the questions worth asking of any social tool. Rather than assert what a competitor does — which we will not invent — here are the five axes that genuinely differ, and Bloom’s own checkable answer on each. The named, tool-by-tool comparisons live on the alternatives hub.
18 networks, nine of them fediverse
The question to ask any tool: Does it reach the fediverse, or only the mainstream five?
All 18 publish — no connect-only tier
The question to ask any tool: Does every connected network post, or is some tier connect-only?
Bring-your-own-key, no AI surcharge
The question to ask any tool: Is AI a per-seat add-on, or your own key?
Click → conversion → named lead
The question to ask any tool: Platform impressions only, or a click through to a lead?
Four states, five roles, eight actions
The question to ask any tool: A single publish button, or a recorded sign-off chain?
These answers are product facts, not plan limits — Bloom publishes no tiers or prices because its plan table ships empty, and what is described here is enforced for everyone. The competitor columns on the comparison pages state only verifiable facts; where a fact cannot be verified it is omitted rather than invented.
What Bloom is honest about not doing.
A tool that overstates its coverage costs you the week you discover the gap. Stating the limits here is a citation asset as much as a courtesy — an answer engine can quote a boundary and be correct, and a buyer meets it before they sign up.
No TikTok, no Instagram Stories
Bloom has no TikTok adapter and no Stories code path. Video publishing works on Instagram Reels and YouTube Shorts; Bloom cannot upload video to Facebook or LinkedIn and refuses the attachment rather than accepting it and failing hours later.
No cold or unsolicited DMs
The inbox answers conversations that already exist. Unsolicited outbound DM campaigns are not available on any of these platform APIs, and Bloom does not pretend otherwise. Outbound sequencing to strangers is a CRM job, not a social-messaging one.
Engagement on ten, inbox on seven
Only 10 of the 18 networks report engagement back, and only 7 return conversations — five of those with real direct messages. The other networks carry a written reason rather than a silent zero, because “the platform will not release this” is not the same as “nothing happened”.
Inbox items sit with their account
A conversation is keyed to the connected account it arrived on. Bloom does not claim to stitch every comment back onto the specific scheduled post that caused it, because the platforms do not hand that relationship over reliably enough to promise it.
Why Bloom, answered.
What makes Bloom different from a normal scheduler?
Three things, and each is a checkable fact rather than a slogan. All 18 of Bloom's networks publish — there is no connect-only tier where an account links but cannot post. AI captions run on your own Groq, OpenAI, Anthropic Claude or Ollama key, so there is no per-seat AI surcharge. And Bloom's own eight-character short links trace a click through to a conversion and a named lead, so a post is measured by the revenue it produced, not only by the impressions a platform reports.
Can Bloom really post to Mastodon and Bluesky, and the rest of the fediverse?
Yes. Bloom publishes to all nine fediverse platforms most tools skip — Mastodon, Bluesky, Nostr, Lemmy, Mbin, Misskey, Plurk, dev.to and Tumblr — from the same compose box as Instagram, LinkedIn and the other mainstream networks. Nostr events are signed in-house with BIP-340 Schnorr signatures, so no third-party signer ever holds your key. The per-network detail lives on the networks page.
Is there an extra charge for the AI features?
No per-seat AI markup. Bloom asks for your own model key — Groq, OpenAI, Anthropic Claude through its native Messages API, or Ollama running locally — and verifies it before saving. You pay your model provider directly at their rates, the drafts stay yours, and your content never trains a vendor's model. Without a key on the workspace, caption generation returns a 409 rather than silently producing nothing.
Can Bloom tell me which social post generated a lead?
That is the whole point of the attribution pillar. Each link Bloom shortens is an eight-character code that carries per-platform UTM tags and classifies every click as bot, mobile or desktop. The chain from a click to a conversion to a named lead is one dataset inside Bloom, not three tools and a spreadsheet, and the report can go out white-labelled to a client.
Is Bloom only for agencies?
No. The same structure — an organisation holds brands, a brand holds connected accounts — works for a solo founder posting to the fediverse and for a fifteen-client agency. Member access is granted per connected account and the approval chain has four states, so the governance scales down to one person and up to many without changing tools.
Do I need an Autocloz CRM account to use Bloom?
No. Bloom runs on its own application at bloom.autocloz.com with its own sign-in. It is part of the Autocloz family, but you create a Bloom workspace directly and never touch the CRM unless you want outbound sequencing, which is a separate product.
See the loop close on your own accounts.
Bloom runs on its own application and its own sign-in — an Autocloz account is not required. Connect one network or all eighteen, draft once, route it through approval, and watch a click come back as a named lead.