# Civo Compute

Official pricing: https://www.civo.com/pricing  
Category: hyperscaler · Isolation: vm

## Pricing regimes (raw)

- **Standard Compute** (sizes): xSmall 1 vCPU/1 GiB $0.00744/h; Small 1 vCPU/2 GiB $0.014881/h; Medium 2 vCPU/4 GiB $0.029762/h; Large 4 vCPU/8 GiB $0.059524/h; XL 6 vCPU/16 GiB $0.119048/h; 2XL 8 vCPU/32 GiB $0.238095/h
- **Performance Compute** (sizes): Performance-S 4 vCPU/16 GiB $0.119055/h; Performance-M 8 vCPU/32 GiB $0.238096/h; Performance-L 16 vCPU/64 GiB $0.476192/h; Performance-XL 32 vCPU/128 GiB $0.952384/h
- **CPU optimized** (sizes): CPU-8 8 vCPU/16 GiB $0.190476/h; CPU-16 16 vCPU/32 GiB $0.380952/h; CPU-32 32 vCPU/64 GiB $0.761905/h; CPU-64 64 vCPU/128 GiB $1.52381/h
- **RAM Optimized Compute** (sizes): RAM-S 2 vCPU/16 GiB $0.107137/h; RAM-M 4 vCPU/32 GiB $0.214288/h; RAM-L 8 vCPU/64 GiB $0.428575/h; RAM-XL 16 vCPU/128 GiB $0.857137/h
- **GPU Compute on-demand** (sizes)
- **GPU Compute 6-month commitment** (sizes) [commit]
- **GPU Compute 12-month commitment** (sizes) [commit]
- **GPU Compute 24-month commitment** (sizes) [commit]

## Features

Yes: snapshots, fork/clone, persistent disk, volumes, ≥24 h sessions, custom image (Docker or snapshot), start from your own snapshot, full VM (own kernel), Docker inside, root, systemd, SSH, public IPv4, custom domains, raw TCP inbound, egress allowlist, open internet, static egress IP, private networking, GPU, Python, Node.js, live fork (no pause), EU data residency, snapshots on demand, gVisor or VM (no shared kernel), inbound access rules, firewall inside (nftables), extra volumes

No: memory snapshots, pause/resume, idle auto-stop, your own Docker/OCI image, nested virtualization, browser, desktop GUI, computer-use API, code interpreter, browser + desktop control, anti-bot stealth, CAPTCHA solving, residential IPs, preinstalled agents, HTTPS preview URLs, self-hosting, BYOC, open source, SSO, arm64, Windows, macOS, GPU desktop, HTTP method/path egress rules, wake on request, live resize, memory fork, MCP server, automatic snapshots, agent harness API, hosted agent API (their own agent), secret proxy, secret proxy for any API, shared volumes

Unknown: everything else. Evidence (source + quote) per feature: https://battleships.dev/data/providers/civo.json → feature_evidence

## Caveats

- DIY infrastructure rather than an agent-managed sandbox: guest installation, HTTPS/domain setup, abuse controls and operations are customer responsibilities. Linux guest administrative capabilities are not preinstalled agent features. 30% guest CPU utilization does not reduce allocated-compute charges. Unknowns remain null; a partial subtotal is not a complete invoice.
- Compute Large 4/8/100GB $0.059524/h; do not substitute Kubernetes Large 60GB root-disk specs.
- Hourly/monthly toggle is illustrative. Billing docs say 730h month, while displayed $40/month divided by hourly rate is ~672h; no cap inferred from inconsistent arithmetic.
- Egress and ingress explicitly free/unlimited. Powered-off instances still charged until deleted.
- Snapshot API lifecycle/current price not verified: linked snapshots page returned 404. Billing mentions snapshots but that alone does not establish usable snapshot entitlement. Custom OS images described for CivoStack Enterprise; public-cloud custom image support left null.
- Snapshot price re-checked 2026-09-28: neither civo.com/pricing nor docs/account/billing publishes a snapshot rate, so snapshot_gib_month stays null (unknown, not free).
- Boot time not measured: the pricing page only says instances launch "in under 60 seconds"; boot_overhead_s left unset.

