# Usage rates and included amounts

> The list rate of each meter that web services, instances, game servers and databases bill by, and what every account and the Paid plan include each month.

Source: https://www.coritan.com/docs/billing/usage-rates/

These are the list rates in US dollars on Oct 11, 2026, for services [billed by use](/docs/billing/usage-billing/). The order's quote shows the rates that apply to what you are ordering, and the public [pricing page](https://www.coritan.com/pricing) shows the current ones.

## Rates {#rates}

| Meter | Unit | Rate | What it counts |
| --- | --- | --- | --- |
| Memory | GiB-hour | $0.0030 | A web deployment: the memory its instances hold while they run. A server: its memory size while it runs. |
| CPU | vCPU-hour | $0.015 | The processor time a service uses. A busy vCPU for an hour is one vCPU-hour. |
| Disk | GB-hour | $0.00005 | A server's disk, for as long as the server exists, running or not. A web deployment has no disk meter. |
| Requests | million | $0.15 | A web deployment: the requests an instance answers. |
| Data out, North America and Europe | GB | $0.0125 | What a service sends to visitors from a location in that region. |
| Data out, Oceania | GB | $0.025 | The same, from a location in Oceania. |
| Data out, everywhere else | GB | $0.02 | The same, from any other location. |
| Builds | minute | $0.0025 | A web deployment: each minute a build runs. |
| Logs | GB | $0.125 | A web deployment: the log data its instances write, before it is compressed. |

A GiB-hour is one gibibyte (1,024³ bytes) held for one hour. A GB of data is 1,024³ bytes too.

A server on a **Performance** hardware tier pays 1.5 times the memory, CPU and disk rates. Data out costs the same on every tier. A web deployment has one tier.

## Included each month {#included}

Each month starts on the 1st (UTC). The amounts are shared by every service of an account in that pool, and they are used up in the order the hours pass. Past an amount, every unit is billed. [How usage billing works](/docs/billing/usage-billing/#included) explains the two pools.

| Meter | Web pool, every account | Server pool, with the Paid plan |
| --- | --- | --- |
| Memory | 100 GiB-hours | 25 GiB-hours |
| CPU | 50 vCPU-hours | 6.25 vCPU-hours |
| Disk | Not billed | 200 GB-hours |
| Requests | 10 million | Not counted |
| Data out, North America and Europe | 100 GB, in any region | 1,000 GB |
| Data out, Oceania | The same 100 GB | 500 GB |
| Data out, everywhere else | The same 100 GB | 500 GB |
| Builds | 3,000 minutes | Not billed |
| Logs | 15 GB | Not billed |

## Regions for data out {#regions}

Data out is priced by where the service runs, because Coritan cannot see where a visitor is. Each location belongs to one class.

| Class | Locations |
| --- | --- |
| North America and Europe | `fra`, `lhr`, `iad`, `ewr`, `lax`, `pdx` |
| Oceania | `syd` |
| Everywhere else | `sin` |

A deployment that runs in several locations pays each location's data out at that location's rate.

## The Paid plan {#paid-plan}

The Paid plan costs $4.50/mo, $12.15 for a quarter or $43.20 for a year, for the whole account. Cloud Compute instances, game servers and databases need it, and Pro, Business and Enterprise include it ([How usage billing works](/docs/billing/usage-billing/#paid-plan)).

## Monthly figures {#month}

A month in an estimate is 730 hours. The order page and its quote use that figure for the monthly cost of a server that runs and exists all month.

## Read the rates from the API {#api}

`GET /api/v1/price-book` answers every price the cost estimate on the public pricing page reads, in one request and with no sign in. It holds the rate card (`card.rates`, the price of data out by region in `card.egress_gb`, and the amounts each pool includes in `card.included_monthly`), the Paid plan's price (`paid_plan`), every size billed by use (`sizes`, with its memory, vCPUs and disk), the Free, Pro and Business plans with their limits (`plans`), Object Storage's rates (`storage`), the SMTP Relay plans (`relay`), the price of an extra mailbox (`mail`) and the domain price list (`domains`). Prices are strings in US dollars, so no digit is lost. The answer is the same for every visitor, and a price you change in the admin console reaches it within a minute.

## Related

- [How usage billing works](/docs/billing/usage-billing/)
- [How App Deployment is billed](/docs/managed-containers/how-billing-works/)
- [How Cloud Compute is billed](/docs/cloud-compute/how-billing-works/)
- [How game servers and databases are billed](/docs/managed-containers/how-servers-are-billed/)

## API

- `GET /api/v1/price-book`: The price book (https://www.coritan.com/docs/api/reference/client/catalog/#op-get-api-v1-price-book)