TypeDB Cluster 3.x alpha launch

TypeDB Cluster 3.x alpha 1 marks the first time TypeDB is available in an enterprise-ready format. With high availability and clustered deployment, TypeDB moves beyond single-node operation and into the class of systems designed to support real-world, always-on applications.

This release represents a major milestone in TypeDB’s evolution, as the platform transitions from research innovation to mature infrastructure suitable for commercial, enterprise, and government use. It aligns with the fact that TypeDB is already being deployed in environments where reliability, continuity, and data correctness are operational requirements rather than optional features.

What this release provides

TypeDB is often used as a system of record, where correctness and continuity are both required. This leads to additional core production requirements:

• Always on The database must remain available during machine failures, maintenance, and software upgrades.
• Consistency Writes must be applied atomically. Users should never see partial results or inconsistencies caused by failures, retries, or replication delays.

This alpha release introduces high availability for TypeDB through a clustered, strongly consistent deployment model. The cluster maintains TypeDB’s ACID guarantees while running across multiple nodes:

• Designed for production deployment The cluster provides the foundations required for running TypeDB in environments that expect uptime, fault tolerance, and predictable behaviour.
• Distributed but predictable Strong consistency and ACID guarantees ensure that the system behaves the same way as a single-node TypeDB, even though it is distributed.
• Operational simplicity High availability is exposed through a simple, unified interface. Applications connect to the cluster as a single system, without needing to handle replication or failover logic.
• ACID-compliant and strongly consistent Transactions remain atomic, isolated, and durable even when running across multiple nodes.

TypeDB Cluster is designed to meet these requirements without relying on eventual consistency.

The foundation of TypeDB Cluster

TypeDB Cluster provides high availability by distributing TypeDB across multiple servers while preserving its transactional model.

• ACID across nodes The cluster maintains TypeDB’s ACID properties in a distributed environment.
• Strongly consistent replication Data is replicated between nodes using the Raft consensus protocol, ensuring that all committed transactions are applied in the same order on all replicas.
• Cluster management Nodes can be added to or removed from a running cluster. Increasing the number of nodes increases the system’s fault-tolerance and availability.
• Driver support TypeDB drivers support automatic node discovery and failover, so applications can connect to the cluster without manual configuration.

Launch status and roadmap

TypeDB Cluster 3.x is released as alpha to indicate its status as a validation release.

With the core coordination mechanisms in place, the current focus is on exercising the system under real-world conditions, including network partitions, node failures, and recovery workflows. This phase ensures that the cluster behaves predictably when stressed and that its consistency and availability guarantees remain visible and verifiable to operators.

In parallel, performance and scalability are being optimised, and operational tooling is being refined. This release is intended for evaluation, testing, and early adoption, and it reflects the full architectural direction of TypeDB Cluster as it moves toward a production-ready release.

General notes and summary

TypeDB Cluster allows teams to use the full expressivity of TypeDB without having to compromise on how their systems are run in practice.

Users can model, query, and reason over complex data in the same way they do with TypeDB Core, while relying on a deployment that is highly available, fault tolerant, and suitable for always-on applications. The cluster handles replication, failover, and node management so applications and operators do not need to.

The result is a system that is both powerful to build with and reliable to operate: a knowledge database that fits naturally into production environments without adding operational or development complexity.