Oracle vs CockroachDB Licensing is the comparison that decides whether your RAC plus Active Data Guard footprint is a competitive necessity or an expensive habit.

What CockroachDB is

CockroachDB is a distributed SQL database designed for global OLTP workloads. It is PostgreSQL wire-compatible, supports serialisable isolation by default, and is built around the concept of distributed range-replicated data with automatic rebalancing. The architectural lineage is Google's Spanner paper, adapted to commodity infrastructure.

For Oracle estates, CockroachDB is the most credible like-for-like alternative to Oracle Database EE plus RAC plus Active Data Guard. RAC delivers active-active inside a single shared-storage cluster; ADG delivers cross-site disaster recovery; CockroachDB delivers both natively without separately-licensed options. For globally distributed workloads — financial services trading systems with operational presence in multiple regions, retail platforms with regional latency requirements, telecoms with active-active national-grid requirements — CockroachDB frequently outperforms RAC because RAC was never architected for cross-region operation.

What CockroachDB replaces in an Oracle estate: Database EE, the RAC option, Active Data Guard, GoldenGate for replication, and a meaningful portion of Partitioning option usage. It is the wrong destination for analytics-heavy workloads (Snowflake or Databricks) and for document-shaped workloads (MongoDB).

Distributed SQL architecture

Three architectural features decide most RAC-replacement comparisons:

• Range-replicated storage with consensus. Data is split into 512 MB ranges, each replicated 3+ ways using Raft consensus. Reads and writes route to the leaseholder replica. Failover is automatic and sub-second; there is no concept of a "primary" or "standby" cluster.
• Multi-region survivability. Survival goals are configured per database: zone survival, region survival, or multi-region survival. A multi-region cluster survives the loss of an entire AWS region without data loss and with no failover orchestration. The equivalent on Oracle requires Active Data Guard far synchronous, custom application logic, and significant operational engineering.
• Native horizontal scale. Adding nodes increases capacity linearly. There is no equivalent to RAC's interconnect bottleneck. Sharding is automatic; the application sees a single SQL endpoint.

The implication for buyer-side TCO: features that Oracle bundles into separately-licensed RAC and Active Data Guard options — at $23,000 per core list each, on top of the base EE licence — are CockroachDB defaults.

Licensing: Core, Enterprise, Cloud

Most enterprise customers run Cloud Dedicated for production. Self-managed Enterprise is the path for regulated estates that cannot use a managed cloud service. Negotiated multi-year commits on Cloud Dedicated typically reduce 20 to 35 percent against on-demand.

Cloud Dedicated and Standard pricing

The single largest TCO variable is right-sizing. We routinely see CockroachDB Cloud Dedicated estates running 20 to 35 percent over necessary because the cluster was sized for projected peak rather than measured peak. A buyer-side capacity review before the next renewal usually pays back the engagement within the first quarter.

Capability comparison with Oracle Database EE + RAC + ADG

Performance, consistency, latency

Three performance characteristics dominate Oracle-to-CockroachDB comparisons:

• Strong consistency by default. Serialisable is the default isolation level. The application gets stronger correctness guarantees than Oracle's read-committed default without buying additional features. For applications that historically required Oracle SERIALIZABLE plus careful locking discipline, CockroachDB simplifies the model.
• Latency in multi-region. Single-region writes are typically 1 to 4 ms; cross-region writes pay one inter-region round-trip latency. Multi-region tables with regional pinning ("home region") let workloads serve reads and writes locally with cross-region replication on the critical path only for high-availability scenarios — a pattern that has no Oracle equivalent without significant operational engineering.
• Throughput. Linear scale-out to thousands of nodes. Industry-published TPC-C results above 1 million tpmC on commodity hardware. For Oracle workloads that historically required exotic RAC hardware to hit throughput targets, CockroachDB delivers comparable throughput on standard cloud compute.

The trade-off: single-row latency on small operations is higher than well-tuned Oracle on Exadata. For workloads that benchmark single-statement latency in sub-millisecond territory, Oracle still wins. For workloads that benchmark steady-state throughput, consistency, and survivability, CockroachDB wins decisively.

5-year TCO worked example

Scenario: 96-core Oracle Database EE workload with the RAC option, Active Data Guard, Partitioning, Advanced Compression, Advanced Security, and Diagnostics Pack. Three-region multi-master deployment serving a global trading platform. Annual run-rate: $4.3M including support.

The 75 percent saving across five years is at the upper end of what we see, driven primarily by elimination of the RAC and ADG options. For Oracle estates that are not licensed for RAC plus ADG, the saving narrows to 50 to 60 percent against base EE — still material but less dramatic.

Migration: SQL, PL/SQL, app changes

Oracle-to-CockroachDB migrations are PostgreSQL-pattern migrations with multi-region wrinkles. Four components:

Schema and SQL. CockroachDB's PostgreSQL compatibility means most Oracle-to-Postgres patterns apply. Tools such as the AWS Schema Conversion Tool, ora2pg, and CockroachDB's own MOLT toolkit auto-convert 70 to 85 percent of typical schemas. Remaining manual remediation covers NUMBER precision, DATE semantics, identity columns, MERGE syntax, and Oracle-specific functions.

PL/SQL. The genuine work, as with any Oracle exit. CockroachDB has limited stored-procedure support relative to Oracle PL/SQL. The pattern is to lift PL/SQL business logic into application services rather than transliterate. SCT-style tooling auto-converts 30 to 50 percent; the rest is manual.

