CockroachDB BYOC

Vendor-managed CockroachDB service deployed into the customer's AWS, Azure or Google Cloud account.

4 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Vendor-assisted BYOC onboarding using scoped cross-account cloud identity

    External vendor control plane

  2. Operated by

    Vendor or service partner

    Cockroach Labs manages database provisioning, upgrades, backups, monitoring and incidents; the customer owns the cloud account, network and billing boundary.

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.

    CockroachDB BYOC customer-cloud support ↗ · Source checked 2026-11-14

  • 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.

    CockroachDB BYOC customer-cloud support ↗ · Source checked 2026-11-14

  • 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.

    CockroachDB BYOC customer-cloud support ↗ · Source checked 2026-11-14

Cockroach Labs handles provisioning, patching, backups and monitoring in the customer's cloud account. The customer supplies account access, network policy and cloud-resource governance.

Operating responsibility source ↗ · Checked 2026-11-20

BYOC service component locations ↗

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodVendor-assisted BYOC onboarding using scoped cross-account cloud identity
InfrastructureServers / containers
The database data plane runs as persistent compute and storage inside the customer account, while Cockroach Labs operates it through a separate control plane.
Licensing modelCommercial Only
This listing covers the commercial BYOC managed service, not source-code licensing for a separately self-hosted CockroachDB distribution. Cockroach Continuum packages BYOC as a Mission Critical deployment at $1,000 per vCPU per year; the public-preview Cluster Virtualization add-on is $200 per host-vCPU per year. Existing pre-Continuum organizations retain current pricing and support until a migration path is available.
LicenseCommercial CockroachDB BYOC service.

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.

5 of 12 fields researched (42%) · 4 documented · 1 unresolved. Evidence coverage is not a feature score.

Cloud commitment eligibility
DocumentedEvidence and scope for Cloud commitment eligibility

The BYOC product page says customer-account infrastructure can use applicable committed-use discounts or reserved instances. This does not establish that Cockroach Labs software charges decrement a particular cloud commitment.

Customer cloud infrastructure discounts; software/service billing eligibility is separate · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

Single sign-on
AvailableEvidence and scope for Single sign-on

The vendor documents Cloud Organization SSO using SAML or OIDC with a customer IdP, enforcement and domain restrictions. A BYOC cluster belongs to that managed organization. This is vendor-hosted Cloud Console identity; SQL-user federation and DB Console policies are separately configured.

Commercial Cloud organization identity used with BYOC; database-client identity separate · Source ↗ · BYOC organization and cluster boundary ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The AWS onboarding guide publishes customer-account role/trust and lifecycle permission policies, then provisions the managed cluster through Cloud Console or API. Vendor documentation also lists Terraform creation. Use the BYOC-specific role and account preparation; self-hosted CockroachDB manifests are a different deployment.

Vendor-operated Continuum BYOC AWS onboarding artifacts and API path · Deployment artifact ↗ (Current Continuum onboarding policies; agree account/region and supported service version) · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing

The BYOC overview requires a customer-sized Mission Critical cluster, cloud quotas and continuous lifecycle permissions. It does not establish a single minimum CPU/RAM/storage/zone topology for 100 users and 1 TB. Select workload concurrency, provisioned storage, regional availability and failure headroom with Cockroach Labs before requesting capacity.

Continuum managed BYOC workload sizing; complete numerical footprint unresolved · Source ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

Continuum Mission Critical BYOC is USD 1,000 per vCPU per year, metered by the minute, with premium support. The public-preview Cluster Virtualization add-on is USD 200 per host-vCPU per year on AWS and Google Cloud. Invoice billing and per-organization enablement are required. Customer cloud infrastructure is billed separately. Pre-Continuum organizations keep their existing pricing/support until migration is available.

CockroachDB BYOC on Continuum commercial service charges, not a total operating estimate or pricing for separately self-hosted CockroachDB. Public-preview host/virtual clusters are excluded from availability SLAs. · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Show all fields (7 not researched)
Marketplace delivery
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
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

This entry covers CockroachDB BYOC on Cockroach Continuum, not ordinary fully managed CockroachDB Cloud or customer-operated self-hosting. BYOC is a Mission Critical deployment in AWS, Azure, or Google Cloud, priced at $1,000 per vCPU per year, with premium support and 99.99% single-region or 99.999% multi-region SLAs. Cluster Virtualization is a $200 per host-vCPU per year public-preview add-on on AWS and Google Cloud; dedicated and virtual clusters are excluded from the availability SLA during preview. Existing BYOC organizations created before Continuum keep their current pricing and support until an account-team migration path is available. Invoice billing and per-organization enablement are required.

Category fit

Databases & vector
Provides a managed distributed SQL database whose data-plane resources run inside the customer's 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
    Customer-operated · Open Source / Open Core
  • ClickHouse BYOCManaged analytical database with its data plane in your cloud account.
    • AWS
    • Azure
    • Google Cloud
    Vendor-operated BYOC · Commercial Only
  • Couchbase Server Enterprise EditionSelf-managed distributed NoSQL database deployed in customer-controlled Kubernetes with the Couchbase Operator.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Elastic Cloud EnterpriseCommercial self-managed orchestration platform for Elastic Stack deployments across customer cloud hosts.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • 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
    Customer-operated · Source Available
  • Meilisearch Community EditionSelf-hosted search engine for typo-tolerant full-text, semantic and hybrid retrieval.
    • AWS
    • Google Cloud
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • MilvusVector database for similarity search and retrieval over embedding collections.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Neo4j Self-ManagedSelf-managed graph database available in open-source Community and commercial Enterprise editions.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core

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

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • CockroachDB BYOC customer-cloud support ↗ · AWS, Azure, Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.

      Cockroach Labs explicitly offers BYOC in the customer's AWS, Azure or Google Cloud account. The vendor operates database services using scoped cross-account identity while the customer retains the cloud account and data-plane boundary.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory