We announced the acquisition of OrioleDB over a year ago. Since then, we have been working on cleaning up the legal structure and finalizing the asset transfers. We have now wrapped up all legal activities, and we fully own US Patent 10,325,030 (“Durable multiversion B+-tree”).

Today, Supabase is explicitly making available a non-exclusive license of U.S. Patent No. 10,325,030 to all OrioleDB users (including proprietary forks) in accordance with the OrioleDB license.

OrioleDB is a storage extension for Postgres which uses PostgreSQL's pluggable storage system. It is designed to be a drop-in replacement for PostgreSQL's existing storage engine. OrioleDB is built to take advantage of modern hardware and cloud infrastructure, providing better performance and scalability for Postgres workloads.

OrioleDB benchmarks show that it is around 5.5x faster than Heap (TPC-C, 500 warehouses):

Supabase are working with the OrioleDB team to develop a high-performance storage engine for Postgres and push the state of the art with a Postgres-first mindset.

OrioleDB will continue as an open source project with an open contribution model. Whether you’re running Postgres in production, building tools on top of it, or just curious about storage engines, you’re invited to contribute issues, tests, docs, and code. Our goals are:

• Develop OrioleDB as a drop-in storage engine for Postgres via the Table Access Method APIs.
• Collaborate with the Postgres community to minimize and upstream the changes needed so OrioleDB can run as a Postgres extension.

License compatibility with Postgres#

OrioleDB License is now Apache 2.0. This license is quite similar to PostgreSQL License, but explicitly grants patent usage. With this change, Supabase is making available a non-exclusive license of U.S. Patent (“Durable multiversion B+-tree”) to all OrioleDB users, including proprietary forks. The patent is intended as a shield, not a sword, to protect Open Source from hostile IP claims.

Aligned with Postgres#

The intention of OrioleDB is not to compete with Postgres, but to make Postgres better. We believe the right long-term home for OrioleDB is inside Postgres itself. Our north star is to upstream what’s necessary so that OrioleDB can eventually be part of the Postgres source tree, developed and maintained in the open alongside the rest of Postgres.

• Upstreaming & standardization. Continue collaborating on the patches required for storage-engine flexibility, with an eye toward running on stock Postgres.
• Performance & stability. A steady cadence of benchmarks, fixes, and features aimed at production workloads.
• Docs & onboarding. Clearer docs and guides so teams can evaluate and adopt OrioleDB quickly.

• Share benchmarks, migration notes, and production feedback.
• Join technical discussions around pluggable storage and Postgres patching efforts in the Postgres mailing lists.
• Try OrioleDB, kick the tires, and open issues or PRs