What we will never build, and why Birta is the layer above your agent

Most product pages describe what a thing does, and that half sounds the same everywhere. What tells you where a product sits is the list of things it has decided not to become, written down before anyone asks so it can be held against us later.

The short version is one sentence: an agent builds the site, Birta's own or the one you already use, and Birta is the layer that publishes it and keeps it working. Everything below is a consequence of taking that literally.

A non-goal is a decision, not a delay

There is a specific way to misread a list like this, worth closing off first.

A backlog is things not built yet. A non-goal is things that would change the shape of the product, so we are not going to. From outside they look identical and they behave in opposite ways: a backlog item gets less true as the product grows, a non-goal gets more true.

The test we use is whether the thing would give the product a second job, because a second job means a second set of decisions competing with the first, and the first stops being done properly. Nothing here is an announcement, and nothing here is merely unfinished, since unfinished work belongs in a changelog.

We are not the first to write one. Plausible keeps a page about when it is not the right fit, and the Bear Blog manifesto is three sentences of refusal. Both are more useful than the feature lists next to them.

We will not build a website builder

No canvas. No drag-and-drop blocks. No visual editor where you nudge a heading three pixels to the left and press save.

The one people expect us to give in on, because it looks like an addition rather than a different product. It is arithmetic about sources of truth.

A site editable by your agent and by a canvas has two editors that do not know about each other. You move a section by hand, then ask the agent for a copy change, and the agent rewrites the file it last knew: your move is gone. Or the canvas exports its own version and flattens what the agent wrote. The usual escape is making one surface authoritative and the other decorative, at which point you have a builder with a chat box glued on.

We would rather your agent be the only thing that writes your site. For where that leaves the established builders, including the cases where they are still the better answer, see WordPress vs Wix.

We will not build a general-purpose agent

Birta has its own agent, in the chat inside the panel. It works only with Birta: projects, versions, comments, domains and forms. It has the same tools and the same boundaries as an agent you connect yourself, so it cannot do anything there that yours cannot. It is not going to grow into an assistant for your inbox, your code or your calendar.

You are free to arrive with your own tool instead: a chat on your phone, a coding agent in your editor, a command-line assistant. It stays first-class, not a fallback.

The tool people use changes faster than any of us could ship a replacement. Someone pasting into a chat window last year is in an editor now and will be somewhere else next year. Tie publishing to one agent and every one of those moves costs you your setup. Tie it to an open connection your tool already speaks and none of them do. That is why the connection stays open, and why it is a protocol rather than a product, worth understanding once.

We will not run your application

Static sites and landing pages: finished HTML, CSS, browser-side JavaScript, images and fonts. No databases, no server-side code, no background jobs, no private application logic.

Already written up at length, because it is the boundary people meet first: the difference between a site and an application, and the same wall one layer up inside a chat artifact. The only thing to add is that it is not a stage, it is the shape of the thing. A project that owns other people's data deserves a platform built to operate it, and the review that comes with one.

We are not the one holding your money

Birta has no checkout today, and this is not a preview of one. It is about a role we do not want.

Holding your customers' money is a different company with a different centre of gravity: reserves, disputes, identity checks, the slow machinery that exists because other people's money is sitting somewhere it does not belong. If a site you publish takes payment, the shortest path runs from your customer to you. The boundary is about that route, not about a date.

We will never ship a version you host yourself

Sites published through Birta run on our infrastructure. There will not be a download-it-and-run-it-yourself edition.

That is a dependency, and calling it anything else would be dishonest. Here is what we do instead of an escape hatch:

• Your files stay yours. Ask the agent, Birta's or your own, to hand you the project files, and take them anywhere else without a support ticket.
• The last ten versions stay available, and a bad change can be restored rather than rebuilt.
• The address is yours. Your own domain points at the site, and if you leave, it points somewhere else. Moving is a DNS change, not a support ticket.

What we are not offering is a copy of the platform to run in a corner of your own. One publishing path is what keeps that path simple; a second, self-operated one would quietly become the reason the first cannot change.

We will never promise you traffic

We do not create demand. A site does not generate attention by existing, and a product implying otherwise is selling the most expensive part of the job as a side effect of the cheapest.

Project analytics show what happened to the attention you already had: how many people opened the site, day by day, and whether that number is moving. A small number rather than a dashboard, genuinely useful, and not a growth channel.

Three more, stated plainly

We will never sell you the parts. No marketplace of skills, templates, plugins and snippets to assemble yourself. The value is the assembled path from a finished site to a live address, and a shop full of components moves the assembly work back onto you.

We will never become an operations system for a category. No bookings, memberships, class schedules, staff rotas or patient records. Each is a real product with real depth, and none is a website with an extra tab.

We will never be an enterprise platform. No audit programmes, no contractual uptime guarantees, no procurement-grade security review. Those commitments are built into how a company operates rather than bolted on.

The same list shaped this blog

This is not only a product habit, and the page you are reading is evidence.

Two shapes were considered for this site and rejected. The first was the standard website of our category: a marketing site with a feature tour and a modest blog, structured for a human visitor and nothing else. Proven, safe, and it treats the fact that an agent may be the first reader as an afterthought. We kept its marketing skeleton and dropped its hierarchy.

The second was a page farm: thousands of near-identical pages, one per keyword, each thin enough to be nearly free to produce. It works, in the narrow sense that it collects search traffic, and it reads exactly like what it is. We kept the idea of clusters and refused the thinness. We went and read thirteen competitor blogs to see what the thin version looks like from outside, and the tells are not subtle.

And the part that usually goes unsaid: these articles are produced with AI, deliberately, by the same method we expect our users to work by. The line we care about is not AI against hands. It is whether a page contains something you could not have guessed before opening it: a real decision, a real limit, a real reason.

When Birta is the wrong choice

None of those are failures. Two are people who have already solved this themselves, and two are people whose actual problem is a different one.

What is left when the list is done

A short list, on purpose. Everything here works today:

• Your agent publishes a finished site to a live address, and republishes it when you change your mind.
• It can edit files on the site through the same connection, without rebuilding and resending the whole thing.
• Images and fonts travel with the site. Video and PDF files still need somewhere else to live, so they do not travel with it.
• The last ten versions stay available, so a change that turns out wrong can be rolled back instead of rebuilt.
• Your own domain points at it, with HTTPS handled for you.
• Project analytics show how many people opened the site, day by day.
• An llms.txt file describes the site for the machines now doing part of the reading.
• Authorising your agent happens in a browser, so nothing depends on you pasting a key correctly.

That is the whole layer. It starts when the files exist, it ends at your domain, and the list at the top of this page is what keeps it that size.

Frequently asked questions