ClickHouse Cloud on AWS Marketplace: how does billing work and is pricing the same as direct?

Buying ClickHouse Cloud through AWS Marketplace gives you the same core service and pricing model as buying direct, but the way you’re billed and how it shows up in your AWS bill is different. The main tradeoff is between consolidated procurement via your AWS account (and any committed spend you’re trying to burn down) and having a direct commercial relationship with ClickHouse for things like custom plans or enterprise contracts.

Quick Answer: ClickHouse Cloud on AWS Marketplace uses the same usage-based pricing model as buying directly from ClickHouse, and workloads are metered in the same way (compute, storage, data transfer, etc.). The biggest differences are where you pay (through your AWS bill vs directly), how discounts and commitments are applied, and how procurement/approvals are handled inside your organization.

Why This Matters

If you’re standardizing on AWS and need ClickHouse Cloud to roll into a single cloud bill, the Marketplace route can simplify procurement, leverage existing AWS Commitments (e.g., EDP), and centralize approvals. If you care more about flexible commercial terms, dedicated support arrangements, or multi-cloud planning beyond AWS, you’ll often prefer buying direct from ClickHouse and connecting to AWS infrastructure that way.

Key Benefits:

• Consolidated billing: All ClickHouse Cloud usage purchased via AWS Marketplace appears on your AWS invoice, which simplifies finance workflows and vendor management.
• Leverage AWS commitments: Marketplace spend usually counts toward AWS committed spend or EDP, helping you avoid leaving prepaid capacity on the table.
• Same ClickHouse experience: You get the same ClickHouse Cloud service—millisecond queries at scale, managed operations, and the same SQL surface area—regardless of whether you buy via Marketplace or direct.

Core Concepts & Key Points

Concept	Definition	Why it's important
Usage‑based pricing	ClickHouse Cloud charges for actual usage: compute (service sizes and uptime), storage (compressed data and backups), and data transfer, similar whether you buy direct or via AWS Marketplace.	Helps you forecast cost based on workloads (ingest rate, query concurrency, retention) rather than seat licenses or opaque tiers.
AWS Marketplace billing	A procurement channel where ClickHouse Cloud charges are routed through your AWS account and show up on your AWS invoice.	Lets you align ClickHouse spend with AWS finance controls, budgets, and enterprise discounts.
Commercial flexibility	The ability to negotiate custom terms, enterprise agreements, and multi-cloud strategy directly with ClickHouse.	Influences whether Marketplace or direct purchase is a better fit, especially for larger or more complex deployments.

How It Works (Step-by-Step)

At a high level, buying ClickHouse Cloud through AWS Marketplace doesn’t change how the database behaves—just how you purchase and how usage is billed.

1. Subscribe via AWS Marketplace:

   • You start by finding ClickHouse Cloud in AWS Marketplace and clicking “Continue to Subscribe” / “Set up your account.”
   • Your AWS account becomes the billing entity for ClickHouse Cloud—Marketplace acts as the reseller.
   • Any required approvals for Marketplace subscriptions (internal or AWS-side) must be completed before you can use the service.

2. Link to ClickHouse Cloud and create services:

   • After subscribing, you’re redirected to ClickHouse Cloud to either create a new organization or link an existing one.
   • You still choose regions, service types, and sizes (e.g., production vs dev services), but the “who pays” is now AWS Marketplace.
   • Operationally, everything looks and feels the same: you use the ClickHouse Cloud console, create databases, manage backups, configure scaling, and connect your applications via standard ClickHouse drivers.

3. Usage metering and billing:

   • ClickHouse Cloud meters your usage exactly as it would for a direct customer:
     • Compute: Based on service size, runtime, and sometimes autoscaling behavior.
     • Storage: Compressed data, replicas, and backups stored in your ClickHouse Cloud services.
     • Data transfer: Egress and sometimes cross-AZ/cross-region movement, depending on configuration.
   • Instead of sending you a direct invoice, ClickHouse forwards usage and charges through AWS Marketplace.
   • Your finance team sees a single line item (or itemized usage, depending on AWS’ invoice detail) under your AWS bill; this can also count toward AWS spending commitments.

Common Mistakes to Avoid

• Assuming pricing is fundamentally different on Marketplace vs direct:

  • Marketplace doesn’t change the core ClickHouse Cloud pricing model—compute, storage, and data transfer are still the main levers.
  • How to avoid it: Plan your capacity and cost based on workload characteristics (ingestion rate, retention, query concurrency), not on the procurement channel. Use the same sizing and cost estimation approach whether you’re going Marketplace or direct.

• Ignoring AWS finance and procurement constraints:

  • Some organizations have strict rules about Marketplace purchases vs direct vendors; others need to burn down AWS commitments.
  • How to avoid it: Before choosing a path, confirm:
    • Whether Marketplace spend counts toward your AWS commitments.
    • Whether your procurement team prefers consolidating under AWS or negotiating directly with ClickHouse.
    • If there are approval workflows or spending limits for Marketplace subscriptions in your AWS account.

Real-World Example

Imagine you’re running a high-cardinality observability backend—logs, metrics, and traces—on ClickHouse Cloud in AWS. You have sustained ingestion, billions of rows per day, and developers relying on sub-second queries for dashboards and AI/agentic workloads.

Your finance team has a large AWS EDP commitment they want to fully consume this year. They also want a single cloud invoice instead of separate vendor bills.

In this scenario:

• You subscribe to ClickHouse Cloud via AWS Marketplace.
• You deploy a production service for logs (large MergeTree tables with compressed storage) and a separate service for real-time analytics and ML features.
• ClickHouse Cloud meters:
  • Compute: Based on the production services running 24/7 with burst capacity for peak ingest and querying.
  • Storage: Your compressed data—potentially petabytes logical, but heavily reduced thanks to ClickHouse’s columnar storage and compression.
  • Data transfer: Egress for dashboards, internal services, and any cross-region data flows.
• All of this appears on your AWS invoice as Marketplace usage, contributing to your AWS committed spend and simplifying your finance team’s view of cloud costs.

Pro Tip: When you’re comparing Marketplace vs direct pricing, benchmark a representative workload first—set up a ClickHouse Cloud service, ingest a realistic data sample, and run your typical queries. Use the resulting usage profile to forecast costs under either procurement path, rather than trying to reason from abstract price lists.

Summary

ClickHouse Cloud on AWS Marketplace gives you the same underlying service—real-time analytics, vector search, and millisecond queries at scale—as buying direct, with a near-identical usage-based pricing model. The main difference is procurement: Marketplace channels your ClickHouse spend through AWS, which can help you consolidate invoices and take advantage of AWS commitments, while direct purchase gives you more flexibility for custom agreements and multi-cloud planning.

Next Step

Get Started