Shared or dedicated nodes
Every environment picks a tenancy when you create it, and a deploy can override it. Here's the difference, the trade-offs, and when to mix both. You're not locked in: change an environment's tenancy later.
Cheaper out of the box
Your build runs alongside other tenants on pooled capacity, separated by container boundaries. It's the default, and there's no capacity to plan.
Set the CPU and memory each replica gets, from 0.125 vCPU and 256 MB up to 4 vCPU and 8 GB, and pay per second for what your running replicas request. Stop a workload and its billing stops at once.
- Marketing sites and landing pages
- Web apps and admin panels
- APIs with light or bursty traffic
- Staging, previews and internal tools
Built for scale
Lease a whole node in a fixed size, 2 or 4 vCPU today, used only by your organisation. No noisy neighbours, and performance that stays predictable as traffic grows.
You pay per second for the node while you hold it, however busy it is. Remove everything from it and billing stops. When your replicas need more than one node holds, another is leased automatically.
- Production APIs and microservices
- Databases and other stateful services
- High-traffic web apps
- Compliance-sensitive workloads
Side by side
| Shared | Dedicated | |
|---|---|---|
| You pay for | The CPU and memory each running replica requests, per second | Each leased node, per second |
| Per replica | 0.125 to 4 vCPU, 256 MB to 8 GB, 1 to 4 GB per vCPU | Up to the node's size, no ratio rule |
| Other tenants | Yes, separated by containers | None |
| Node metrics | No | Yes, on the Nodes page |
| Price | $7.30 per vCPU, $10.07 per GB a month | $67.38 (2 vCPU / 4 GB), $146.00 (4 vCPU / 8 GB) a month |
Mix both
Most teams start every environment on shared nodes, then move specific ones to dedicated as traffic or compliance needs grow.
| Environment | Runs | Tenancy |
|---|---|---|
| marketing | The website | Shared |
| staging | Every service, for testing | Shared |
| production | The API and its database | Dedicated |
Billing example: an organisation runs five workloads on shared nodes and stops one. Billing for that one stops immediately, and the organisation keeps paying only for the four still running.
Technical comparison in the docs · Where compute fits in the platform
Pick a tenancy per environment
Free to sign up. You add a card when you deploy your first build.