database.pizza

A safety-first database for small, fast apps.

Every data and schema change becomes history you can inspect and undo. See how a row changed, compare the schema around a migration, and restore just the thing that broke.

Create a free database See how it works
Row history Schema history Scoped undo

Built-in database history

Every change leaves
a way back.

History is recorded as the database changes. Inspect it without touching live data, then undo at the scope the mistake actually needs.

01 / Schema history

See how your schema changed.

Move through available schema history to compare tables and columns around a migration. History is a review tool, not a backup or point-in-time restore.

02 / Row history

Follow one record.

Search for a row and compare its recorded versions, then recover an earlier value while it remains in history.

03 / Scoped undo

Undo only what broke.

Restore an earlier row or schema state without rewinding every other change made to the database.

Who it's for

History that makes
change feel safe.

Small apps and AI-built tools move fast and break things. database.pizza keeps database change history as it happens, so a bad migration or an overwritten row is something you can inspect and undo.

Database for AI-built apps

Inspect changes after agents run.

Agents create tables, run migrations, and write rows quickly. Row and schema history help you review recent effects without claiming who caused each journal entry.

Row history

Compare recorded row versions.

When a field is overwritten, available row history shows earlier values so you can prepare a focused correction.

Schema history

Understand a migration.

Schema history shows tables and columns around recorded migrations, making a rename or drop easier to explain.

Undo database changes

Undo only what broke.

Prepare a scoped correction for a record, table, or schema state without rewinding unrelated changes.

Inside database.pizza

A custom SQL stack.

One path from client to storage. Applications, developers, and agents use the same scoped interfaces, isolated SQL engine, and reviewable database history.

01 / Interfaces

PostgreSQL + HTTP

Connect applications, scripts, and agents through HTTPS or PostgreSQL.

The PostgreSQL wire server works with a subset of psql-compatible drivers. The HTTPS endpoint gives browser, server, and agent workflows a direct authenticated path to the same engine.

psql + driversHTTPS + JSON

Dogfooding the stack

Apps running on
the real path.

Gogs and Vikunja exercise managed tenants through the same PostgreSQL proxy, PizzaSQL engine, and PizzaKV storage path. They are integration targets, not a general compatibility promise.

01 / Git service

Gogs

Git hosting backed by a managed PizzaSQL database through GORM and XORM's SQLite dialect.

Open Gogs 02 / Task manager

Vikunja

Projects and tasks backed by the same managed path, with CTEs, windows, and conflict handling under load.

Open Vikunja
Read the field notes

Supported interfaces

Connect the way that fits.

The HTTPS API is the recommended public interface today. PostgreSQL wire access is available with partial compatibility and no TLS yet — test your driver before relying on it.

01
InterfacePostgreSQL wire
TCP

Use PostgreSQL where it fits.

Connect a subset of PostgreSQL tools and drivers to PizzaSQL. Compatibility is partial and there is no TLS yet — not every feature or ORM works.

Partial support
psql + CLI toolsSome driversNode / Go / Python
Connect with psqlPartial compatibility
$ PGSSLMODE=disable psql \
  -h db.database.pizza \
  -d acme/production

Partial compatibility. Test your driver — not every PostgreSQL feature or ORM works yet.

02
InterfaceHTTP API
HTTPS

Go directly from the web.

A browser, edge function, script, or agent can execute parameterized SQL over authenticated HTTP using a narrowly scoped API key.

Call from
BrowserEdgeScriptsAgents
Send a queryScoped bearer key
POST /acme/production/query
Authorization: Bearer pz_live_...

Recommended today. Secure HTTPS access is the public interface we suggest while PostgreSQL TLS is not yet available.

Open beta

Free throughout beta.

Usage limits keep capacity available so everyone gets a fair chance to test database.pizza.

Free during beta

Access is free throughout the open beta, and we intend to keep a free tier available afterward.

Best-effort availability

Uptime is not guaranteed. Use the service at your discretion, and keep another copy of critical data.

OPEN BETAFree access
$0free during beta
Fair-use limits Shared capacity, clearly defined.
3databases
500Kqueries / week
100 MBstorage
8PostgreSQL connections
Try the open beta →
InfrastructureRuns on Oracle Cloud