Hosting for the apps you build with AI agents
An agent can write a working app in an afternoon. Then it needs somewhere to run, a database, an SSL certificate, backups and someone watching it. That part is what we do, and each piece is one action or one API call.
The loop
Write, push, review it running, merge
The faster an agent writes, the more the work moves to everything after the code. These four steps are the whole cycle.
The agent writes it
Claude Code, Cursor, Copilot, an in-browser builder, or your own hands: whatever you work in, the output is a repository. Nothing about your project has to be shaped around us, and there is no library of ours to add.
Push, and it deploys
Connect GitHub, GitLab or Bitbucket, choose the branch, and every push builds and deploys into a container of your own. 14 presets, or your own Dockerfile.
Review it running
Each pull request on GitHub gets its own preview address. When an agent has written more code than you want to read, trying it is the faster review. On Pro, Studio, Agency, Solo Plus, and Solo HA.
Merge, or roll it back
Merge and your live app rebuilds. If a commit turns out badly, deploy the previous one in one action. Your data lives in a separate database, so rolling back code leaves it alone.
What the app needs
A database beside your app, priced by its memory
Three engines, each in a container of its own. Each database is charged by the memory you give it, from £6 a month, on any paid plan.
PostgreSQL
version 15The usual choice for an application database.
ClickHouse
version 25.8For fast reports over events, logs and product usage.
The database is closed to the internet by default
A managed database is not reachable from the internet unless you switch on a public address, where you choose which IP addresses may connect and connections are encrypted with TLS. On plans with the private network, it can also get a private address that only your own apps and devices can reach. The private network is on Pro, Studio, and Agency, from £59 a month, and your laptop can join it to run a query by hand. A standby copy that takes over automatically (PostgreSQL and Redis) doubles that database's price.
Let the agent do it
A key scoped to the job, not to your account
If you would rather not click through the setup yourself, create a key in the dashboard and tick what it is allowed to touch. Hand it to your agent or your build pipeline. It is a key for the job, not a way into your account.
Writing an integration rather than pointing an agent at it? The API reference is here.
A key cannot widen itself
Creating, rotating and revoking keys requires a signed-in browser session. A scoped key cannot mint a broader key, so a leaked deploy key stays a deploy key.
Expiry and a label
Set an expiry when you create it, and give it a label naming the job or the agent it belongs to. Up to 10 keys can be active at once.
Rotate in place
Rotation issues a fresh token with the same name, scopes and expiry. Swap it into your agent, then retire the old one.
Recorded
Key creation, rotation and revocation land in your audit log with who did it and when.
Already handled
The parts you do not have to build
Included on every plan, on UK servers we run ourselves, at the same fixed price.
What it costs
One fixed price per plan, in GBP
The price on the pricing page is the price on your receipt, whatever your traffic does. Managed databases are added on top, priced by memory, from £6 a month each.
Questions from people shipping agent-written code
For the whole thing as a walkthrough, read how to deploy an app your AI agent built.
Does it matter which AI tool wrote the code?
No. We deploy from a git repository, so anything that produces one works: Claude Code, Cursor, Copilot, an in-browser builder, a teammate or you. There is nothing of ours to install and no project layout to adopt.
Can an AI agent deploy on its own?
Yes, if you want it to. Create a key in the dashboard, tick what it is allowed to touch, and give it to the agent. Many people do the setup themselves first and hand over the repetitive parts later.
What stops an agent doing something I did not intend?
A key only carries the permissions you ticked, and it can never create another key or widen its own reach. You can give it an end date, replace it, or revoke it outright, and each of those is written to your audit log. Your billing and account settings are never in its reach at all.
Which databases can I run next to the app?
PostgreSQL 15, Redis 7 and ClickHouse 25.8, each in its own container. Attach one to a site and the dashboard offers its connection string as DATABASE_URL (or REDIS_URL). You can add managed PostgreSQL, Redis and ClickHouse databases to any paid plan. Each database is charged by its memory: £6 per GB a month, with 1 GB the smallest size, so a 1 GB database is £6 a month and a 4 GB one is £24. Its processing power grows with its memory. A standby copy that takes over automatically if the main one fails (PostgreSQL and Redis only) doubles the price.
How is this billed if my app gets busy?
One fixed price per plan, in pounds, whatever your traffic does. Plans start at £12/month, and the price you sign up at is the price you renew at. Any managed database you add is priced by its memory, so you see that cost before you create it. An app on Starter (£12) with a 1 GB PostgreSQL database (£6) costs £18 a month.
Do I get preview environments on every plan?
Pull-request previews are on Pro, Studio, Agency, Solo Plus, and Solo HA, for GitHub repositories. Git deploys on every push come with every paid plan, from Starter at £12/month.
Can I reach the database from my laptop?
Yes. On Pro, Studio, and Agency, add your laptop to the private network and your local tools connect to the database's private address. On any plan you can instead switch on a public address: you choose which IP addresses may connect, and connections use TLS.
What happens to the code if I leave?
It stays yours. Your app is built from your repository, which you own and control, and your data lives in a database you can back up and download. There is nothing proprietary in the middle to extract yourself from.