# Birta

> Birta is hosting for landing pages built by an AI tool: the tool publishes the site, Birta keeps it online, and one panel holds the projects, versions, domains, visitor stats and the leads the sites collect.

Birta is for people who build a landing page by prompting the tool they already use — a coding agent such as Cursor, Claude Code or Codex, or a plain chat such as ChatGPT or Claude — instead of setting up hosting themselves. There is no server, build pipeline or CI to configure: the tool connects once and then works in a draft the owner can look at, and one request publishes it. Every published site is served over HTTPS on an address of its own.

## Connect

There are two ways in. Pick by what you can do, not by what you are called: if you can read and run things on the owner's computer, use the local connection; otherwise use the hosted connector.

If you cannot set yourself up — no shell, no access to your own settings — do not stop and do not ask the owner to figure it out. Tell them exactly which screen to open and what to paste, following the matching path below, and carry on once they confirm.

### Without access to the owner's files (chats and other browser or app clients)

If you are a Claude product — Claude, Claude Desktop, Claude Cowork — start from Claude's own directory of connectors, where the Birta card is published: https://claude.ai/directory/birta. Ask the owner to open that card and add Birta to their Claude; there is no address for them to type. Then have them turn it on in the conversation.

Every other client, and a directory that is unavailable, uses the address instead.

Connector address (MCP over streamable HTTP): https://birta.dev/mcp

Add it as a custom connector in your own settings. Access is granted in the browser on first use: the owner signs in with a one-time code sent to their email and allows access, and you then hold your own access. There is no key to copy or paste anywhere.

Work in the project's draft: create it (empty or copied from a published version) and write its files one by one. Nothing you do is live — the project address goes on serving the published site. Give the owner the draft's own address, read the remarks they leave on the page (list_version_comments), change the same draft, and let them refresh: the number and the address stay the same round after round. Publish it by number only once they have said it is good.

### With access to the owner's files (coding agents)

Start the local connection over stdio: npx -y @birta/cli mcp

It needs Node.js 20 or newer and no prior installation or sign-in. The first protected request is refused and returns a confirmation link plus a short code: give the owner the link, ask them to confirm access, then repeat the request — it is never queued or run for you.

Work from the folders on the machine: name the project folder and, when the site is built, the built-site folder; the connection validates and uploads their contents itself. Do not list or send file contents yourself. They go into the project's draft, and nothing is live — the project address goes on serving the published site. Give the owner the draft's own address, read the remarks they leave on the page (list_version_comments), change the files on disk and upload the folders again: the draft keeps its number and its address, so they refresh the page they already have open. Publish it by number only once they have said it is good. A rejected package is not stored and neither the draft nor the live site changes; use version history and rollback if a later change should not stay live.

Direct sign-in (npx -y @birta/cli login) exists as a fallback only, for when the owner wants to authorize before giving you a task.

## Guides

