LLM.coPrivate, self-hosted LLMs & custom AI applications.
Automatic.coAI-powered workflow & business process automation.
RMA.aiAI-powered cybersecurity monitoring, threat detection & defense.
VB.coOperating AI™ — one intelligent layer for middle-market ops.
LAW.co
RFP.co
Search.co
VDR.aiydb
YDB is an open-source distributed SQL database designed for high-availability, scalable workloads. It combines ACID transactions with strict consistency across multiple nodes, supporting both row and column storage, and offers PostgreSQL and Kafka-compatible modes for easier integration.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | ydb-platform/ydb |
| Owner | ydb-platform |
| Primary language | C++ |
| License | Apache-2.0 — OSI-approved |
| Stars | 4.7k |
| Forks | 793 |
| Open issues | 5.1k |
| Latest release | 26.1.1.20 (2026-07-02) |
| Last updated | 2026-07-08 |
| Source | https://github.com/ydb-platform/ydb |
What ydb is
YDB is a C++ distributed DBMS with disaggregated storage and compute layers, fault-tolerant configuration across availability zones, and automatic disaster recovery. It supports ACID multi-node transactions, horizontal scaling to 10,000+ nodes, and row/column table formats with a rich SQL dialect (YQL).
Get the ydb source
Clone the repository and explore it locally.
git clone https://github.com/ydb-platform/ydb.gitcd ydb# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Requires C++ build toolchain and Ya Make build system; consult BUILD.md for compilation steps. Minimal 8 GB RAM per node.
- Deployment on Ubuntu Linux is standard production path; MacOS and Windows support is for development only.
- Three deployment methods: Ansible (bare metal/VMs), Kubernetes (containers), or manual. Kubernetes path is production-ready; manual deployment increases operational burden.
- Multi-zone setup (3+ datacenters recommended) for fault tolerance; single-node clusters suitable only for development and functional testing.
- PostgreSQL-compatible mode and Kafka-compatible mode available but require explicit enablement and testing against your application driver/producer expectations.
When to avoid it — and what to weigh
- Simple Single-Node or Single-Region Database — YDB's complexity (multi-zone failover, distributed transactions) adds overhead for small deployments. Traditional RDBMS or simpler stores are more appropriate.
- Team Lacks Distributed Systems Expertise — Deployment, configuration, and operational tuning of a distributed DBMS requires deep knowledge of cluster management, consistency guarantees, and failure scenarios.
- Need for Immediate Hands-On Vendor Support — Community-driven project with no clear SLA or commercial support offering documented in public repo. Support channels are Discord/Telegram; enterprise support model is unknown.
- NoSQL Document Store or Graph Database Requirement — YDB is SQL-focused (row/column tables and queues). If your workload requires document storage, key-value pairs, or graph traversal, other systems are better suited.
License & commercial use
Apache License 2.0 (Apache-2.0). Permissive OSI-approved open-source license allowing use, modification, and distribution for commercial purposes, subject to attribution and indemnification clauses.
Apache-2.0 is a permissive license generally compatible with commercial use without royalty or attribution requirements at runtime. However, no formal commercial support package, SLA, or vendor-backed indemnification is evident in public repo. Enterprise deployments should conduct legal review and evaluate community support sufficiency before production commitment.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Strong |
| License clarity | Clear |
| Deployment complexity | High |
| DEV.co fit | Good |
| Assessment confidence | High |
Not explicitly detailed in provided README excerpt. Operational security in distributed systems requires careful network segmentation, authentication (TLS for inter-node and client-server), and access control policies. Multi-tenant and serverless isolation is claimed but requires independent security audit. Hardware failure recovery and data redundancy are integral; cryptographic at-rest encryption coverage is unknown and requires review. Community-driven project means no formal security audit vendor or SLA.
Alternatives to consider
CockroachDB
Similar distributed SQL architecture with ACID transactions and fault tolerance; stronger commercial backing and support model. Go-based, often simpler operational model than C++.
Vitess (MySQL-flavored) or Citus (PostgreSQL extension)
If PostgreSQL ecosystem lock-in is strong, these provide distributed scaling with sharding/partitioning; less deep consistency model than YDB but proven in production at scale.
ClickHouse (for analytics) or Cassandra (for high-write OLTP)
If workload is purely analytical (ClickHouse) or eventual-consistency OLTP (Cassandra), these avoid YDB's architectural complexity and operational overhead.
Build on ydb with DEV.co software developers
YDB is a strong fit for large-scale OLTP requiring multi-region fault tolerance and strict consistency. Begin with a single-node quick-start cluster for functional testing. Assess community support, operational readiness, and PostgreSQL compatibility before production commitment. Contact the YDB community on Discord or Telegram for deployment guidance and use-case validation.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
ydb FAQ
Can YDB survive a complete datacenter outage?
Is YDB compatible with existing PostgreSQL applications?
What is the minimum viable deployment?
Where do I get commercial support?
Custom software development services
Bringing ydb into production usually means new services, new interfaces, and new failure modes. DEV.co is a software development agency that builds all three and stays on for the open-source databases maintenance.
Evaluate YDB for Your Distributed Database Needs
YDB is a strong fit for large-scale OLTP requiring multi-region fault tolerance and strict consistency. Begin with a single-node quick-start cluster for functional testing. Assess community support, operational readiness, and PostgreSQL compatibility before production commitment. Contact the YDB community on Discord or Telegram for deployment guidance and use-case validation.