World's first sealed Postgres
The Cellar
The Cellar is a sealed database for your app. You get a connection string, REST, live updates, and an import hatch. Paste a phpMyAdmin SQL dump (or CSV / JSON) and Zipper turns those tables into chambers. Browse and edit rows in Studio. Mint, revoke, and regenerate capability seals. Narrow a seal per user with scoped sessions (POST /session — tables and operations only). Every request runs under a 7.5s server budget with Server-Timing, and the official Cellar client retries 429/503 with Retry-After — no more client-side timeout hangs. Encryption and row rules stay on. SQL is Zipper’s dialect — it never hits the host Postgres parser. It is not Amazon RDS, not stock MySQL, and not a second Supabase. Live updates run on this Zipper process, not a world bus.
In plain English — A real Postgres database for your app, run by Zipper. You get a connection string, a REST API, live updates, and a studio to browse your rows — with encryption and row-level rules always switched on.
Sealed query
World's first sealed Postgres
This is your app database. Run SQL here. The password is a seal, not a Postgres superuser. Encryption and row rules stay on. The public pad is a tasting room (read only).
Public sealed sandbox — statements never persist. Sign in to open a workspace cellar.
- ▸ Hatch: capability seal, fail-closed Origin
- ▸ Scoped sessions — narrow tables + ops per user
- ▸ 7.5s request budget + Server-Timing, Retry-After on 503
- ▸ Resilient client SDK — 429/503 auto-retry
- ▸ Climate: AES-256-GCM and RLS always on
- ▸ Import phpMyAdmin SQL / CSV / JSON
- ▸ Studio: browse, insert, edit, delete rows
- ▸ DELETE … RETURNING + multi-column order (PostgREST)
- ▸ Mint · revoke · regenerate seals
- ▸ SQL, REST, live hatch, and agent setup
- ▸ Email/password seals for your users
Auto-provisioned on every new zone. Read the The Cellar docs, including use cases and API examples. Manage it from the dashboard after you create an account.
Create an account