Why we're building Bailey in the open
We're building a governed publishing platform out loud — shipping notes, dead ends, and the decisions behind them. Here's why, and what you can expect from this blog.
There’s a quiet problem hiding inside the AI boom. People are making real things — a landing page, a booking form, a little tool — by asking an assistant to build it. And then they get stuck on the least interesting part: putting it online. Hosting, domains, “where does the form data go,” “is this even safe to collect emails on.” The creative part took five minutes. The plumbing takes a weekend, or never happens at all.
Bailey exists to delete that weekend. Connect your AI assistant once, then just ask — “publish this,” “take it down,” “who signed up?” — and it’s live at an address that’s yours. You never leave the chat.
But “easy to publish” isn’t the whole story, and if it were, we wouldn’t bother writing about it. The thing we actually care about is what happens after you hit publish.
The part nobody talks about: the data
The moment your page collects anything — an email, a booking, a message — you’ve taken on a responsibility most no-code tools quietly hand right back to you. Where does that data live? Who can read it? Can you delete it in one click when someone asks? Is it leaking into a dozen third-party scripts you never chose?
This is the “Shadow AI” problem in miniature: tools that make it easy to start collecting data and impossible to govern it. We’re building the opposite. With Bailey, the data your site collects stays bounded, auditable, and killable in one click. A site can never read another site’s data. Personal data has to declare why it’s being collected, or it doesn’t get published. The governance isn’t a feature you turn on — it’s the floor.
That’s the bet: the easy publishing loop is the scaffolding; the governed data plane is the point.
Why write all this down
Two reasons.
First, building in public keeps us honest. When you commit to explaining a decision out loud, you find out fast whether it actually holds up. Half the value of these posts is the ones we’ll have to rewrite.
Second, the people we’re building for deserve to understand what they’re standing on. Not a 40-page security whitepaper — a clear, human explanation of where your data goes and why you can trust the answer. If we can’t explain it simply, we haven’t earned your data.
What you’ll find here
- Build in public — the messy middle. What we shipped, what we killed, and the trade-offs behind both.
- Release notes — what’s new, in plain language, with the why attached.
- Deep dives — how the governed data plane actually works, for the curious and the skeptical.
- Showcase — real sites people put online just by asking, and how they did it.
We’re early. The product is moving fast, some of these posts will age like milk, and that’s fine — that’s the deal with building in the open.
Oh, and this blog? It’s published with Bailey. Of course it is.