Always running, never shared
Each app runs in its own container: its own files, its own processes and its own memory limit. Your app keeps running between requests, as it would on your own server.
No cold starts
Requests reach a process that is already running.
No borrowed memory
Memory limits are per container, so a neighbour’s leak stays in their container.
In-memory state works
Caches, websockets and background workers behave as they do on a normal server.
Processor time is guaranteed, and you can use more when it is free
A guaranteed share
Each plan has a guaranteed share of processor time, measured in GHz and split evenly across the sites on the plan.
More when the machine is quiet
When the machine has spare capacity, a busy site uses more than its share. Your bill stays the same.
Memory is a hard limit
Each site has a fixed memory limit. Need more? Move up a plan, or add memory to one site at £6 per GB a month.
| Plan | Sites | Guaranteed processor share | Memory per site | Storage per site | Price a month |
|---|---|---|---|---|---|
| Starter | 1 | 1 GHz | 1 GB | 15 GB | £12 |
| Business | 3 | 2 GHz | 1 GB | 30 GB | £24 |
| Pro | 10 | 3 GHz | 2 GB | 80 GB | £59 |
| Studio | 15 | 4 GHz | 2 GB | 150 GB | £99 |
| Agency | 25 | 5 GHz | 3 GB | 300 GB | £179 |
| Solo | 1 | 2 GHz | 4 GB | 50 GB | £29 |
| Solo Plus | 1 | 3 GHz | 8 GB | 100 GB | £59 |
| Solo HA | 1 | 3 GHz | 8 GB | 150 GB | £99 |
The processor share is split across the plan's sites. Full detail on the pricing page.
Your database runs on the same platform
Add managed PostgreSQL 15, Redis 7 or ClickHouse to any paid plan, each in a container of its own on our UK servers. They are not reachable from the internet unless you switch on a public address.
- PostgreSQL 15: attach it to your site and the dashboard offers its connection string as DATABASE_URL.
- Redis 7: for sessions, queues and caching, offered to your app as REDIS_URL.
- A MySQL database per site: as standard, never shared with another site.
- Private network: on Pro, Studio, and Agency: your apps, databases and laptop on one private network.
Each managed database is £6 per GB of memory a month, from £6 for the smallest. Managed databases in detail
Processor and memory graphs for each container, uptime checks as often as every minute with alerts, and a terminal on your running container. You can see how your app performs instead of guessing.
Performance FAQ
How much processor time does my app get?
Each plan has a guaranteed processor share, shown in GHz in the table, split evenly across the sites on the plan. That share is the floor your site always gets. When the machine has spare capacity, a busy site can use more than its share at no extra cost.
Is memory shared the same way?
No. Memory is a hard limit per site, set by your plan. One app cannot take memory from another, and a memory leak in one container cannot take your other sites down.
Do my apps have cold starts?
No. Your app keeps running between requests, so the first visitor after a quiet spell reaches a warm process. Pull-request previews are the exception: they sleep when idle and wake on the next visit.
Where do the databases run?
On our own servers in the UK, each managed database in a container of its own. Every site also gets its own MySQL database. Each managed database is charged by its memory, £6 per GB a month, so the smallest is £6 a month.
Can I see what my app is using?
Yes. The dashboard shows processor and memory use for each container, and uptime checks run as often as every minute with alerts, so you can see when it is time to move up a plan.
Get a container of your own
Warm processes, fixed memory limits and a database beside your app, from £12 a month. Also see deployments and Node.js hosting.