OrioleDB
Managed OrioleDB
OrioleDB with a TLS endpoint, per-database credentials, an IP allow-list and engine-native backups. OrioleDB is coming soon; the details below describe how it will run.
Sample query
> SELECT 1; | ?column? |
|---|
| 1 |
Features
OrioleDB on Databasezy
-
TLS at the gateway
Public connections require TLS 1.2 or 1.3. Encryption inside the cell depends on the engine.
-
Backups
Engine-native backups to object storage.
-
Metered
Billed for what runs, with a spend cap.
-
Audited
Every control-plane action lands in the audit log.
Quick start
Connect to OrioleDB
Hosts, ports and the CA bundle come from the portal or the CLI after you create an instance. Credentials are shown once and never stored by our control plane.
OrioleDB is not available to create yet. These snippets show how connecting will work when it launches.
From the CLI
zb instances create --engine orioledb --name orioledb-7f3k --waitzb api GET /v1/orgs/{org}/ca.pem > databasezy-ca.pemzb connect orioledb-7f3kAt a glance
- Category
- Relational
- Versions
- 17
- Wire protocol
- postgres · port 5432
- Runtime
- Operator: cloudnative-pg
- Backup
- pg_dump
- Pause
- Scale to zero
- Free tier
- No
- Licence
- Apache-2.0 / PostgreSQL
Connection strings and drivers
postgresql://app:<password>@orioledb-7f3k.us-east.databasezy.com:5432/app?sslmode=verify-full&sslrootcert=databasezy-ca.pempsql "host=orioledb-7f3k.us-east.databasezy.com port=5432 dbname=app user=app sslmode=verify-full sslrootcert=databasezy-ca.pem"import pg from "pg";
import { readFileSync } from "node:fs";
const pool = new pg.Pool({
connectionString: process.env.DATABASE_URL,
ssl: { ca: readFileSync("databasezy-ca.pem", "utf8") },
});
const { rows } = await pool.query("select now()");import os, psycopg
with psycopg.connect(os.environ["DATABASE_URL"]) as conn:
print(conn.execute("select now()").fetchone())Deployment
Choose where it runs
Placement is chosen per database, so a regulated workload and a side project can live in the same organisation.
-
Standard hosting
Shared cells with namespace isolation, default-deny network policy and an IP allow-list. Available on every paid plan.
- Usage-based compute, billed per running hour
- Spend cap to stop surprises
-
Secure hosting (HIPAA)
This database runs on dedicated nodes in a separate HIPAA cell, under a signed Business Associate Agreement. Planned for Team and Enterprise; HIPAA hosting opens after the independent penetration test. Join the waitlist.
- $0.10 per instance-hour on top of compute
- How secure hosting works
-
From the CLI or API
Script instances in CI with the zb CLI or the REST API. Pick the placement per instance.
secure placementzb instances create --engine orioledb --placement secure --wait
Plans
OrioleDB on each plan
Usage-based pricing with a spend cap: you pay a plan fee plus what your instances use.
Free tier
OrioleDB is not on the free plan. It starts on Solo, where a monthly compute credit covers one s0 instance.
Sizes
From s0 (0.25 vCPU, 1 GiB) at $10/mo up to xl32 (32 vCPU, 128 GiB). Resize without changing the connection string.
All sizes and pricesBackups
pg_dump. Snapshots only: point-in-time recovery is not available for this engine.
Migrate
Migrate to OrioleDB from
Migrations into OrioleDB open when the engine launches. These are the sources it will accept.
Documentation
OrioleDB docs
- OrioleDB guide Versions, configuration, limits and engine-specific behaviour.
- Connect to OrioleDB Drivers and connection strings for each language, with TLS verification.
- Backups, restore and PITR Schedules, retention, manual snapshots and restoring into a new instance.
- Connection pooling When to use the built-in pooler and how to size application pools.
- Pause and resume Scale to zero, wake on connect and pause schedules.
- Secure hosting and the BAA Dedicated nodes, immutable backups and HIPAA eligibility.
- Limits Connections, storage and request limits by size and plan.
- CLI reference Every zb command used on this page, with flags.
OrioleDB questions
Which OrioleDB versions can I run?
17 today. Minor and patch updates are applied in your maintenance window after a pre-change backup.
Which extensions, modules or plugins are available?
See the engine documentation for what is available.
How are backups handled?
Backups use pg_dump. Paid plans run scheduled backups (Solo: daily, 7-day retention; Team: daily, 14-day retention). OrioleDB does not support point-in-time recovery; you restore from the most recent snapshot into a new instance.
Is the connection encrypted?
Public connections always require TLS (1.3 where your client supports it, 1.2 at minimum). MySQL and MariaDB also use verified TLS from gateway to database; other engines currently use plaintext inside the cell. Verify the public server with our CA bundle from the portal's Connect tab or `zb api GET /v1/orgs/{org}/ca.pem`, and restrict access further with the IP allow-list included on every plan.
Can I pause it when I'm not using it?
Yes. On paid plans you pause on demand, or from your own scheduler. A paused instance bills storage and backups but no compute, and wakes in 10 to 40 seconds.
What are the limits?
OrioleDB is not on the free plan. Paid sizes run from s0 (0.25 vCPU, 1 GiB, 60 connections, $10/mo) to xl32 (32 vCPU, 128 GiB, 5,000 connections), with up to 16 TB of disk.
When can I create a OrioleDB instance?
OrioleDB is coming soon. The roadmap page shows progress; you can create an account now and use the available engines in the meantime.
What you get on each plan
Plan features as they apply to OrioleDB.
| Feature | Free | Solo | Team | Enterprise |
|---|---|---|---|---|
| OrioleDB on this plan | No | Yes | Yes | Yes |
| Plan fee | — | $25/mo | $599/mo | Custom |
| Largest size | — | xl32 | xl32 | xl32 |
| Included per instance | — | 8 GB | 8 GB | Negotiated |
| Max disk per instance | — | 1 TB | 16 TB | 16 TB |
| Scheduled backups | — | Daily, 7-day retention | Daily, 14-day retention | Hourly, 35-day retention · cross-region copy · immutable |
| Point-in-time recovery | — | Not available for this engine | Not available for this engine | Not available for this engine |
| Pause | — | On demand (schedule it from cron or CI) | On demand (schedule it from cron or CI) | On demand (schedule it from cron or CI) |
| Secure hosting (HIPAA) | — | — | Waitlist (opens after the pen test) | Waitlist (opens after the pen test) |
| Support | — | Tickets, first response in 4 hours (urgent) | Tickets, first response in 1 hour (urgent) | Tickets, first response in 30 minutes (urgent) |
| Uptime SLA | — | — | 99.9% | 99.95% |
OrioleDB is on the way
Create an account and run the available engines today; OrioleDB is coming soon.