Im open-sourcing Bloomberry

A few days ago I joked that everyone talks about open-source GTM, so I might as well actually open-source the GTM.

So I did.

Bloomberry is going open source.

Not shutting down or abandoning the hosted product. The opposite. I put it back on a waitlist and I want to push both versions harder.

The split is simple:

bloomberry.ai

is the stable product.

Free. Pro. Teams. Enterprise.

We host it, maintain it, keep the integrations working and make sure you don’t have to spend your night debugging OAuth.

The repo is the playground.

Run it yourself. Fork it. Tear pieces out. Build on top of it.

Voice Memory. Company Brain. Signal-to-Post. Approvals. Publishing. MCP. The actual guts of what I’ve been building.

I’m opening the roadmap too.

What’s next. What needs work. What I’m thinking about. What contributors want to take on.

Think something should work differently? Open an issue.

Can make it better? Send the PR.

Build something I never would’ve thought of? Even better.

I’m finalizing the license now so the rules are clear before the repo goes live. Customer data, credentials, private profiles and internal production stuff obviously stay private.

The product itself doesn’t need to.

Because if somebody can clone the repo tomorrow and erase Bloomberry’s advantage, then the advantage wasn’t very good.

I’d rather compete on product, taste, distribution and how fast we learn.

So that’s the plan.

• Stable hosted product on one side.

• Open repo, public roadmap and contributors on the other.

Open-source GTM, literally.

And yes, maybe a little bit out of spite.

Actually, for sure out of spite.