Civo

Civo GPU pricing overview

Civo is a specialist GPU cloud provider headquartered in London, UK. Civo is a developer-focused cloud platform offering B200, H200, H100, A100, and L40S GPU instances with UK data sovereignty and competitive pricing. On-demand and 36-month commitment options available. Vera Rubin NVL72 and B300 Blackwell Ultra coming soon. Kubernetes GPU clusters deploy in 120 seconds. 100% renewable energy, annualised PUE ~1.2. ISO 27001, SOC 2 Type II. UK data sovereignty — data not transferred internationally. Billing is On-demand, 6/12/24/36-month commitments with a minimum commitment of None (on-demand). Available regions include UK, EU, US, India. GPU instances can be provisioned on-demand, making Civo suitable for both short-duration experiments and sustained production workloads.

Civo vs other GPU providers

Civo competes with providers including Lambda Labs, CoreWeave, RunPod, Paperspace, Vast.ai, and the major hyperscalers (AWS, Google Cloud, Azure) for GPU compute workloads spanning LLM training, fine-tuning, and inference serving. Key differentiators include: B200, H200, H100 — competitive UK pricing; 36-month commitment pricing available; UK data sovereignty — data never transferred internationally. Use the side-by-side comparison tool above to see Civo pricing against any other provider across shared GPU models. For a broader market view, the live GPU prices table shows all 3 Civo listings alongside 91+ providers in a single sortable view.

Best use cases for Civo

Civo is best suited for: UK/EU teams needing data sovereignty, Kubernetes-native AI deployment, Teams wanting renewable-energy GPU compute, Long-term commitments at discounted rates. Support tiers range from Standard → Enterprise, making it viable for both individual researchers and enterprise teams with SLA requirements. There are currently 3 active GPU listings on Civo, covering A100 80GB, RTX 4090, L40S. H100 SXM5 instances with NVLink interconnect are commonly used for large-scale training workloads. A100 40GB and RTX 4090 instances are frequently used for fine-tuning and inference of smaller models.

Civo billing model and cost structure

Civo uses On-demand, 6/12/24/36-month commitments pricing. Spot pricing is not currently available on this provider — all instances are on-demand. Reserved instance pricing may be available for predictable long-running workloads — check the provider's pricing page for current committed-use rates. Always compare the effective hourly rate including egress, storage, and networking costs when evaluating total cost of ownership across providers.

Choosing the right GPU on Civo

GPU selection depends on model size, precision, and whether your workload is compute-bound or memory-bandwidth-bound. For LLM training above 30B parameters, H100 80GB SXM5 instances with NVLink are the standard choice — high HBM3 bandwidth and FP16 throughput make them well-suited for large transformer workloads. For inference of 7B–13B models in FP16 or BF16, A100 40GB is a common choice on many providers. RTX 4090 instances are widely used for fine-tuning, prototyping, and quantized inference (INT4/INT8) of models up to 70B. Read the H100 vs A100 guide or the GPU benchmarks for ML guide for a full breakdown.

How Civo pricing data is collected

Prices shown are sourced from Civo's public pricing API or pricing page and refreshed every 15 minutes. On-demand rates reflect the current list price for a single GPU instance in the cheapest available region. Spot prices, where available, reflect interruptible instance rates at the time of the last snapshot. All prices are in USD per hour. Daily snapshots are kept in our history archive and visualised in the GPU price history charts — useful for identifying seasonal pricing patterns and evaluating whether current rates are above or below the 30-day average.

Evaluating managed LLM inference APIs as an alternative to self-hosted GPU compute? Compare live LLM token prices across OpenAI, Anthropic, Google, Groq, and many other providers. The cheapest GPU cloud guide covers the break-even analysis between self-hosted and managed inference at different request volumes.