Ridge DB
Ridge is seed's bounded, single-node relational database. It can run as an
embedded library or as the loopback-only ridged service through a documented
PostgreSQL-wire subset. Ridge Admin provides the browser-based administration
workbench.
Ridge v0.3 gates V3-G0 through V3-G44-A, V3-G47, V3-G48-G58, and V3-G62, V3-G64-G66 are complete for their recorded scopes (V3-G52 partial: the 1M-row bulk-load fast path is pending). V3-G59 (background checkpointer), V3-G60 (COPY bulk ingest), V3-G61 (sorted bulk storage), and V3-G63 (coherent shared cache) are implemented with focused evidence and their closure gates still explicit. V3-G67 (disk space efficiency) is planned. Alpha preview readiness closed 2026-08-19: V3-G44-B (getting-started documentation) shipped with the production deploy of this documentation set and V3-G46 (alpha platform closure) closed with the privileged macOS launchd service lifecycle evidence. This is a local production foundation, not a PostgreSQL replacement and not a distributed database.
Choose a starting point
| Goal | Guide |
|---|---|
| Start a local database | Quickstart |
| Understand storage, WAL, and MVCC | Architecture |
| Follow the complete Ridge and Ridge Admin runtime | Runtime architecture |
| Write supported SQL | SQL reference |
| Embed Ridge in a seed application | Embedded API |
| Connect with psql or an application driver | Pgwire and drivers |
| Back up, restore, inspect, or maintain data | Operations |
| Use the browser administration application | Ridge Admin |
| Check compatibility and unsupported features | Compatibility |
| Diagnose a failure | Troubleshooting |
| Equip an AI agent to work with Ridge | AI agents and the ridgedb skill |
Capability summary
| Area | Current bounded capability |
|---|---|
| Storage | Persistent recursive B+Trees, generation-2 typed rows and schemas |
| Durability | CRC-32 logical WAL, fsynced commit, committed-only recovery |
| Transactions | Atomic multi-table transactions, read committed and repeatable read |
| Concurrency | Disjoint staging and publication with deterministic conflict detection |
| SQL | Multi-column relational SQL, indexes, constraints, joins, aggregates, windows |
| Data workloads | JSON, time-series, full-text search, exact and bounded-HNSW vectors |
| Operations | Integrity, vacuum, backup/restore, PITR, metrics, quotas, read-only mode |
| Connectivity | Embedded API and bounded TLS/password pgwire on loopback |
| Administration | Ridge Admin local web UI with local and verified SSH connections |
What Ridge intentionally does not claim
Ridge does not currently provide replication, failover, sharding, distributed
SQL, stored procedures, triggers, extensions, the pgwire COPY protocol and
binary formats, SCRAM, general binary formats, or complete PostgreSQL
catalogs. File-based CSV ingest through COPY ... FROM 'path' WITH (FORMAT csv, ...) is supported. PostgreSQL drivers work only through
the tested pgwire subset.
Roadmap note (2026-08-18): v0.4 is scoped as device↔cloud synchronization
for offline-first applications (edge peers syncing with one authoritative
cloud through a hardened gateway; ridged itself stays loopback-only).
Multi-master replication, failover, sharding, and distributed SQL remain
deferred to v0.5 or later.
Unsupported syntax and protocol shapes fail explicitly. Do not infer a feature from PostgreSQL, MySQL, or SQLite merely because Ridge accepts familiar SQL.
Sources of truth
Public documentation summarizes the operational contracts. The authoritative implementation sources are:
grove/apps/ridge/CAPABILITIES.mdfor the closed capability inventory;grove/apps/ridge/V3_CONTRACT.mdfor SQL, type, isolation, and error rules;grove/libs/ridge_sql/README.mdfor the accepted SQL surface;grove/apps/ridge/ROADMAP.mdfor gates and deferred work;grove/apps/ridge-admin/README.mdandRELEASE.mdfor Ridge Admin;- executable tests and benchmark artifacts under
grove/apps/ridge/tests/,grove/libs/ridge_sql/tests/, andgrove/apps/ridge/benchmarks/.
Capability claims are versioned and bounded. Benchmark results are regression evidence for a named host and workload, not universal database rankings.