Skip to content

Engines

OrioleDB

Tested with:Not yet tested on Databasezy · facts from catalogue/engines.yaml

OrioleDB is a storage engine for PostgreSQL: tables created USING orioledb skip PostgreSQL’s buffer manager and heap, use an undo log instead of VACUUM for old row versions, 64-bit transaction ids and copy-on-write checkpoints. You keep plain SQL, every PostgreSQL driver and ORM, and every table you want on PostgreSQL’s own engine can still be created USING heap.

Each instance is a PostgreSQL 17 cluster managed by CloudNativePG running OrioleDB’s own PostgreSQL build (upstream’s orioledb/orioledb image, pinned by digest). The orioledb extension is preloaded and created in your database for you, and default_table_access_method is orioledb: a plain CREATE TABLE lands on the engine, and the catalog tells you where a table lives.

psql
create table events (id bigserial primary key, at timestamptz not null, payload jsonb); -- OrioleDB
create table lookup (k text primary key, v text) using heap; -- PostgreSQL heap
select c.relname, a.amname from pg_class c join pg_am a on a.oid = c.relam where c.relname in ('events', 'lookup');
select orioledb_version();

The instance’s Extensions page and zb instances extensions manage the extensions of your database. OrioleDB is built in and cannot be turned off; the contrib modules the image ships (pg_stat_statements, pg_trgm, hstore, uuid-ossp, citext, pgcrypto) can be enabled. PostGIS, pgvector, pg_cron, pgaudit, the foreign data wrappers and the rest of the PostgreSQL extension list are not in the OrioleDB image.

OrioleDB at a glance, from the engine catalogue
Status Coming soon
CategoryRelational
Versions17 (newest is the default)
Protocol and port PostgreSQL wire protocol on 5432
RuntimeOperator-backed (CloudNativePG)
Backupspg_dump
Point-in-time recoveryNo
PauseScale to zero
Free planNo, paid plans only
FeaturesBuilt-in transaction-mode pooler, Extensions
LicenceApache-2.0 / PostgreSQL
  • Write-heavy or update-heavy tables where VACUUM and transaction-id wraparound are a recurring cost on PostgreSQL.
  • Experiments and benchmarks against the engine with your own schema and drivers, before it is ready for production.

Pick PostgreSQL for anything that needs point-in-time recovery, high availability, read replicas, logical replication or the full extension list today.

  1. Open the portal and choose New instance.
  2. Pick OrioleDB and a version (17).
  3. Choose a size and region. Secure placement is listed only once HIPAA hosting is open (after the independent penetration test) and your organization has signed the BAA.
  4. Check the hourly price and monthly estimate, then confirm. The Connect tab fills in when the instance is ready.
How a OrioleDB instance is reached: host, ports, TLS and credentials
Host orioledb-<id>.<region>.databasezy.com, for example orioledb-7f3k.us-east.databasezy.com
Port 5432 PostgreSQL wire protocol
TLS Required on every port; plaintext is refused. Verify the server: sslmode=verify-full with the CA bundle.
Credentials Username app and a generated password, presented as SCRAM password authentication. Shown once at creation; reveal or rotate it from the Connect tab.

Connect exactly as you would to PostgreSQL, with sslmode=verify-full and the CA bundle for libpq-based drivers.

OrioleDB listens on port 5432 (PostgreSQL wire protocol). Versions: 17. Replace the example host with the one on your instance's Connect tab; credentials are shown once at creation. This engine is not orderable yet; the snippets show how connections will work at launch.

Connection URI
postgresql://app:<password>@orioledb-7f3k.us-east.databasezy.com:5432/app?sslmode=verify-full&sslrootcert=databasezy-ca.pem
db.js
import { readFileSync } from "node:fs";
import { Pool } from "pg";
const host = "orioledb-7f3k.us-east.databasezy.com";
export const pool = new Pool({
host,
port: 5432,
database: "app",
user: "app",
password: process.env.ZB_PASSWORD,
ssl: {
ca: readFileSync("databasezy-ca.pem", "utf8"),
rejectUnauthorized: true, // verify chain
servername: host, // verify hostname (verify-full)
},
max: 10, // keep well under the size's max_connections
idleTimeoutMillis: 30_000,
});
const { rows } = await pool.query("select version()");
console.log(rows[0]);

Planned client: node-postgres (pg) 8.13. Not yet tested against OrioleDB on Databasezy.

The PostgreSQL connection guide covers TLS, pooling and the allow-list in more depth, and the ORM guides (Prisma, Drizzle, Django, SQLAlchemy, Rails) apply unchanged. Schema migration tools that emit CREATE TABLE without an access method create OrioleDB tables; add USING heap to a table that needs an index type OrioleDB only bridges (GIN, GiST, BRIN, SP-GiST; native B-tree indexes are the fast path).

zb migrate does not target OrioleDB yet. Load data with pg_dump and pg_restore as your own user: a dump taken from PostgreSQL restores onto the engine (the tables are created without an access method and land on OrioleDB), and a dump taken from an OrioleDB instance carries SET default_table_access_method = orioledb, so restoring it into plain PostgreSQL needs pg_restore --no-table-access-method.

shell
pg_dump -Fc --no-owner --no-privileges "$SOURCE_URL" > app.dump
pg_restore --no-owner --no-privileges -d "$TARGET_URL" app.dump

Backups are logical dumps (pg_dump -Fc of your database) taken on the plan’s schedule and restored into a new instance. There is no write-ahead-log archiving and no point-in-time recovery for this engine, and no in-place restore: OrioleDB stores its tables with its own checkpoints and WAL records, and upstream promises no PITR for them. The PITR add-on cannot be bought for an OrioleDB instance.

