If you stop paying
Functions are stored, not lost: they answer 402 until the account is paying again. The database works for seven days, is then stopped, and is never deleted; you are pointed at transfer_database, which has no deadline.
Nothing to install. No second account.
Your AI built the site. We give it an address.
Tell your AI "put this site online", and you get back a link anyone can open.
On your phone? Connecting is done once, on a computer. Send yourself the guide for later.
Add it toClaude CodeCodexCursorVS CodeClaude Desktop, claude.aiChatGPT
Three steps, and you're online
- Step one
Ask for it in plain words
"Publish this site." Nothing to configure — your assistant is already holding the tools.
- Step two
You get a link that works
Files, server code and a Postgres database go up together. The reply is the address.
- Step three
Change it whenever
Ask for an edit and it goes live again. Every earlier version is kept.
Quick connect
Works with the assistant you already use
The simplest way: paste this line into your AI chat.
Fetch and execute the appropriate instructions to set me up for juudd from https://juudd.com/agent-setup/prompt.md
Or click through it yourself, with a picture of every screen:
Or add it by hand, app by app:
terminalclicktap to select, then copy
claude plugin marketplace add https://juudd.com/marketplace.json
claude plugin install juudd@juuddThe plugin adds the connector above and the rules its tools enforce, in one step.
~/.codex/config.tomlclicktap to select, then copy
[mcp_servers.juudd]
url = "https://mcp.juudd.com/mcp"then codex mcp login juudd
.cursor/mcp.jsonclicktap to select, then copy
Install in Cursor{
"mcpServers": { "juudd": { "url": "https://mcp.juudd.com/mcp" } }
}.vscode/mcp.jsonclicktap to select, then copy
Install in VS Code{
"servers": { "juudd": { "type": "http", "url": "https://mcp.juudd.com/mcp" } }
}With GitHub Copilot
settings
Customize → Connectors → Add, then paste the URL and keep what Claude detects.
Works on every Claude plan, Free included: Free allows one custom connector. A config file will not work for these.
settings, on the web
Turn on Developer mode in Settings → Security and login, then Plugins → + → New Plugin with the connector URL.
Pro, Plus, Business, Enterprise or Education, on the web. Measured end to end on 7 September 2026.
wherever it keeps servers
Add a remote MCP server over HTTP at the connector URL.
The server advertises its own authorization metadata, so there is no API key, no token and no header to set by hand.
A framework project has two doors: build it yourself and post the folder, or send the source and the platform builds it in a sandbox.
Five limits, stated before you build on it.
Straight answers- It will not install your dependencies
- It will not show what a function printed
- It will not delete anything
- It will not serve an apex domain everywhere
- It will not take a domain that is behind another CDN
Why each one
It will not install your dependencies
A build runs against a toolchain this platform pins, and a package.json naming anything outside it is refused with the whole list in the reply. What a build cannot produce becomes a function.
It will not show what a function printed
site_errors says which routes failed, when and how many times, not why. What a request returns is all you have to debug from, so write your functions to answer with what went wrong.
It will not delete anything
Every version you deploy stays, so a site can be replaced but never wiped clean. Taking one off the internet is a different thing and it is allowed: unpublish_site stops serving it, and keeps every version.
It will not serve an apex domain everywhere
On the paid tier your own domain works, but example.com with no www works only if your DNS provider flattens CNAMEs or offers ALIAS records. If yours does not, use www and redirect.
It will not take a domain that is behind another CDN
Ownership is proven through the domain's DNS, and another CDN in front of it hides exactly what has to be read. It has to come off that CDN first.
Free tier open today
Files are free. A database or your own domain is $12.
Priced and not yet purchasable: the billing that would collect it is not built.
The price works because this platform never pays for AI. You already pay Claude or ChatGPT; we give what it writes an address.
Free Plan
For static sites.
Freepermanently, not a trial
What you get:
- Up to 2 sites per account
- Static file hosting, served on our platform domain
- Deployable server functions Stored, but a request to one returns 402 until you upgrade.
- No card required
- No database
- No custom domain support
Paid Plan
For sites that need a database or a domain.
$12/ month
Everything in Free, plus:
- Up to 10 sites per account
- Postgres database included
- Custom domain support
- Fully executable server functions
- $12 of included usage Metered beyond it. Nothing measured here has come close to using it up.
- 60 days of full access for every new account Counted from the day you sign up. A card is taken at the start.
- Graceful downgrade, no cliff When the sixty days end the site keeps serving as static, because static is always free.
Heavy traffic, and if you stop paying
Neither plan counts requests
A bot flood is traffic you did not want and cannot prevent, so it is not traffic you pay for. That is part of the price, not a support policy.
Why we do not count requestsAsk your assistant to publish it. That's the whole thing.
Add the connector, then describe what you want. Everything it will refuse is written above.
Connect your assistant