Pricing
The monthly minimum becomes infrastructure credit, storage is metered plainly, and dedicated plans begin with the capacity the workload actually needs.
Plans
Annual billing costs the equivalent of ten monthly minimums. Usage beyond included credit and any applicable taxes are billed separately.
Starter
For one developer
A real deployment with a tiny starting bill.
Pro
For teams shipping often
More collaborators, history, projects, and storage.
Enterprise
For isolated infrastructure
Reserved customer capacity without paying for hardware you do not need.
Starter example
Low risk, positive contribution from day one.
Shared pool example
Density and autosizing create the margin.
Dedicated example
Dedicated does not need to mean oversized.
The 100-customer figures are an illustrative planning scenario, not a margin guarantee. Actual workload mix, support, taxes, backups, and capacity determine cost.
Compare
| Capability | Starter | Pro | Enterprise |
|---|---|---|---|
| Included members | 1 | 5 | Custom |
| Workspaces | 5 | 25 | Custom |
| Projects | 10 | 100 | Custom |
| Services | 25 | 100 | Custom |
| Persistent storage | 10 GiB | 100 GiB | Planned |
| Automatic resource profiles | |||
| Manual CPU and memory | |||
| Pull-request previews | |||
| Organization invitations | |||
| Dedicated data plane | |||
| Log retention | 7 days | 30 days | 30–90 days |
If an invoice is surprising, the product has failed. These are the rules we want users to understand before deploying.
It becomes usage credit. Starter includes €5 of infrastructure usage and Pro includes €20. If measured usage stays inside that credit, the minimum is the bill.
Shared plans meter provisioned persistent storage at €0.20 per GiB-month. The charge uses included plan credit first. Starter supports up to 10 GiB and Pro up to 100 GiB; Enterprise storage is capacity-planned.
The selected plan begins and its full monthly minimum becomes usage credit. Before the preview ends, billing shows the projected charge and the resources producing it.
Preview services start asleep at zero replicas and wake on HTTP, so idle previews avoid normal compute usage. Persistent data is not cloned automatically.
No. Enterprise means isolation, not waste. We can begin with a small reserved pool for modest workloads and add capacity when sustained demand proves it is needed.
Yes. Internal and managed-service workspaces can be assigned a non-billable contract entitlement while still recording usage and cost internally.
Private preview
The preview is designed to reach production, not trap you in a toy tier. Keep the project, domain, and configuration when billing starts.
