Projects and services
Sizes and replicas
What a size and replicas do for each kind of service, and how each is charged.
Updated
Every service has a size, and every application has a replica count. The size sets the rate the service is charged at, by the hour for an application or a stack and by the GB of data it holds for a database, and the CPU and memory an application's containers or a database may use. Replicas set how many containers of an application run side by side.
Sizes
The sizes, smallest first, are Nano, Small, Medium, Large and Extra large. Cahaves sets what each one holds and what it costs, and can change both, so this page names no figures. You can read the current ones in two places while you create a service:
The Size field lists every size on offer with its CPU and memory, its monthly estimate and its rate in dollars an hour. The line under it reads "Billed by the hour. The monthly figure assumes 730 running hours."
The Order summary beside the form shows, for the size you chose, CPU, Memory, Instance disk, Hourly rate and the 730-hour estimate. "Actual billing is hourly. Monthly prices estimate 730 running hours."
For a database, both show the size's rate per GB-month instead, such as "$0.50/GB-mo", and the Order summary shows Rate and Charged by: "The data it holds, each hour it runs".
On the nano size in the shared pool, the Order summary adds a Free allowance row: "Your first nano service across all your organizations runs free", or for a database, how much data your first nano database across all your organizations holds free.
Instance disk is listed for each size, and Cloud does not hold a service to it. Keep data that must outlive a deployment on a volume or in a database.
The Size field on a service's Settings section lists the sizes with CPU and memory from a fixed list and without prices. When the two disagree, the create form's figures are the current ones.
What a size applies to
| Service | What its size does |
|---|---|
| Application | Sets its rate, and holds each of its containers to the size's CPU and memory as real limits. |
| Database | Sets its rate only. Cloud does not limit a database's CPU or memory. |
| Compose stack | Sets its rate only, at the dedicated rate, from Small up. Cloud cannot limit the containers of a stack. |
A service's Overview shows its Size, its Pool (Shared, or Dedicated for a compose stack) and, for an application, its Replicas.
Replicas
An application runs 1 to 10 identical containers side by side, set under Replicas on its Settings section, "Copies running side by side." A database and a compose stack have no replica count.
How a size is charged
Once an hour, Cloud counts the containers each service has running and charges that hour at the size's rate for each one, at the rate in force for that hour. Three replicas are charged three times one; a compose stack is charged for each of its running containers. A service with nothing running is charged nothing for that hour.
A database is charged instead by the data it holds: for each hour it runs, the GB it held when Cloud last measured it, at its size's rate per GB-month over 730 hours. Your first nano application in the shared pool runs free, and your first nano database holds a set amount of data free, each counted once across all your organizations. Billing explains the charges, the free allowance, the monthly limit and how each month is paid.
When Cahaves changes a rate, the new rate applies from the hour it takes effect. An hour already charged keeps the rate it was charged at.
Change the size or replicas
On the service's Settings section, choose a new Size or Replicas and press Save settings.
| Service | Takes the change |
|---|---|
| A running application | At once. It restarts with the new limits or replica count. |
| A stopped or never-deployed application | At its next start or deploy. |
| A database | Charged at the new size's rate from the next hourly charge. Its new CPU and memory apply at its next deploy. |
| A compose stack | Charged at the new size's rate from the next hourly charge. Nothing about the running stack changes. |
A catalogue application names the smallest size it runs well at, and a smaller one is refused when you create it, with a sentence such as "n8n needs small or larger."
When Cahaves withdraws a size, it stops being offered. A service already on it keeps running at it, and the next time you save that service's settings, choose a size that is on offer: Cloud refuses a withdrawn one with "Choose one of the sizes on offer."