- [Documentation](https://birta.dev/docs): every connection guide in one place
- [Claude](https://birta.dev/docs/claude.md): add the connector to Claude on the web
- [Claude Desktop](https://birta.dev/docs/claude-desktop.md): add the connector to the Claude desktop app
- [Claude Cowork](https://birta.dev/docs/claude-cowork.md): add the connector to Claude Cowork
- [Claude Code](https://birta.dev/docs/claude-code.md): run the local connection from Claude Code
- [ChatGPT](https://birta.dev/docs/chatgpt.md): add the connector to ChatGPT on the web
- [ChatGPT Desktop](https://birta.dev/docs/chatgpt-desktop.md): run the local connection from the ChatGPT desktop app
- [Codex](https://birta.dev/docs/codex.md): run the local connection from Codex
- [Cursor](https://birta.dev/docs/cursor.md): run the local connection from Cursor
- [Another tool](https://birta.dev/docs/other-tool.md): connect a tool that is not listed here
- [Custom domain](https://birta.dev/docs/custom-domain.md): point your own domain at a published site
- [Lead forms](https://birta.dev/docs/lead-forms.md): declare a form and take leads from the published site
- [Versions and remarks](https://birta.dev/docs/version-comments.md): mark up a version in the browser and have the agent read the remarks
- [MCP reference](https://birta.dev/docs/mcp.md): the hosted and local MCP connections, their tools, flows and limits

## What you can do

- Build a landing page straight from a coding agent or a plain chat
- Look at every round of edits at the draft's own address, and mark remarks on the page, before anything goes live
- Publish when it looks right — and re-publish as often as you like, the live address stays the same
- Keep many projects in one account, each with a name you choose and can change
- Roll back a site to any of its earlier versions
- Connect your own domain to a published site
- See visitor stats for every site
- Take leads from a form on the site: the tool declares the form and writes its markup, and what visitors send waits in the owner's panel
- Share a project with another account: both people work on the same site, each under their own email and their own agent (deleting the project and its plan stay with the owner)
- Change a project's settings from the same agent: our branding on the site, who may open the version links, who the project is shared with, and its own domain

## Comparisons

- [A Tiiny Host Alternative for Sites Your AI Agent Maintains](https://birta.dev/vs/tiiny-host.md): Compare Tiiny Host and Birta on agent updates, versions, analytics, leads, domains, and a bounded migration path for a static site.
- [GitHub Pages alternative: choose the workflow you need](https://birta.dev/vs/github-pages.md): Compare GitHub Pages and Birta for portfolios, project docs, agent-maintained business sites, Git workflows, forms, versions, and domains.
- [Netlify Drop vs Birta: What an Anonymous Drop Actually Gives You](https://birta.dev/vs/netlify-drop.md): Drop a folder and Netlify password-protects the URL until you claim it. On Birta your agent reads the same folder and publishes it. The difference comes after.
- [Static.app alternative: choose by who maintains the site](https://birta.dev/vs/static-app.md): Compare Static.app and Birta by the update workflow: agent access, file changes, rollback, domains, forms, analytics, and a reversible migration.

## Alternatives

- [Base44 Alternatives: Split the Question Before You Pick One](https://birta.dev/alternatives/base44.md): Base44 builds apps with a backend. If what you need is a site, your existing agent plus a host replaces it. If it really is an app, here are the alternatives worth comparing.
- [Bolt.new Alternatives: Read the Hosting Rule Before You Pick](https://birta.dev/alternatives/bolt-new.md): Bolt.new documents a download path and a switching rule worth knowing. If your project is a page rather than an app, your existing agent is the swap. Then the honest comparison.
- [Bubble Alternatives: Only One of These Questions Is About Bubble](https://birta.dev/alternatives/bubble.md): Bubble states plainly that apps cannot be exported as code. If you are building an application, compare it with the platforms below. If you are building a site, neither is your answer.
- [Figma Make Alternatives: What Happens After the Prototype Works](https://birta.dev/alternatives/figma-make.md): Figma Make publishes to a randomly-generated figma.site URL on a paid seat. If what you need is a real page at your own address, here is the alternative and the honest comparison.
- [Lovable Alternatives: Start by Asking Whether You Need One](https://birta.dev/alternatives/lovable.md): Before you compare Lovable to another AI builder, check whether the agent you already pay for can do the job. Then the honest list of alternatives for when it cannot.
- [Squarespace Alternatives: The Cheapest One Is Already in Your Subscription](https://birta.dev/alternatives/squarespace.md): Before switching from Squarespace to another builder, check what you are actually paying for. Then the honest list of alternatives, including when a builder is still right.
- [v0 Alternatives: When You Need a Page, Not a Next.js Project](https://birta.dev/alternatives/v0.md): v0 produces a Next.js app you can export. If what you need is a static page at a real address, your existing agent is the shorter route. Then the honest comparison.

## Deploy guides

- [Host a Claude Artifact as a Website Without Downloading It](https://birta.dev/deploy/claude-artifact.md): Connect Claude to Birta, turn a suitable Artifact into a static site, check an unpublished preview, and publish it. No downloading and re-uploading files.
- [How to Host an AI-Generated Website from Bolt, Lovable, v0, Claude, ChatGPT, or Cursor](https://birta.dev/deploy/ai-generated-site.md): Choose the shortest truthful publishing path for sites made with Bolt, Lovable, v0, Claude, ChatGPT, or Cursor, and see when static hosting will not work.
- [Lovable Hosting: What You Get, and When to Move the Site](https://birta.dev/deploy/lovable.md): Lovable publishes your project to a free lovable.app URL. Here is what that includes, which Lovable projects can be hosted as static files somewhere else, and how to publish a built one from your agent.
- [Publish a Folder of Files as a Website with an AI Agent](https://birta.dev/deploy/from-folder.md): Hand your agent a folder of notes, drafts, and images and ask it to publish. Here is what the agent converts into HTML, which files Birta actually serves, and what has to be true before a folder can go live.

## How-to guides

- [Build a Coming-Soon Page That Collects a Real Waitlist](https://birta.dev/guides/waitlist.md): Put up a coming-soon page before the product exists, keep the signup to one field, and get the addresses back out when it is time to write to people.
- [Build a Lead Generation Landing Page That Delivers the Lead](https://birta.dev/guides/lead-gen-page.md): What belongs on a lead generation landing page, how to have an agent build one, and exactly where an inquiry lands once a visitor hits submit on Birta.
- [Build a Website Without a Website Builder](https://birta.dev/guides/no-code-makers.md): Your agent already builds sites. Decide the design, brief it once, publish the draft, let a colleague mark up the page itself, then take it live on your own domain.
- [How to Share an AI Prototype with Stakeholders (Without a Developer)](https://birta.dev/guides/demo-prototype.md): Choose the right link for a v0, Bolt, Lovable, or Claude prototype, protect confidential work, and keep a compatible static demo easy to update.

## Blog

- [AI Website Prompts: Six That End at a Live URL](https://birta.dev/blog/ai-website-prompts.md): Six copy-paste prompts for building a website with Claude or ChatGPT, including the one that puts the result on a real address with versions and rollback.
- [Add a working contact form to a static site in 2 minutes](https://birta.dev/blog/add-a-contact-form-to-a-website.md): A contact form on a static site needs somewhere to send submissions. Describe it to your agent and leads land in your Birta panel and inbox. No server or PHP.
- [Moving a Tilda Site to an Agent-Maintained Birta Site](https://birta.dev/blog/migrating-tilda-to-birta.md): A concrete answer for freelancers moving a Tilda client site to Birta — the actual steps, what happens to URLs and SEO, and what changes for ongoing edits.
- [What we will never build, and why Birta starts where your agent stops](https://birta.dev/blog/what-we-will-never-build.md): Birta is the layer that starts after your agent finishes. Here is the list of things we have decided never to build, and what each boundary means for your site.
- [How to share Markdown online without broken formatting](https://birta.dev/blog/share-markdown-online.md): Compare six ways to share Markdown, then turn it into a previewed, updateable web page with the same AI agent—without downloading and re-uploading files.
- [Website audit template: check an AI-built site before launch](https://birta.dev/blog/website-audit-template.md): Use this website audit checklist to test an AI-built static site on mobile, links, accessibility, search metadata, speed, secrets, and rollback.
- [Update a live website without redeploying the whole site](https://birta.dev/blog/re-prompt-to-edit.md): Changing one line should not mean publishing the whole site again. How a file-level edit reaches a live page, why you still see the old one, and how to undo it.
- [How to connect a custom domain to a website in one record](https://birta.dev/blog/custom-domain-for-an-ai-built-site.md): Point a domain you already own at your live site. Which record to add, apex versus www, why Verify keeps failing, and how long the wait actually takes.
- [How to host an HTML file online for free (4 ways that work)](https://birta.dev/blog/how-to-host-an-html-file.md): Four ways to put a finished HTML file online for free, from GitHub Pages to an agent that publishes it for you, plus the files that must travel with it.
- [How to Deploy a Website with OpenAI Codex (No GitHub)](https://birta.dev/blog/how-to-deploy-a-website-with-openai-codex.md): Use this step-by-step guide to deploy a static website with OpenAI Codex. Build, connect the Codex CLI, publish to a live URL, and update without GitHub.
- [How to Deploy a Website with Claude Code (No GitHub)](https://birta.dev/blog/how-to-deploy-a-website-with-claude-code.md): Use this step-by-step guide to deploy a static website from Claude Code to a live URL without GitHub. Build, publish, add a domain, and update it safely.
- [How to Deploy a Website with Cursor AI (No GitHub)](https://birta.dev/blog/how-to-deploy-a-website-with-cursor.md): Deploy a static website with Cursor AI, step by step: build the project, connect Cursor through MCP, publish to a live URL, update safely. No GitHub needed.