Database

Every Wok includes a dedicated Postgres database — not a shared schema. You get full SQL, an instant REST API over your tables, and daily logical backups, with strong isolation from other tenants.

⚡

Click SQL on any Wok card in the dashboard for an in-browser console: run DDL, seed rows, or peek at data without spinning up Studio. NOTIFY pgrst auto-fires on success so your REST API picks up schema changes immediately.

Instant REST API (shipped)

Tables are exposed over a PostgREST REST API automatically, guarded by row-level security. Read and write with @supabase/supabase-js or plain HTTP:

orders.ts

const { data } = await tw
  .from("orders")
  .select("id, total, customer:customers(name)")
  .gte("total", 100)
  .order("created_at", { ascending: false })
  .limit(20);

Backups (shipped)

Every Wok's database is logically dumped daily via pg_dump to a MinIO bucket on separate storage. Restores recreate the database on a fresh host; your Wok keeps its endpoint and keys.

Isolation (shipped)

Each Wok's Postgres runs as its own container with its own credentials. The Standard tier bin-packs Woks onto one host (strong database isolation, shared kernel); see Isolation tiers for the stronger tiers on the roadmap.

Roadmap

Point-in-time restore — continuous WAL streaming to enable restore to any second within a retention window. Phase-7 enterprise hardening; daily pg_dump is the current promise.
Managed migrations — versioned schema changes with expand/contract safety and auto-rollback. Today you run migrations via direct SQL or via standard Supabase migration tooling against your Wok.