OrioleDB backups use pg_dump. They run inside the instance's namespace, stream straight to the cell's object storage and are checksummed on upload. How often they run and how long they are kept follows your plan's backup policy. Eligible customer-requested resizes and version upgrades on paid plans take a pre-change backup; platform image refreshes follow a separate rollout process.

Point-in-time recovery is not available for OrioleDB. A restore returns the data as of a scheduled or manual backup. Restores create a new instance and leave the original untouched; in-place restore is not offered for this engine.

shell
zb backups create orioledb-demo --label before-release # manual snapshot
zb backups list orioledb-demo
zb backups restore orioledb-demo <backup-id> --name orioledb-demo-restore

OrioleDB can scale to zero. A paused instance has no running pods and bills no compute; its storage and backups are kept and billed as usual. Connections are refused until you resume it.

shell
zb instances pause orioledb-demo
zb instances resume orioledb-demo

See Pause and resume for schedules, wake times and billing while paused.

  • Supported versions: 17 . New instances default to 17, the only version offered.
  • Minor and patch releases: no automatic maintenance-window upgrade scheduler runs yet. Customer-requested upgrades to offered versions start when requested; image refreshes follow the engine's image/rollout process. PostgreSQL-family catalogue versions name majors, so arbitrary patch versions cannot be selected.
  • New majors are added within 60 days of the upstream release. A major reaches end of life on Databasezy six months after upstream ends support, with notices 90, 30 and 7 days ahead.

One PostgreSQL major (17) on one pinned OrioleDB beta build. A newer beta is rolled out by Databasezy as a change of the pinned image, which restarts the instance; it can also require ALTER EXTENSION orioledb UPDATE in your database, which the changelog announces.

OrioleDB is not offered on the Free plan; it runs on the paid sizes below. The size sets the CPU, memory, storage ceiling and connection limit; the gateway refuses connections over the limit with a protocol error. Storage grows in steps up to the ceiling, and you can resize at any time.

Sizes available for OrioleDB: vCPU, memory, storage ceiling, connection limit and monthly price
Size vCPU Memory Max storage Max connections ≈ $ / month
s0 0.25 1 GiB 20 GB 60 $10
s1 0.5 2 GiB 50 GB 100 $15
s2 1 4 GiB 200 GB 200 $60
m2 2 8 GiB 500 GB 400 $110
m4 4 16 GiB 1 TB 800 $210
l8 8 32 GiB 4 TB 1,500 $410
l16 16 64 GiB 8 TB 3,000 $960
xl32 32 128 GiB 16 TB 5,000 $1,870

Full details, including hourly prices and burst CPU, are in the size catalogue; plan quotas are in limits and quotas.

Not offered in the beta (the API refuses the setting): high availability and read replicas, logical replication to your own subscribers, branches, extra database users and the database studio. OrioleDB’s documented limitations apply to its tables: no prepared transactions, no CLUSTER or VACUUM FULL, SERIALIZABLE implemented with table locks rather than true snapshot isolation, non-B-tree indexes through an experimental bridge, bitmap scans only on int4, int8 and ctid primary keys, backward cursor fetches only with SCROLL. OrioleDB’s buffer pools are sized with the instance (a quarter of memory for orioledb.main_buffers, a sixteenth for orioledb.undo_buffers) and are not customer settings.

Databasezy runs OrioleDB under the Apache-2.0 / PostgreSQL licence, as listed in the engine catalogue. Your data and schemas are yours whatever the server's licence; the licence governs the server software we run.

OrioleDB is dual-licensed under the Apache License 2.0 and the PostgreSQL License; the patched PostgreSQL it runs on is under the PostgreSQL License. Nothing in the image is under a source-available or commercial licence.

  • TLS on every connection. TLS 1.2 is the minimum and TLS 1.3 is preferred; plaintext is never offered. Verify the server, not just the encryption: use sslmode=verify-full. See TLS and the CA bundle.
  • IP allow-list. The gateway checks the client address before authentication, on every plan. Manage it under Network → IP allow-list in the portal or with PUT /v1/orgs/{org}/instances/{id}/network.
  • Credentials. Generated inside the cell, shown once, never stored by the control plane. Rotate them with an overlap window so nothing breaks.
  • Secure hosting. Secure placement (HIPAA-ready) is a per-instance option for organizations that have signed the BAA: dedicated nodes and immutable backups (customer-managed keys are not built yet). It opens after the independent penetration test; until then you can join the waitlist. See Secure hosting and the BAA.
  • Staff access. Databasezy staff cannot read your data without a grant you issue. See data confidentiality.

As on PostgreSQL, you never get the superuser: the orioledb extension is created by the platform, the preload list and the engine’s buffer settings are not customer settings, and connections are TLS with SCRAM authentication.

Is this a separate database from PostgreSQL?

Section titled “Is this a separate database from PostgreSQL?”

It is PostgreSQL 17 built with OrioleDB’s patches plus the orioledb extension. Your drivers, ORMs and tools work unchanged; the storage engine under each table is what differs.

Can I add OrioleDB to my existing PostgreSQL instance?

Section titled “Can I add OrioleDB to my existing PostgreSQL instance?”

No. OrioleDB needs its own PostgreSQL build, so it ships as its own engine. Dump and restore your data into an OrioleDB instance to try it.

PostgreSQL’s PITR replays archived write-ahead log on top of a physical base backup. OrioleDB keeps its tables outside PostgreSQL’s buffer manager with copy-on-write checkpoints and its own WAL records, and the project does not promise a restorable base-backup-plus-WAL path for them yet. Databasezy only offers what it can restore: logical dumps.

No. The beta is available on paid plans only.