Open-Source Databases · orioledb

orioledb

OrioleDB is a modern storage engine for PostgreSQL designed for cloud deployments and multi-core hardware. It replaces PostgreSQL's default heap storage with a lock-less, MVCC-based architecture that eliminates VACUUM operations and transaction ID wraparound issues.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/orioledb/orioledb

4.1k

GitHub stars

170

Forks

Primary language

Apache-2.0

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	orioledb/orioledb
Owner	orioledb
Primary language	C
License	Apache-2.0 — OSI-approved
Stars	4.1k
Forks	170
Open issues	117
Latest release	beta16 (2026-06-18)
Last updated	2026-07-08
Source	https://github.com/orioledb/orioledb

What orioledb is

OrioleDB implements a PostgreSQL table access method extension with copy-on-write checkpoints, undo-log-based MVCC, row-level WAL, and lock-less page reading to achieve vertical scalability and reduce maintenance overhead. It requires patched PostgreSQL builds and currently targets PostgreSQL 16–17.

Quickstart

Get the orioledb source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/orioledb/orioledb.git2cd orioledb3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

High-concurrency OLTP workloads

Systems with dozens of CPU cores and heavy concurrent write loads benefit from lock-less page reading and undo-log MVCC, which eliminate buffer contention and traditional VACUUM pauses.

Cloud-native deployments with managed replication

Row-level WAL and planned active-active multimaster support suit applications that need distributed consensus-based replication without the complexity of traditional PostgreSQL streaming replication.

Large tables with continuous updates

Tables that experience frequent updates and deletes benefit from automatic space reclamation via page-merging and undo eviction, eliminating manual VACUUM tuning and bloat management.

Implementation considerations

Requires building PostgreSQL from a specific commit listed in `.pgtags` (e.g., separate commits for PG16 and PG17); exact version matching is enforced at compile time.
Mandatory preload of `orioledb.so` via `postgresql.conf` and database restart required before first use.
Cluster must be initialized with ICU, C, or POSIX locale; mismatched collations will prevent OrioleDB table creation.
Currently beta software; thorough testing and benchmarking in non-production environments strongly advised before any evaluation for production use.
libzstd development package and Python 3.5+ with testgres are required for source builds; Docker images available for amd64 and arm64v8 (Alpine Linux only).

When to avoid it — and what to weigh

Production availability is critical now — OrioleDB is in public beta. The project explicitly recommends against production use; contact the vendor for production support arrangements.
You require collations beyond ICU, C, or POSIX — OrioleDB tables support only ICU, C, and POSIX collations. If your application relies on other collations (e.g., locale-specific sorting), compatibility is limited.
You depend on PostgreSQL ecosystem tools unchanged — OrioleDB requires building against a specific patched PostgreSQL commit (pinned per major version). Tools and extensions expecting unmodified PostgreSQL internals may encounter incompatibilities.
You need immediate vendor support — Commercial support and SLAs are not clearly documented in the available data; contact [email protected] for details.

License & commercial use

Dual-licensed under Apache License 2.0 and PostgreSQL License. Users may choose either. Supabase provides a separate patent grant (see PATENTS.txt). All contributions must be made under both licenses.

Apache License 2.0 and PostgreSQL License are both permissive OSI licenses that permit commercial use. However, OrioleDB is in public beta and explicitly not recommended for production. Commercial production support must be negotiated separately (contact [email protected]). License clarity is high, but production readiness is not.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Active
Documentation	Adequate
License clarity	Clear
Deployment complexity	High
DEV.co fit	Good
Assessment confidence	High

Security considerations

OrioleDB is beta software; comprehensive security audits and formal threat modeling are not documented. As a PostgreSQL extension written in C with direct access to storage, it expands the attack surface of the database kernel. Standard PostgreSQL security practices (role-based access control, encryption at rest/transit) are not explicitly addressed. Evaluate threat model in context of beta status and limited production hardening.

Alternatives to consider

PostgreSQL with standard heap + aggressive VACUUM tuning

Proven, battle-tested; requires tuning effort but avoids beta software and patched PostgreSQL builds.

MySQL InnoDB or similar modern storage engines

Mature, production-grade alternatives with similar MVCC and lock-free optimizations; different SQL dialect and ecosystem.

Distributed PostgreSQL forks (e.g., Citus, Neon)

Purpose-built for cloud and distributed workloads; different trade-offs and maturity profiles than OrioleDB's single-node beta architecture.

Software development agency

Build on orioledb with DEV.co software developers

OrioleDB offers significant architectural advantages for modern hardware and cloud deployments, but is currently in beta. Contact the vendor for production support, or begin testing and benchmarking in non-production environments to assess fit for your concurrency and maintenance requirements.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

PolarDB-for-PostgreSQL ydb olake

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source Databases Database Development Cloud Deployment & Infrastructure Talk to DEV.co

orioledb FAQ

Can I use OrioleDB tables alongside standard PostgreSQL heap tables?

Yes. Use `USING orioledb` in CREATE TABLE to opt in; existing heap tables remain. Selective migration is supported.

Is OrioleDB production-ready?

No. Official status is public beta. Vendor recommends testing and benchmarking only; production use requires direct vendor contact for support arrangements.

Do I need to manage VACUUM for OrioleDB tables?

No. Undo-log MVCC and page-merging eliminate bloat and the need for VACUUM. This is a key maintenance reduction versus standard PostgreSQL.

What PostgreSQL versions are supported?

OrioleDB currently targets PostgreSQL 16 and 17, each with a specific patched commit pinned in `.pgtags`. Compatibility with other versions is not clear.

Software development & web development with DEV.co

Need help beyond evaluating orioledb? DEV.co is a software development agency offering software development services and web development for teams of every size. Our software developers and web developers build custom software, web applications, APIs, and open-source databases integrations — and maintain them long-term.

Evaluate OrioleDB for High-Concurrency PostgreSQL Workloads

Talk to DEV.co Schedule a Consultation