Documentation

Getting Started🔗 Copy link

Compare Cloud Costs is a free, open-source tool. It aggregates and normalizes on-demand (pay-as-you-go) pricing across AWS, Microsoft Azure, Google Cloud, Oracle Cloud, DigitalOcean, and Alibaba Cloud, plus 8 specialized providers, into one side-by-side view.

Use the product tabsat the top to switch between categories: AI & Machine Learning, App Hosting, Certificates, Containers, Databases, Data & Analytics, GPU, Inference, Networking, Search, Storage, Time-Series, Graph, and more.

Use the filter sidebar on the left to narrow results by provider, geography, instance specs, and product-specific attributes.

What CCC is (and isn't)

CCC is a planning and comparison tool, built from publicly available pricing pages and APIs. It's meant to help you compare options quickly during architecture and budget planning, before you've committed to a provider or a configuration.

It is not a replacement for a dedicated FinOps or cloud cost management platform. Those tools connect directly to your cloud accounts and see things CCC structurally cannot: your actual usage, your negotiated or contracted rates, anomaly detection on live spend, and recommendations tuned to your specific bill. CCC works from list prices published by each provider, which makes it a strong starting point for directional comparisons, not a source of truth for what you're actually paying today.

If you already run a mature FinOps practice, think of CCC as a lightweight complement for early-stage "what would this cost on another cloud" questions, not a tool that competes with or replaces the platform you use to manage live spend.

CCC is independent — not affiliated with, endorsed by, or sponsored by any cloud provider it compares. Every provider is priced with the same methodology from the same kind of public source, so no provider gets an advantage in how it's presented. See the Terms of Use for the full statement.

↑ Go back to the top

Product Categories🔗 Copy link

AI & Machine Learning

Compares managed AI foundation models and APIs (e.g., GPT-4, Claude 3, Gemini 1.5, Llama 3). Filter by context window, multimodal support, and input/output price per 1M tokens.

App Hosting

Covers managed application hosting and Platform-as-a-Service offerings (App Service, App Engine, Heroku, etc.). Compare by compute tier, operating system, and architecture.

Containers

Covers two areas: managed container runtimes, including Kubernetes node pools (EKS, AKS, GKE) and serverless container platforms (Fargate, Cloud Run, ACI); and container registries (ECR, ACR, Google Artifact Registry). Filter by service type, orchestrator, architecture (x86 or ARM), and billing granularity.

Databases

Covers managed relational, NoSQL, and in-memory database services (RDS, Azure SQL, Cloud SQL). Filter by database family, engine, deployment type (Single AZ, Multi-AZ, Serverless), and HA mode.

Data & Analytics

Covers managed data warehouse and analytics services (Redshift, BigQuery, Synapse, Snowflake, Databricks, and native cloud-provider offerings). Filter by engine, deployment type, and service tier.

GPU

Compares GPU accelerator pricing for ML training, scientific computing, and rendering, covering single and multi-GPU configurations. Filter by GPU model (A100, H100, RTX, V100, L4, etc.), GPU count, and system specs (vCPU, memory).

Networking

Compares data transfer, VPC, load balancing, VPN, NAT gateway, and dedicated connection pricing. Supports filtering by service type, connection type, routing, and direction (egress/ingress).

Serverless

Compares function-as-a-service pricing (AWS Lambda, Azure Functions, Google Cloud Functions) alongside integration services like API Gateways, Messaging Queues, Event Buses, and Workflows. Key attributes: supported runtimes, cold start behavior, billing granularity, and memory configuration.

Storage

Compares object, block, and file storage pricing (S3, Azure Blob, GCP Cloud Storage). Filter by storage type, performance tier, redundancy (LRS, ZRS, GRS), and media type.

Virtual Machines

Compares compute instances across providers (EC2, Azure VM, Compute Engine). Filter by operating system, CPU vendor/architecture, GPU support, and instance category (General Purpose, Compute Optimized, Memory Optimized, etc.). Prices are hourly, on-demand, Linux-based unless noted.

⏱️ Time-Series Databases

Specialized databases for time-stamped, sequential data (metrics, sensors, financial ticks, logs). Compare Timestream, Azure Data Explorer, and Bigtable pricing for writes, reads, and storage tiers.

🔗 Graph Databases

Databases optimized for relationships, networks, and complex queries. Compare Neptune, Cosmos DB (Gremlin), and Oracle Graph for social graphs, recommendation engines, and knowledge bases.

🔍 Search Engines

Full-text search, analytics, and log aggregation. Compare OpenSearch, Azure Cognitive Search, and GCP Cloud Search for indexing, querying, and scaling distributed clusters.

🔐 Certificate Management

Public and private certificate authorities, SSL/TLS management, and lifecycle automation. Compare AWS Certificate Manager, Azure Key Vault, and GCP Certificate Authority for managed certificates, private CAs, and auto-renewal.

🤖 Inference Endpoints

Model serving platforms for deploying trained ML models to production. Compare SageMaker, Azure Machine Learning, and Vertex AI for real-time and batch inference pricing (CPU/GPU compute and storage), separate from model training.

↑ Go back to the top

Workloads & Architectures🔗 Copy link

The Workloads page prices complete 24 end-to-end cloud architectures across 5 core categories instead of isolated components. Adjust scale parameters and the engine calculates component requirements and queries the optimal matching SKUs across AWS, Azure, Google Cloud, Oracle, DigitalOcean, and Alibaba Cloud.

Tracked Architectural Groups (24 Total Workloads):

• 🛡️ Middleware & Inter-App: Connective tissue and fallback layers—Serverless Fallback Buffer, AI Gateway & Caching Proxy, Enterprise API & Auth Gateway, and Cross-Cloud Event Router.
• 🧠 AI & Machine Learning: GenAI and vector systems—RAG AI Knowledge Base, LLM Fine-Tuning Clusters, and Real-Time Multi-Modal Inference Pipelines.
• ⚡ Web & Microservices: Core application backends—Serverless Web Application, Classic 3-Tier Web Architecture, and E-Commerce Microservices.
• 🌊 Data Analytics & HPC: High-throughput processing—Real-time Streaming Analytics, Cloud Data Warehouses, Batch ETL, and HPC Clusters.
• 🔐 Networking & Security: Secure backbones—Zero-Trust Edge Gateways, Hybrid Cloud Interconnects, and Warm-Standby Disaster Recovery.

Architecture Priorities

When evaluating a workload, you can dynamically shape its infrastructure by adjusting four key Architecture Priorities based on cloud best practices:

• Capacity: Adjust the baseline compute and storage scale (e.g., from dev-sized environments to high-traffic production clusters).
• Performance: Control the latency and throughput requirements. Higher performance provisions premium caching layers (Redis, Valkey) and high-IOPS storage.
• Reliability: Enhance fault tolerance. Higher settings automatically provision load balancers, multi-AZ database deployments, and automated backup storage.
• Security: Strengthen the architecture's security posture by injecting Web Application Firewalls (WAF), Key Management Services (KMS), and Threat Detection into the cost estimate.

Explore all 24 workloads and customize configurations on the Workloads page.

↑ Go back to the top

Use Cases & Step-by-Step Comparisons🔗 Copy link

These real-world scenarios show how to compare pricing across multiple product categories, apply filters, and export results for decision-making.

Use Case 1: Evaluating Database + Compute for a Scaling Startup

Scenario: You're running a SaaS product with a PostgreSQL database and API servers. You want to compare cost-effective options for both components as your user base grows from 1,000 to 5,000 concurrent users.

Steps:

1. Start on the Databases tab. Click Databases at the top of the page.
2. Filter for managed relational databases. In the left sidebar:
   • Select Engine: PostgreSQL to narrow to your database type.
   • Select HA Mode: Multi-AZ to ensure high availability.
   • Set Memory: 8–32 GB to match a medium-sized production database.
   • Keep Geography: All to see global options.
3. Note the top 3 providers by hourly price (typically AWS RDS, Azure Database, or Google Cloud SQL).
4. Switch to Virtual Machines tab. Now compare compute instances for your application servers.
5. Filter for balanced compute. In the sidebar:
   • Select Category: General purpose.
   • Set vCPU: 2–4 and Memory: 8–16 GB.
   • Select Geography: US East to match your database region.
6. Export or screenshot results. You now have a side-by-side cost table for all major providers. Use this to calculate total monthly cost: (Database hourly price + Compute hourly price per instance × 2–3 instances) × 730 hours/month.

💡 Tip: Repeat this comparison at 5,000 and 10,000 concurrent users by increasing vCPU/memory filters. You'll see how scaling costs differ across providers — some remain linear, while others show volume discounts or better pricing at larger sizes.

Use Case 2: Multi-Region Disaster Recovery Architecture

Scenario: You need to set up a disaster recovery (DR) backup in a different geographic region. You want to compare both primary and backup region costs across Storage (for backups) and Networking (for data replication).

Steps:

1. Start on the Storage tab. Click Storage at the top.
2. Filter for object storage. In the left sidebar:
   • Select Type: Object Storage (S3-equivalent).
   • Select Geography: US East for your primary region.
3. Record storage pricing per GB/month. Note the cost for your expected backup volume (e.g., 500 GB).
4. Switch filters to Geography: EU West (your DR region) and repeat. Compare how storage costs differ.
5. Switch to Networking tab. Now estimate data transfer costs for replication.
6. Filter for inter-region data transfer. In the sidebar:
   • Look for rows mentioning Data Transfer Out (Intercontinental) or Data Transfer Between Regions.
   • These typically cost $0.02–0.05 per GB, depending on direction and provider.
7. Calculate monthly DR cost: (Primary storage + DR storage + daily replication volume × 30 days × data transfer rate).
8. Export or create a spreadsheet with your calculations and share with your team for decision-making.

💡 Tip: Use the Aggregate View toggle (in the toolbar) to collapse results by instance type and see min/max/avg pricing. This makes it easier to spot which provider offers the best value across regions.

Use Case 3: Containerized Workload Scaling on Kubernetes

Scenario: You're migrating a Docker-based application to Kubernetes and need to compare the per-node cost of different providers' managed Kubernetes services (EKS, GKE, AKS, DOKS, OKE).

Steps:

1. Start on the Containers tab. Click Containers at the top.
2. Filter for Kubernetes node pools. In the left sidebar:
   • Select Type: Kubernetes (or look for EKS, GKE, AKS, OKE, DOKS).
   • Set vCPU: 4 and Memory: 16 GB (a typical mid-size node).
   • Select Geography: US East.
3. Note the per-node hourly cost for each provider. This is what you'll pay for each Kubernetes worker node.
4. Check for hidden costs. Managed Kubernetes services often add control-plane charges:
   • AWS EKS: +$0.10/cluster/hour (control plane).
   • Azure AKS: Free control plane (included).
   • Google GKE: Free control plane for one cluster, then charges apply.
5. Calculate cluster cost: (Control plane fee + per-node cost × number of nodes) × 730 hours/month.
6. Compare across node sizes. Re-apply filters for 2-vCPU (dev clusters) and 8-vCPU (production) to see how pricing scales.
7. Create a comparison sheet with dev, staging, and production cluster costs for each provider.

💡 Tip: Also check the Serverless tab for Cloud Run / Fargate / App Engine if you're considering a serverless container approach. Many teams find these cheaper than managing Kubernetes clusters for variable workloads.

↑ Go back to the top

Bring Your Estimate🔗 Copy link

Every comparison above starts from a blank slate — you pick a category, set filters, and read prices. Bring Your Estimatestarts from what you already have: upload a cost estimate exported from a provider's pricing calculator (or a quote your sales rep sent), and it maps each line item to its closest equivalent on the other clouds.

It is free and open during the preview — no account, no activation code. We are using the preview to calibrate match quality against real estimates, so telling us where a match was wrong is genuinely useful. Uploaded files are parsed in memory and never written to disk or stored.

Match confidence

Not every workload has a true equivalent on every cloud, and pretending otherwise would make the numbers useless. Each matched line item carries a confidence rating:

• Exact — identical vCPU and memory, same operating system. Directly comparable.
• Close — same vCPU count, memory within 25%. Equivalent performance, minor spec difference.
• Approximate — the nearest available service, with meaningful architectural differences. Azure SQL Hyperscale against Amazon RDS is a good example: both are managed SQL, but storage architecture and scaling behavior differ.
• Low confidence — we found a price, but only by relaxing something you specified. Most often the region: we price a set of major hubs live, so a Windows workload in West Europe may be priced from a US region instead. Every low-confidence row states exactly what was substituted.

One substitution we never make is the operating system. Windows carries licensing cost that Linux does not, so pricing a Windows workload from a Linux SKU would understate your bill rather than approximate it — that is a wrong answer, not a low-confidence one.

What gets excluded, and why your totals differ

Support plans, provider-specific licensing, and proprietary managed services have no cross-cloud equivalent by definition. These are flagged as "provider-only, no equivalent" and excluded from comparison totals — along with any line whose specifications could not be read from your file.

You will therefore see three separate figures: comparable spend (the lines that matched), excluded spend, and your full estimate total. Excluded items stay visible in the table so nothing from your original estimate disappears, but counting them against a provider that does not sell them would distort the comparison.

For the same reason, when a provider matches only part of your estimate, any savings figure is calculated against what those specific workloads cost you today — never against your full spend. Each provider row shows how many of your workloads it covers.

The Specialized Catalog behind it

Matching at this level needs more than a category average. The Specialized Catalog indexes every instance we track by what it actually is — vCPU, memory, operating system, region — so your workload is matched on what it runs, not on which bucket it falls into. You can see its size and freshness on the Status page.

Bring Your Bill

Bring Your Bill applies the same engine to an actual invoice rather than an estimate — same matching, same confidence ratings, same exclusions. It is in development; the pricing catalog behind it is already built.

Important:results are directional estimates based on public list pricing, not quotes. They exclude negotiated discounts (AWS EDP, Azure EA), reserved and committed-use pricing, taxes, and egress. Verify against each provider's official calculator and your account team before making migration or purchasing decisions.

↑ Go back to the top

Datacenters🔗 Copy link

The Datacenters page compares the global physical footprint of each cloud provider side by side, independent of pricing, to help teams evaluate geographic reach, redundancy, and regulatory coverage.

Unlike the pricing categories, this page does not connect to a live database; data is sourced manually from each provider's official infrastructure pages and verified periodically.

Data sources

Each figure on the page — region count, Availability Zone count, edge locations, countries served, and government cloud regions — is drawn directly from the provider's own published documentation:

• AWS — AWS Global Infrastructure, Regions & Availability Zones
• Azure — Azure Global Infrastructure, Azure Geographies
• Google Cloud — Google Cloud Locations, Google Network Infrastructure
• Oracle Cloud — OCI Cloud Regions, OCI Infrastructure
• DigitalOcean — Regional Availability
• Alibaba Cloud — Alibaba Cloud Global Infrastructure
• Cloudflare — Cloudflare Global Network

Source links are also reproduced at the bottom of the Datacenters page itself, grouped by provider.

Accuracy & freshness

Infrastructure figures change frequently as providers expand. Counts shown on the page reflect a manually verified snapshot — the "Last verified" date is displayed at the bottom of the Datacenters page. Key caveats:

• Announced regions are regions the provider has publicly committed to launching but that are not yet generally available. They are marked with an amber indicator and shown as "Planned" in expanded rows.
• Edge locations (CDN/PoP nodes) are approximate — providers use different terminology and update counts frequently. Figures are rounded.
• Government cloud regions may have restricted access and are not always open to all customers. Counts refer to publicly announced dedicated compliance regions.
• Region coordinates on the world map are approximate and intended for geographic orientation only, not precise geolocation.

Important: Always verify current infrastructure availability directly with the provider before making architecture or compliance decisions.

↑ Go back to the top

Compliance & Regulations🔗 Copy link

The Compliance & Regulationspage compares each provider's security, privacy, industry, and government certifications side by side, independent of pricing. It covers standards such as ISO 27001/27017/27018/27701/22301/20000-1/42001, SOC 1/2/3, PCI DSS, HIPAA, FedRAMP High/Moderate, CSA STAR, FIPS 140-2, HITRUST, NIST 800-171, GDPR, IRAP, C5, ENS, MTCS, and ISMAP.

Like the Datacenters page, this data is curated manually from each provider's official compliance documentation rather than a live database. A missing certification means it wasn't found in that provider's published docs at verification time, not that it's unavailable.

The page tracks a curated set of widely-recognized standards for side-by-side comparison; it is not exhaustive. The largest clouds hold far more (AWS advertises 140+ certifications, Azure 100+). For a provider's complete catalog, use its trust center, linked at the bottom of the Compliance page.

Filters

Tiles are provider-centric — each provider shows the certifications it holds, with every certification name linking to a definition of the standard. Three filters narrow the view:

• Provider — limit the tiles to specific providers.
• Region — uses the same geography buckets as the pricing pages; regional standards (e.g. IRAP, C5, ENS, MTCS) appear only when their jurisdiction is selected, while globally recognized standards always show.
• Certification — a cross-filter: selecting one or more certifications disables any provider that lacks them, answering questions like "which providers qualify for FedRAMP High?"

Accuracy & freshness

Compliance status changes rarely (roughly annually), so the matrix is re-verified against each provider's official compliance page about every six months. The "Last verified" date and the per-provider source links are shown at the bottom of the page. Key caveats:

• Certification names link to a definition of the standard (Wikipedia or the standard body); the provider's own compliance page — linked at the bottom of the page — is the source of truth for who holds what.
• Some entries are intentionally conservative — where a provider's page did not clearly confirm a certification, it is left off rather than assumed.

Important: This page is for general comparison only and is not legal or compliance advice. Always confirm a provider's current certifications directly with the provider before relying on them.

↑ Go back to the top

Pricing Data🔗 Copy link

Data sources

Pricing data is fetched automatically on a weekly basis from each provider's public pricing APIs and pages. When a live fetch fails, the tool falls back to a curated static configuration that is updated manually.

All prices are on-demand (pay-as-you-go) in USD. Discounted rates that depend on a commitment, a contract term, or an upfront payment are not included.

Every row records where its price came from. The Status page shows the split per provider and category — how much is fetched live from a provider API versus served from static fallback — along with when each pipeline last ran. Rows sourced from fallback are labeled Static there. Coverage is not uniform across providers, and the Status page is the honest picture of it at any moment.

Exports

Comparison tables can be exported as CSV. Exported files are point-in-time snapshots — they do not update after download, and provider pricing changes frequently, so a file becomes stale quickly.

Each export ends with a disclaimer footer covering what the figures exclude (negotiated discounts, reserved and committed-use pricing, taxes, egress) and stating that they are directional estimates rather than quotes. Please keep that footer attached if you share or forward the file — exported numbers separated from it lack the context needed to read them correctly. See the Terms of Use for the full position on exported data.

Normalization

To enable apples-to-apples comparisons, all prices are normalized to a common unit — typically USD per hour. Resource specs (vCPUs, RAM, GPU count) are standardized across providers where definitions differ (e.g. Oracle OCPUs vs vCPUs).

Price Trends

The application tracks historical price changes across ingestion runs. When viewing the pricing tables, you will see an indicator next to the price: a red up arrow (▲) if the price increased, a green down arrow (▼) if the price decreased, or a grey dot (●) if the price remained unchanged. This allows you to quickly spot pricing shifts and volatility across cloud providers.

Accuracy & freshness

Prices are directional and intended for high-level comparison only. Always verify final pricing on the official provider calculator before making purchasing decisions.

Comprehensive Coverage & Missing Services: This is not a comprehensive catalog of every provider offering. We consolidate data in good faith from public pricing pages and APIs, but may omit some services, instance types, or categories. If you spot something missing or misrepresented, reach out and we'll fix it.

The data here is a directional indicator — a sample of popular instances to highlight architectural cost differences — not a substitute for an official quote. Verify final estimates with the official calculators or pricing pages:

• AWS Pricing Calculator
• Azure Pricing Calculator
• Google Cloud Pricing Calculator
• Oracle Cloud Cost Estimator
• DigitalOcean Pricing
• Alibaba Cloud Pricing Calculator
• Cloudflare Workers Pricing
• OpenAI API Pricing
• Anthropic Pricing
• Pinecone Pricing
• Qdrant Pricing
• Zilliz Cloud (Milvus) Pricing
• Weaviate Pricing
• Chroma Pricing

Not every provider above publishes an interactive calculator — for those (Cloudflare, and the vector database providers), the link goes to their official pricing page instead.

Disclaimer: Price data may be delayed, incomplete, or imprecise. comparecloudcosts.com makes no warranties regarding accuracy. See our Terms of Use for full details.

↑ Go back to the top

Public API🔗 Copy link

The same pricing dataset behind the dashboard is available as a versioned, key-authenticated API for scripts, internal tools, and third-party integrations — GET /api/v1/pricing. It accepts the same filter parameters as the dashboard (provider, geography, category, vCPU/memory range, search, etc.) and returns the matching pricing records as JSON.

This is separate from the internal /api/pricing endpoint the dashboard itself calls, which stays unauthenticated and is not a stable contract — build against /api/v1/pricing instead.

Authentication

Every request must include an X-API-Key header. Keys are issued manually — email [email protected] with what you're building and expected volume. A missing or invalid key returns 401.

Tiers & rate limits

Every response carries X-RateLimit-Limit and X-RateLimit-Remaining headers. Exceeding your limit returns 429 until the next hour boundary (UTC).

Example request

curl "https://comparecloudcosts.com/api/v1/pricing?product=compute&provider=aws,azure&minVcpu=4" \
  -H "X-API-Key: ccc_live_your_key_here"

Same directional-pricing caveats as the rest of the site apply — see Pricing Data → Accuracy & freshness above and the Terms of Use.

↑ Go back to the top

Filters🔗 Copy link

Users have the ability to filter every product category on the platform — narrow results by provider, region, specs, price, and category-specific attributes to zero in on exactly the comparison you need. To see these filters applied in a real, multi-category workflow, check out the Use Cases & Step-by-Step Comparisons section above.

Provider

Checkbox list to include or exclude specific cloud providers (AWS, Azure, GCP, Oracle, DigitalOcean, Alibaba Cloud, and category-specific providers like OpenAI, Anthropic, Cloudflare, or the vector database providers). Multi-select — narrow to one provider or compare a custom subset.

Geography

Filters results to regions within a geographic area (N. America, W. Europe, Asia Pacific, etc.). Multi-select — choose one or more.

Specs & Price

Sliders to filter by vCPU count, memory (GB), and hourly price ($). Drag the handles inward to apply a range filter. Sliders at their outer limits apply no filter.

Search

The search box at the top of the table filters by instance type name or description.

Aggregation

Toggle Aggregate View in the toolbar to collapse results by instance type across providers, showing min/max/avg pricing instead of individual region rows.

Category-Specific Filters

Beyond the universal filters above, each product category exposes its own additional attribute filters in the sidebar — for example, GPU and CPU vendor for Virtual Machines; Database Engine, Deployment type, and High-Availability mode for Databases; Context Window and Multimodal support for AI & Machine Learning; Cold Start, Timeout, and Execution Model for Serverless; Orchestrator and Architecture for Containers; Connection Type, Routing Type, and Direction for Networking; and Redundancy and Media type for Storage. See the Product Categories section above for what each category covers.

↑ Go back to the top

Sharing🔗 Copy link

Use the Share buttons in the top bar to share a link to the tool on X (Twitter) or LinkedIn.

↑ Go back to the top

Advertising with Us🔗 Copy link

Compare Cloud Costs puts your brand in front of engineers and architects actively comparing cloud pricing, at the moment they're deciding what to buy.

Sponsorship slots are available on individual workload pages, and your brand also appears on the Datacenters page, the Workloads catalog, inside the CSV export for your sponsored page, and on our Sponsors page. Each placement includes your logo, a short description (up to 500 characters), and a link to your page or product.

Image Specs

All sponsor placements use a single shared banner spec, so one asset works across every slot:

• Dimensions: 1200 × 200px (6:1 aspect ratio)
• Retina asset: 2400 × 400px recommended
• Format: PNG, JPG, or WebP
• Images render responsively (scaled to the container width, aspect ratio preserved), so avoid placing critical text near the edges.

This is close to LinkedIn's Company Page cover image ratio (1128 × 191px, ~5.9:1), so an existing LinkedIn banner will likely need only minor cropping.

💡 Tip: Your banner can include a call to action toward a landing page or your main site. You can swap it for a new one at least once a month; send us the replacement asset and we'll have it live within 3 business days.

Link Tracking

We do not offer native click-through rate (CTR) tracking. Sponsors provide their own trackable destination links (UTM parameters, Bitly, or other redirect services) to measure campaign performance.

Sponsorship Exclusivity

We apply different levels of exclusivity depending on the page you sponsor, so your visibility isn't cluttered by competing offerings:

• Individual Workload Pages (Exclusive): Sponsoring a specific workload (e.g., a three-tier web application) makes that space exclusive to you; we won't allow a direct competitor on the same page.
• Global Pages (Shared / Carousel): On high-traffic pages like Workloads, Compliance, and Datacenters, sponsor banners rotate in a carousel and may feature multiple sponsors.

Sponsorship in CSV Downloads

CSV downloads from a workload page include a header with the workload name, timestamp, and pricing model. Sponsored workloads show the sponsor's name and a link; unsponsored ones show sponsorship info instead.

This gives sponsors brand exposure at download time, while unsponsored workloads serve as a soft call-to-action for potential sponsors.

Site Analytics & Tracking

We use Microsoft Clarity to track page views, engagement, click patterns, and device/browser data, helping us understand audience behavior and sponsor placement performance. All analytics are anonymized and aggregated; individual user data is never shared with sponsors.

Our Sponsors page shows high-level audience metrics, traffic volume, user roles, geographic distribution, engagement depth, and platform breakdown to help you evaluate sponsorship ROI.

Prices

Choose the tier that fits your goals and budget:

Note on premium capabilities: Bring Your Estimate and Bring Your Bill are currently free and open to everyone during the preview — no account or code required. The seat allocations in the higher tiers below apply once these features become generally available. Sponsoring today is support for keeping the pricing data free and independent; the premium seats are a benefit that begins at general availability, not a paywall you are buying past.

• $9.99/month or $99/year
  • Have your brand in a workload page
  • Inclusion on the sponsors page
• $12.99/month or $119/year
  • Have your brand in a workload page
  • Inclusion on the sponsors page
  • Ad carousel placement on the main workload page
• $15.99/month or $149/year
  • Have your brand in a workload page
  • Inclusion on the sponsors page
  • Ad carousel placement across the main workload, compliance, and datacenter pages
  • Access to premium capabilities for 1 user once they become generally available (free to everyone during the current preview)
• $19.99/month or $189/year
  • Have your brand in a workload page
  • Premium placement on the sponsors page
  • Ad carousel placement across the main workload, compliance, datacenter, and main blog post pages
  • A yearly sponsored blog post in https://comparecloudcosts.com/blog
  • Access to premium capabilities for up to 2 users once they become generally available (free to everyone during the current preview)

Interested in sponsoring? Reach out at [email protected].

↑ Go back to the top

Contributing & Feedback🔗 Copy link

The project is open source. Found a bug, missing provider, or incorrect price? Open an issue or pull request on GitHub, or reach out at [email protected].

↑ Go back to the top

Data Dictionary🔗 Copy link

This Data Dictionary provides a comprehensive breakdown of every product category, the specific columns displayed in their comparison tables, and the core definitions of their filters and parameters.

1. Virtual Machines (VM)

General-purpose, compute-optimized, memory-optimized, or accelerator-backed virtual server instances.

2. Databases

Managed relational servers, NoSQL document stores, cache layers, and vector indexes.

3. Serverless

Event-driven Serverless Functions (FaaS) executed on demand.

4. Containers

Managed container control planes (Kubernetes), serverless container runners, and container image registries (repositories for storing and managing container images).

5. Networking

Network routing, load balancing, tunnels, and data transfer egress.

6. Data & Analytics

Cloud data warehouses, streaming analytics, ETL utilities, and lakehouse storage.

7. GPU

Dedicated GPU accelerator instances for machine learning, scientific computing, graphics rendering, and high-performance computing.

8. Storage

Object buckets, VM block storage volumes, shared file systems, and archive tiers.

9. Artificial Intelligence (AI)

GenAI LLM endpoints, embeddings, custom model training nodes, and vector search operations.

10. App Hosting

Fully managed Platform-as-a-Service (PaaS) app runners and app engines.

11. Security & Identity

Firewalls, IAM policies, encryption key management, secrets management, and runtime threat detection.

12. Integration

Managed message queues, publish-subscribe brokers, API gateways, event buses, and serverless workflow orchestrators.

13. Time-Series Databases

Optimized databases for timestamped, sequential data at scale (metrics, sensors, financial data).

14. Graph Databases

Specialized for relationships, networks, and complex traversal queries (social graphs, recommendations, knowledge bases).

15. Search Engines

Full-text search, log aggregation, and analytics (Elasticsearch/OpenSearch clusters or managed search).

16. Certificate Management

Public and private SSL/TLS certificate lifecycle management, CAs, and auto-renewal.

17. Inference Endpoints

Model serving platforms for deploying trained ML models to production (real-time and batch predictions).

↑ Go back to the top

Glossary🔗 Copy link

The following terms are used throughout the platform. Hovering the ⓘ icon next to any term on the Datacenters page will also surface its definition inline.

• Region — A geographic cluster of data centers in a specific physical location. Each region is completely independent and isolated from failures in other regions. Providers typically publish regions as named locations (e.g. "US East (N. Virginia)", "West Europe").
• Availability Zone (AZ) — One or more discrete data centers within a region, each with redundant power, networking, and connectivity. Deploying resources across multiple Availability Zones in the same region allows applications to survive a single data center outage. DigitalOcean does not use traditional Availability Zones — each of its regions maps to a single data center.
• Edge Location — A smaller point-of-presence (PoP) node used for content delivery (CDN) and low-latency services such as DNS, DDoS protection, and WAF. Edge locations are distinct from full compute regions and are not independently deployable as compute environments.
• Government Cloud — Dedicated, isolated cloud regions operated specifically to meet government compliance requirements (e.g. FedRAMP High, IL4/IL5 in the US, UK OFFICIAL). Access is typically restricted to vetted public sector customers.
• On-Demand pricing — Pay-as-you-go pricing with no upfront commitment. Every price on this platform is an on-demand rate. Discounted rates that depend on a commitment, a contract term, or an upfront payment are not included, because they are not comparable across providers.
• vCPU — Virtual CPU. A logical compute unit mapped to a physical processor thread. Oracle Cloud uses OCPUs (one OCPU = 2 vCPUs); this platform normalizes all values to vCPUs for consistency.

↑ Go back to the top