## How this provider charges


DIY infrastructure rather than an agent-managed sandbox: guest installation, HTTPS/domain setup, abuse controls and operations are customer responsibilities. Linux guest administrative capabilities are not preinstalled agent features. 30% guest CPU utilization does not reduce allocated-compute charges. Unknowns remain null; a partial subtotal is not a complete invoice.

Prices below are public list prices unless a row explicitly says promotion/commitment. USD; taxes excluded unless noted.

| Regime | When / billing | Captured prices | Source |
|---|---|---|---|
| Standard Compute | On demand; No monthly cap: billing docs explicitly call monthly figures illustrative 730-hour equivalents. | Large: $0.059524/h; cap None | https://www.civo.com/pricing |
| Performance Compute | On demand; Larger RAM ratio; hourly, not usage-based CPU. | Performance-S: $0.119055/h; cap None | https://www.civo.com/pricing |
| CPU optimized | On demand;  | CPU-8: $0.190476/h; cap None | https://www.civo.com/pricing |

## Billing details
- **granularity_seconds**: 3600
- **minimum_billed_seconds**: 3600
- **setup_fee_usd**: 0
- **api**: True
- **cli**: True
- **ipv 6**: Unknown; not assumed zero.
- **ingress_usd**: 0
- **minimum_term**: Started hour, no cap confirmed.
- **backup**: Unknown; not assumed zero.
- **cpu**: Fixed compute sizes; dedicated physical-thread guarantee not established.
- **provisioning**: Provider claims under 60-second VM launches, not measured API-ready guarantee.
- **free**: $250 new account credit for first month; not a recurring free tier.

## Gotchas
- DIY infrastructure rather than an agent-managed sandbox: guest installation, HTTPS/domain setup, abuse controls and operations are customer responsibilities. Linux guest administrative capabilities are not preinstalled agent features. 30% guest CPU utilization does not reduce allocated-compute charges. Unknowns remain null; a partial subtotal is not a complete invoice.
- Compute Large 4/8/100 GB $0.059524/h; do not substitute Kubernetes Large 60 GB root-disk specs.
- Hourly/monthly toggle is illustrative. Billing docs say 730h month, while displayed $40/month divided by hourly rate is ~672h; no cap inferred from inconsistent arithmetic.
- Egress and ingress explicitly free/unlimited. Powered-off instances still charged until deleted.
- Snapshot API lifecycle/current price not verified: linked snapshots page returned 404. Billing mentions snapshots but that alone does not establish usable snapshot entitlement. Custom OS images described for Civo Stack Enterprise; public-cloud custom image support left null.

## Worked example
4 vCPU / 8 GiB; 50 concurrent × 8 h/day × 22 days = **8,800 guest-hours**; 30% CPU busy; **50 GiB-month total snapshots**, **100 GiB total egress**. 50 GiB retained state is total, not 50 GiB per VM. Compute-only subtotals below exclude unknown components and tax.

| Mode | Delete/recreate / active-window compute | 50 retained hosts, 730-hour month |
|---|---:|---:|
| Standard Compute | $523.81 | $2,172.63 |
| Performance Compute | $1,047.68 | $4,345.51 |
| CPU optimized | $1,676.19 | $6,952.37 |

Snapshot subtotal: unknown; rate $None/GiB-month. Egress: see allowances, pooling/accrual and rate $0/GiB; not every mode has the same allowance.
Powered-off compute billed: True. A retained-host column is the always-running upper scenario when this is false; powered-off storage/IP still accrue.
Monthly caps attach to instance identities, not to a pool of replacement instances. The active-window column requires deleting/releasing billable compute between shifts for products that bill while off. Restoring from disk is not memory resume. The engine cannot perfectly model these lifecycles; see validation/estimator-gaps.md.

## Sources
- https://www.civo.com/pricing
- https://www.civo.com/docs/account/billing
- https://www.civo.com/docs/compute/create-an-instance
- https://www.civo.com/compute