Multi-region design. Where CockroachDB earns its place. Regional table pinning, multi-region survival goals, and follower reads are first-class concepts that need to be designed into the schema. Migrations that ignore this design layer produce CockroachDB clusters that look like single-region Postgres — leaving the multi-region upside on the table.

Application changes. PostgreSQL wire compatibility means most JDBC / .NET / Python drivers work without code changes. The application-level changes are around handling serialisable retry errors gracefully — a one-time engineering investment in retry helpers.

Realistic timeline for a 96-core multi-region Oracle estate: 14 to 22 months end-to-end. Migration cost typically $1.6M to $2.8M depending on PL/SQL volume.

Oracle audit risk during a CockroachDB migration

Cancelling RAC, Active Data Guard, and Oracle Database EE support all trigger LMS engagement letters with predictable regularity. Three vectors:

• RAC option compliance. Historic deployments may have run RAC on more nodes than were ever licensed. Even if RAC is decommissioned, back-licence claims arrive. The buyer-side defence is the documented historical RAC node inventory.
• ADG / standby compliance. Active Data Guard's licensing rules are nuanced — standby uses are sometimes licensed under different metrics. Oracle's playbook is to assert maximal licensing requirements on every standby that ever existed.
• Java SE Universal Subscription. The parallel audit. Java Employee Metric inflates the position dramatically regardless of Oracle Database disposition.

With buyer-side preparation — Effective Licence Position, virtualisation evidence, options usage history filed before the cancellation goes out — outcomes typically settle between 18 and 30 percent of Oracle's opening claim. Without preparation, opening claims of $5M to $25M for mid-market estates are routine.

When CockroachDB is NOT the right answer

Three scenarios where CockroachDB is the wrong destination:

1. Single-region OLTP workloads with no global presence. For workloads that will only ever run in one region, Aurora or AlloyDB is simpler operationally and frequently cheaper. CockroachDB's distributed-SQL upside lives in multi-region. See our Oracle vs Aurora comparison.
2. PL/SQL-heavy estates. CockroachDB's stored-procedure support is not at parity with Oracle PL/SQL or with PostgreSQL plpgsql. For estates with substantial PL/SQL business logic that cannot be lifted into application services, Postgres-compatible engines preserve more investment.
3. Analytics-dominant workloads. CockroachDB is OLTP-oriented. Workloads that are primarily analytical belong on Snowflake or Databricks. See our Oracle vs Snowflake comparison.

For genuinely distributed, multi-region OLTP estates with strong consistency requirements — financial services trading platforms, global retail platforms, telecom subscriber estates — CockroachDB is the strongest like-for-like Oracle Database EE plus RAC plus Active Data Guard replacement on the market.

FAQ — Oracle vs CockroachDB Licensing

What is CockroachDB?

CockroachDB is a distributed SQL database with horizontal scale, multi-region survivability, and PostgreSQL wire-compatibility. It is designed for global OLTP workloads that historically required Oracle RAC plus Active Data Guard plus extensive operational engineering. Data is automatically replicated and rebalanced across nodes; transactions are serialisable by default; survivability can be set at zone, region, or multi-region levels.

How is CockroachDB licensed?

Three commercial paths: CockroachDB Core (BSL community), CockroachDB Enterprise (paid licence with multi-region, change feeds, advanced auth, support), and CockroachDB Cloud (managed service in Dedicated, Standard, and Basic tiers on AWS, Azure, and GCP). Cloud Dedicated is priced per vCPU-hour plus storage and request units; Standard and Basic are usage-based.

Is CockroachDB a credible Oracle RAC replacement?

For most RAC use cases, yes. CockroachDB delivers active-active multi-node operation, automatic failover, and survivability guarantees that exceed RAC for multi-region scenarios. Its consistency model (serialisable) is stricter than RAC's read-committed default. The exception is workloads tightly coupled to RAC-specific features (cache fusion semantics, single-instance latency optimisations).

Does Oracle audit customers who migrate to CockroachDB?

Yes. Non-renewal of Oracle Database EE plus RAC plus Active Data Guard support triggers an LMS engagement letter predictably. Audit vectors are virtualisation compliance, options usage history including RAC option specifically, NUP under-counting, and Java SE Universal Subscription. See our Oracle audit defence guide.

What is the migration timeline?

For a mid-sized multi-region Oracle estate with RAC and ADG: 14 to 22 months end-to-end. PL/SQL is the longest workstream and is typically lifted into application services rather than transliterated. Multi-region design — survival goals, regional pinning, follower reads — needs to be engineered, not lifted-and-shifted.

Does Oracle offer a CockroachDB equivalent?

Oracle's counter-positioning is Globally Distributed Autonomous Database on OCI, or RAC plus ADG plus GoldenGate as a stack. Globally Distributed ADB is technically interesting but priced on the same Oracle commercial model — Universal Credits with options stacking. Benchmark every counter-offer against the CockroachDB 5-year TCO. Counter-offer dynamics are covered in the Oracle negotiation guide.

Independence statement: Oracle Licensing Experts is an independent buyer-side advisory firm. Not affiliated with Oracle Corporation. We have no commercial relationship with Cockroach Labs. All numbers above reflect published pricing and benchmark engagement data.

Related guides