> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cockroachlabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Editions and Add-Ons

export const InternalLink = ({version, path = "", children, ...props}) => {
  let detectedVersion = version || "stable";
  if (typeof window !== 'undefined' && !version) {
    const match = window.location.pathname.match(/\/docs\/([^/]+)/);
    if (match) {
      detectedVersion = match[1];
    }
  }
  const normalizedPath = path.startsWith("/") ? path.slice(1) : path;
  return <a href={`/docs/${detectedVersion}/${normalizedPath}`} {...props}>
      {children}
    </a>;
};

Cockroach Continuum offers CockroachDB in *editions*, cluster plans that set infrastructure, availability, and feature boundaries. [*Add-ons*](#add-ons) enable additional capabilities on a cluster.

There is no separate purchase step for an add-on: when you use an add-on feature, it appears as a line item on your bill for the time it's active.

## Editions

The editions differ first in infrastructure. *Shared* infrastructure serves clusters from multiple organizations. *Dedicated* infrastructure is provisioned for a single cluster.

Continuum offers two editions:

* *Standard* runs production workloads on shared infrastructure, in single-region or multi-region configurations, with usage-based storage billing and a 99.99% availability SLA.
* *Mission Critical* runs on dedicated infrastructure for workloads that need the highest availability and the full security feature set, with a 99.999% SLA for multi-region configurations and region-level resiliency options. Single-region Mission Critical clusters choose [usage-based](/docs/continuum/plenum-overview) or provisioned storage at creation.

You choose an edition when you create a cluster, and the choice is permanent for that cluster: to change editions, you create a new cluster and move the workload.

### Choose an edition

Choose Standard for workloads that tolerate shared infrastructure and do not need features available only on Mission Critical clusters, such as [CMEK](/docs/continuum/cmek) or [physical cluster replication](/docs/continuum/physical-cluster-replication).

Choose Mission Critical for Tier 0 and regulated workloads, for the strictest recovery objectives, and for any cluster that will host [virtual clusters](/docs/continuum/virtual-clusters).

## Feature reference

To view CockroachDB feature availability by edition and on virtual clusters, refer to [Feature Reference](/docs/continuum/feature-reference).

## Add-ons

Add-ons are not installed or enabled separately. Creating a host cluster, starting physical replication, or creating a changefeed to a sink starts the add-on charge, and stopping use stops it.

Add-ons are scoped to the cluster that uses them, with one exception noted in the below table.

| Add-on                                                                                     | Description                                                                                                                                                                                                                                                                                                                                                                                          |
| ------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Cluster Virtualization                                                                     | Enables a Mission Critical cluster to act as a host for virtual clusters. Chosen at [cluster creation](/docs/continuum/create-a-cluster). Refer to the [virtualization overview](/docs/continuum/virtualization-overview) and [Workspaces](/docs/continuum/workspaces).                                                                                                                              |
| Data Replication (<InternalLink path="feature-availability">Limited Access</InternalLink>) | Enables physical cluster replication between Mission Critical clusters for cluster-level [disaster recovery](/docs/continuum/disaster-recovery-overview). Refer to the <InternalLink version="v26.3" path="physical-cluster-replication-overview">physical cluster replication</InternalLink> documentation.                                                                                         |
| Data Sync                                                                                  | Enables changefeeds to external sinks such as Kafka and cloud storage as part of [integrating](/docs/continuum/integrate-overview) with your stack, and is the one add-on available on Standard clusters. Sinkless changefeeds are not part of the add-on boundary. Refer to the <InternalLink version="v26.3" path="change-data-capture-overview">change data capture</InternalLink> documentation. |
| Advanced Compliance                                                                        | Grants access to the Trust Center. The exception to cluster-level scoping: it applies at the organization level, across the organization's Mission Critical clusters.                                                                                                                                                                                                                                |

## Feature entitlements and license behavior

Feature boundaries are enforced by the database itself through license entitlements.

If a statement requires a feature your cluster's plan does not include, it fails with an error of the following form:

```
<feature name>: this feature is not included in your license. Contact
sales@cockroachlabs.com to learn more.
```

Enforcement behavior:

* Physical cluster replication is checked on both the source and the destination cluster.
* Logical data replication requires the entitlement on both clusters.
* Changefeeds to sinks are gated. Sinkless changefeeds are not.
* The `feature.changefeed.enabled` cluster setting is an independent operator control and is unrelated to license entitlements.
* Several license-gateable features are deliberately included on Standard for PostgreSQL compatibility, including point-in-time restore, row-level security, column-level encryption, changefeeds, and `EXPORT`.
* Clusters without a new-format license, and clusters on older CockroachDB versions, are not subject to entitlement enforcement.

## Billing and metering

Continuum bills in credits. Compute is metered in vCPU-hours.

Storage charges depend on the edition and storage model. Standard clusters use usage-based storage billing. Plenum-backed Mission Critical clusters are billed for physical data stored, while provisioned Mission Critical clusters are billed for provisioned capacity.

Network and backup storage costs are passed through from the cloud provider based on usage.

Add-on charges appear as separate line items on the clusters that use them, for the time the feature is active.

An add-on's charge is a multiplier on the compute rate, applied to the vCPU-hours during which the feature is active. The base compute and each add-on appear as their own invoice lines, so the charge tracks when the feature was in use.

Marketplace billing through AWS and GCP is supported, and new organizations receive free trial credits.

For rates, refer to [Pricing](https://www.cockroachlabs.com/pricing).