ClickHouse BYOC
Managed analytical database with its data plane in your cloud account.
3 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
ClickHouse unauthenticated network code execution
CVE-2026-116366 is a critical unauthenticated network code-execution issue in affected ClickHouse releases.
Scope: Vendor fixes are 26.3.62.3-lts, 26.8.36.3-lts, 26.9.27.3, and 26.10.3.7. ClickHouse states that its Cloud and BYOC services were patched.
Network reachability to an affected service is required; validate the exact installed release and exposure.
Action: Upgrade self-managed deployments to the fixed release for the selected branch or later, and confirm managed-service patch status.
Primary source · Reviewed 2026-11-18
What lands where
Supplied by
Vendor or project
Vendor-assisted BYOC onboarding
External vendor control plane
Runs in
Documented customer environment
Vendor control plane; customer data plane
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- AWS
- Azure
- Google Cloud
Servers / containers
Operated by
Vendor or service partner
ClickHouse operates the BYOC service; the customer owns the cloud environment.
Deployment boundaries by provider
- AWS: Customer cloud account · Vendor / partner-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
ClickHouse BYOC customer account support ↗ · Source checked 2026-11-12
- Azure: Customer cloud account · Vendor / partner-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
ClickHouse BYOC customer account support ↗ · Source checked 2026-11-12
- Google Cloud: Customer cloud account · Vendor / partner-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
ClickHouse BYOC customer account support ↗ · Source checked 2026-11-12
The vendor describes a fully managed ClickHouse service in the customer's AWS, Google Cloud or Azure account. Commercial availability and access are agreed during onboarding.
Operating responsibility source ↗ · Checked 2026-11-20
Control-plane and data-plane architecture ↗
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Vendor-assisted BYOC onboarding |
|---|---|
| Infrastructure | Servers / containers The documented BYOC data plane uses a customer-cloud Kubernetes cluster and ClickHouse servers. Vendor management of the control plane is separate from this runtime classification. |
| Licensing model | Commercial Only This listing covers the commercially provided managed/BYOC service, not a separately licensed open-source engine or library. |
| License | Commercial |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
8 of 12 fields researched (67%) · 5 documented · 3 unresolved. Evidence coverage is not a feature score.
- Marketplace delivery
AvailableEvidence and scope for Marketplace delivery
Microsoft Marketplace lists ClickHouse Cloud BYOC as a fully managed service deployed into the customer's own Azure account. This is the Azure BYOC offer, separate from vendor-account ClickHouse Cloud.
ClickHouse Cloud BYOC procurement for Azure; confirm private-offer, region and agreement terms. · Source ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- Cloud commitment eligibility
Edition-dependentEvidence and scope for Cloud commitment eligibility
ClickHouse states that its Microsoft Marketplace BYOC offer can count toward Microsoft Azure Consumption Commitments (MACC). Confirm the selected offer and purchase agreement are eligible before procurement; this does not establish AWS or Google Cloud software-commitment eligibility.
Azure BYOC Marketplace purchase only; agreement and offer qualifications apply. · Source ↗ · Azure BYOC Marketplace offer ↗ · Reviewed 2026-11-21
Edition-dependent · Editor reviewed.
- Single sign-on
AvailableEvidence and scope for Single sign-on
The vendor explicitly includes BYOC organizations in its SAML/SCIM availability statement. Configure the organization SAML connection and verified domains; this concerns vendor-hosted organization/control-plane identity, not autonomous authentication for every database client.
Commercial ClickHouse BYOC organization SAML · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Compliance attestations
Not confirmedEvidence and scope for Compliance attestations
The BYOC page states SOC 2 and ISO 27001 alignment but does not provide the assessed service boundary, report or certificate scope for this customer-account deployment. Obtain the applicable evidence before treating it as an attestation.
BYOC marketing statement checked; applicable attestation scope unresolved · Source ↗ · Reviewed 2026-11-14
Sources checked — unresolved · Editor reviewed.
- Security controls
DocumentedEvidence and scope for Security controls
Current advisory review: CVE-2026-116366 is a critical unauthenticated network code-execution issue in affected ClickHouse releases. Upgrade self-managed deployments to the fixed release for the selected branch or later, and confirm managed-service patch status.
Vendor fixes are 26.3.62.3-lts, 26.8.36.3-lts, 26.9.27.3, and 26.10.3.7. ClickHouse states that its Cloud and BYOC services were patched. · Source ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
- Deployment artifact / IaC
Not confirmedEvidence and scope for Deployment artifact / IaC
The public BYOC page establishes personalized vendor onboarding and a customer-cloud data plane, but does not expose a reviewed reusable provisioning artifact. Obtain the region-specific onboarding template, role policy and version from ClickHouse; an open-source ClickHouse Helm chart is a different deployment.
Managed BYOC onboarding; public artifact unresolved · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
The public BYOC offer targets large-scale deployments with vendor onboarding but does not publish a validated minimum CPU/RAM/storage topology. Obtain supported instance types, availability-zone design and workload sizing for the contracted provider and region. Do not substitute open-source single-node minima.
Commercial managed BYOC footprint unresolved · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
ClickHouse provides BYOC rates through its Trust Center after approving an access request. Azure customers can procure the managed BYOC service through Microsoft Marketplace. ClickHouse says purchases can count toward Microsoft Azure Consumption Commitments.
Commercial BYOC pricing access and Azure procurement. Confirm offer terms, region availability, and the applicable commitment with ClickHouse. · Source ↗ · ClickHouse Cloud BYOC offer in Microsoft Marketplace ↗ · ClickHouse announcement of Microsoft Marketplace availability ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
Show all fields (4 not researched)
- SCIM provisioning
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
- Release snapshot / cadence
- Not researched Supply a public source.
Scope & considerations
The vendor lists AWS, Google Cloud and Azure BYOC options. Confirm region availability and commercial requirements during onboarding. This entry does not describe ordinary ClickHouse Cloud hosting. CVE-2026-116366 is a critical unauthenticated network code-execution issue. ClickHouse states that Cloud and BYOC were patched; self-managed fixes are available in 26.3.62.3-lts, 26.8.36.3-lts, 26.9.27.3, and 26.10.3.7.
Category fit
- Databases & vector
- Managed analytical database with its data plane in your cloud account.
Compare within Databases & vector
- Apache Doris Self-HostedApache-licensed analytical database with upstream AWS EKS/Alibaba ACK/ACS guides and a separately packaged cloudimg Azure VM path.
- AWS
- Azure
- Alibaba Cloud
- CockroachDB BYOCVendor-managed CockroachDB service deployed into the customer's AWS, Azure or Google Cloud account.
- AWS
- Azure
- Google Cloud
- Couchbase Server Enterprise EditionSelf-managed distributed NoSQL database deployed in customer-controlled Kubernetes with the Couchbase Operator.
- AWS
- Azure
- Google Cloud
- Elastic Cloud EnterpriseCommercial self-managed orchestration platform for Elastic Stack deployments across customer cloud hosts.
- AWS
- Azure
- Google Cloud
- Elastic Cloud on KubernetesElastic's Kubernetes operator for deploying and operating Elasticsearch, Kibana and related Elastic Stack resources in customer clusters.
- AWS
- Azure
- Google Cloud
- Meilisearch Community EditionSelf-hosted search engine for typo-tolerant full-text, semantic and hybrid retrieval.
- AWS
- Google Cloud
- DigitalOcean
- MilvusVector database for similarity search and retrieval over embedding collections.
- AWS
- Azure
- Google Cloud
- Neo4j Self-ManagedSelf-managed graph database available in open-source Community and commercial Enterprise editions.
- AWS
- Azure
- Google Cloud
Showing 8 of 18 other listings in Databases & vector. These products address related workflows; read their category-fit notes before comparing scope. See all of Databases & vector →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Bring Your Own Cloud ↗clickhouse.com
- Google Cloud BYOC architecture ↗clickhouse.com
- ClickHouse security changelog ↗clickhouse.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- ClickHouse BYOC customer account support ↗ · AWS, Azure, Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor explicitly offers its managed BYOC service in the customer AWS, Google Cloud or Azure account. This establishes provider compatibility for the commercial BYOC offering rather than a generic open-source Docker deployment; agree availability, access, region and operational boundaries with the vendor.
- ClickHouse BYOC customer account support ↗ · AWS, Azure, Google Cloud
- Infrastructure evidenceChecked
- Licensing evidenceChecked