Sizes
A size is chosen when a resource is created and describes what one instance of it is provisioned with. Sizes and plans are independent: a plan decides what an organization may do, a size decides what one resource gets.
Web services
| Size | vCPU | Memory | Instances |
|---|---|---|---|
| Starter | 1 | 512 MiB | 0 to 3 |
| Small | 1 | 1 GiB | 0 to 5 |
| Medium | 2 | 2 GiB | 0 to 10 |
| Large | 4 | 4 GiB | 0 to 20 |
Every size scales to zero: a service with no traffic runs no instance and costs nothing for compute until a request arrives. The upper bound is how many instances Kuppit will run at once under load. A new service is Starter.
PostgreSQL
| Size | vCPU | Memory | Storage |
|---|---|---|---|
| Starter | Shared | 0.6 GB | 10 GB |
| Small | 1 | 3.75 GB | 20 GB |
| Medium | 2 | 8 GB | 50 GB |
| Large | 4 | 16 GB | 100 GB |
A database runs continuously; it does not scale to zero. A new database is Starter, with PostgreSQL 18.
Costs
Infrastructure is billed on usage: compute while a service is serving, and a database's compute and storage while it exists. Kuppit does not show a fixed monthly price for a size, because for a service that scales to zero there is none; what a resource costs depends on what it does. The dashboard's Usage page shows what has been used.