# What counts toward your limit — and what does not > The complete list, both columns, including the two things outside the ceiling and the reason for each. No "and more", no asterisks. The complete list, both columns, including the two things outside the ceiling and the reason for each. No "and more", no asterisks. 6 May 2026 · 3 min read · cmdz A ceiling is only as good as the list of what it covers. So here is the whole list, both columns, with the reasoning. ## What counts **Compute.** Per vCPU minute, on what you allocate rather than what you happen to use. Allocating two vCPU and using one costs two, because we reserved two for you and cannot sell them to anyone else. **Memory.** Per GB minute, same principle. **Storage.** Per GB month on the allocated volume size, sampled every five minutes. Growing a volume mid-month is charged from the moment it grows. **Object storage.** Per GB month plus a small charge per ten thousand operations. Both are metered from the storage layer directly, and we subtract delete markers rather than billing you for them. **Managed databases.** Per instance hour while running or degraded. A paused instance does not count, which makes pausing a real cost lever for staging environments. **Backups.** Per GB month, measured **after** compression, so you pay the smaller number. Restoring costs nothing at all — a restore fee is a fee for having a bad day, and we are not charging it. **Vector indexes.** Per GB month, separately, because an HNSW index is genuinely more expensive to keep resident than an ordinary index. **Build minutes.** Per minute of build. Queue waiting time does not count; you should not pay for our capacity planning. **Static requests.** Per million, for static workloads only. A server-rendered app is billed on its compute instead, not both. **Transactional email.** Per accepted message. Rejected messages cost nothing. **Dedicated IPv4.** Per month, and only if you ask for one. Shared IPv4 and IPv6 are included. ## What does not count **HTTPS certificates.** Requested and renewed automatically, wildcards included. **Extra domains on an app.** As many as you like. Render charges $0.25 per domain per month; we think charging for a DNS record and a certificate that cost us nothing is hard to justify. **Extra team members.** No per-seat price, on any plan. Vercel charges $20 per additional paid seat. A pricing model that makes you think twice about adding a colleague to a project is a pricing model working against the product. **Log retention.** 7 days of runtime logs and 90 days of build logs, searchable. **Metrics.** Thirteen months of history, so you can compare this month with the same month last year. **DDoS protection, HTTP/3, IPv6.** Standard on every workload. **The MCP server and all 47 tools.** Not an add-on, not a tier. **Support.** Included on every plan, including the free one. ## The two things outside the ceiling **Domain registrations and renewals.** A registration is a purchase from a registry, not a metered resource — the registry charges us at the moment you confirm and the name is yours for a year. If domains sat under the limit, hitting the limit could cause a renewal to fail, and a failed renewal costs you the domain, which is a far worse outcome than a separate charge. Billed on a card, at cost plus a flat 25%, with the renewal price shown before you confirm. **VAT.** The ceiling is on the amount excluding VAT. VAT is added according to your tax status, because that is not ours to cap. That is the complete list of exceptions. There is no third one. ## Rounding, and which way it goes All intermediate calculation happens in high-precision decimals and rounds to whole credits exactly once, when the line is written to the ledger, per metric per day. Where measurement is imprecise, the imprecision favours you by design: - CPU during the first fifteen seconds after a pod starts is not counted. - Storage growth within a five-minute window is only seen at the next sample. - Backups are measured after compression. - Requests blocked at the edge never reach us and never count. These are small amounts. We are listing them because a pricing page that only describes the favourable rounding is not a pricing page. ## Seeing where it went ```bash cmdz usage --breakdown metric cmdz usage --breakdown endpoint cmdz usage --diff 41 42 ``` Per metric, per endpoint, and the difference between two deployments. Your agent can read all three through `cmdz_explain_cost`, which is what makes "why did this get more expensive" a question with an answer rather than a theory. The full price book with an amount next to every line is on [the pricing page](/pricing). ## Set your limit and start. One click with a passkey, then you verify a payment method once to start your 14-day free trial (€ 10 of credit). After that it is prepaid pay-as-you-go — you only ever spend credit you have already bought, and no invoice ever arrives above the amount you set. - [Create account](https://app.cmdz.com/signup) - [Read the docs](https://docs.cmdz.com)