# Cloider pricing reference, price kinds and units > Every Cloider price kind and unit for clusters, apps, databases, buckets and the registry, how to read current prices, and worked cost examples. This page lists **what** Cloider charges for and in which unit. The amounts themselves change over time and are kept in one place, so read them from [cloider.com/#pricing](https://cloider.com/#pricing), from `cloider pricing`, or from the public pricing endpoint. How usage is measured is explained in [Billing model](/concepts/billing-model). ## At a glance | Product | Price kind | Unit | Field in `GET /api/pricing` | | --- | --- | --- | --- | | Kubernetes cluster | Compute | Per compute unit per month | `cluster.compute_unit` | | Kubernetes cluster | Compute unit size | vCPU to memory ratio | `cluster.cpu_to_mem_ratio` | | Kubernetes cluster | Persistent volumes | Per GiB per month | `cluster.volume_gi` | | Kubernetes cluster | Load balancers | Per load balancer per month | `cluster.loadbalancer` | | App | Compute | Per compute unit per month | `app.compute_unit` | | App | Compute unit size | vCPU to memory ratio | `app.cpu_to_mem_ratio` | | Database | Plan | Per database per month, per engine and plan | `database...price` | | Database (paused) | Retained storage | Per database per month while paused | `database...paused_price` | | Bucket | Storage | Per GiB stored per month | `bucket.storage_gi` | | Registry project | Storage | Per GiB stored per month | `registry.storage_gi` | | Domains, DNS records, targets | | Free | | | Bucket requests and traffic, registry pushes and pulls | | Free | | All prices are in US dollars, per month. A billing month counts as 30 days (720 hours), and usage is prorated by the second. Invoices show hourly rates, which are the monthly price divided by 720. ## Read current prices **Dashboard** The pricing section of the home page, [cloider.com/#pricing](https://cloider.com/#pricing), has a calculator for Kubernetes clusters: set vCPU, memory, storage and average utilization to estimate a monthly cost. It uses the current cluster prices. **CLI** ```bash cloider pricing ``` The first table lists `SERVICE`, `UNIT` and `PRICE` for each price kind: the cluster's `compute unit`, `volume per Gi`, `load balancer` and `cpu to memory ratio`, the app's `compute unit` and `cpu to memory ratio`, the bucket's and registry's `storage per Gi`. The second lists every database `PLAN` per engine with its monthly `PRICE`, `CPU`, `RAM`, `STORAGE` and `PAUSED` price. Add `-o json` for the raw answer. **Terraform** The Terraform provider doesn't read prices. Use the **CLI** or **API** tab. **API** The pricing endpoint is public: it needs no token. ```bash curl https://cloider.com/api/pricing ``` ```json title="Response shape" { "cluster": { "compute_unit": "", "volume_gi": "", "loadbalancer": "", "cpu_to_mem_ratio": "" }, "app": { "compute_unit": "", "cpu_to_mem_ratio": "" }, "bucket": {"storage_gi": ""}, "registry": {"storage_gi": ""}, "database": { "PostgreSQL": { "Hobby": { "price": "", "cpu": "", "ram": "", "storage": "", "paused_price": "" } } } } ``` Prices are decimal numbers encoded as JSON strings. `database` has one key per engine (`PostgreSQL`, `MySQL`, `MongoDB`, `Redis`) and, under each, one key per plan (`Hobby`, `Starter`, `Basic`, `Standard`, `Plus`, `Pro`). **MCP** ```text title="Prompt" What are Cloider's current prices for clusters and PostgreSQL plans? ``` ```json title="Tool call: get_pricing" {} ``` ## Compute Kubernetes clusters and apps pay for **compute units**. One compute unit is one vCPU, or the memory the ratio pairs with one vCPU, whichever a workload uses more of: ```text compute units = max(vCPU, memory in MiB / (cpu_to_mem_ratio x 1000)) ``` `cpu_to_mem_ratio` is MiB of memory per millicore of CPU, so `cpu_to_mem_ratio x 1000` is the MiB of memory in one compute unit. `cloider pricing` shows the ratio as `1:`. Each running container counts the larger of its request and its actual use, for CPU and memory separately. A cluster's compute includes its Kubernetes control plane; the calculator on cloider.com estimates the control plane at about $9.99 a month. Clusters and apps have separate compute prices. On an invoice, compute appears as **Compute-Hour** lines: compute units times hours. ## Storage | What | Measured as | Price kind | | --- | --- | --- | | Cluster persistent volumes | Provisioned capacity of each volume, in GiB | `cluster.volume_gi` | | Bucket data | GiB stored, averaged over time | `bucket.storage_gi` | | Registry project images | GiB stored, averaged over time | `registry.storage_gi` | | A paused database's storage | The storage its plan provisions | Cluster volume rate, quoted per plan as `paused_price` | On an invoice, storage appears as **GB-Hour** lines: GiB times hours. ## Load balancers Each Service of type `LoadBalancer` that has a public IP is billed per month, prorated to the time it is active. On an invoice each one has its own **LoadBalancer** line with its name and IP, in **Hour** units. ## Databases Databases are priced per **plan**, per engine. A plan fixes the CPU, RAM and storage, and has a flat monthly price, prorated to the time the database is **Ready**. The plans are, from smallest to largest: | Plan | Notes | | --- | --- | | Hobby | The smallest plan | | Starter | | | Basic | | | Standard | | | Plus | | | Pro | The largest plan | The CPU, RAM, storage and price of each plan are in the pricing endpoint and `cloider pricing`. You can [resize](/databases/resize) a database to a larger plan; the invoice then has one line per plan for the time on each. While a database is **Paused**, it pays only its `paused_price`, which is the plan's storage at the cluster volume rate. ## Worked examples These examples use made-up prices to show the arithmetic. Substitute the current prices from `cloider pricing`. **A small cluster for a whole month.** Suppose a compute unit costs $C a month, a GiB of volume $V, a load balancer $L, and the ratio is 1 vCPU to 3 GiB. A cluster whose containers average 0.5 vCPU and 2 GiB, with a 10 GiB volume and one load balancer, all month: ```text compute units = max(0.5, 2 / 3) = 0.67 monthly cost = 0.67 x C + 10 x V + 1 x L ``` **A database for ten days.** A database on a plan priced at $P a month, Ready for 10 days, then deleted: ```text cost = P x 10 / 30 ``` **A paused database.** The same database paused for the whole month costs its `paused_price`. ## Price changes Prices have effective dates. Each day's usage is priced at that day's rates, so a new price applies from its effective date onward. If prices change during a month, the invoice splits each affected line into one line per price period. ## Next steps - [Billing model](/concepts/billing-model): how usage is measured. - [Usage](/account/usage): what your resources cost right now. - [Billing](/account/billing): your invoices.