zanith

Studio

The bundled web UI for any database the engine can talk to. Studio ships as a separate package @zanith/studio — install it alongside the engine and run zanith studio to launch.

Install + launch

SHELL
# alongside the engine
npm install -D @zanith/studio
 
# launch — defaults to localhost:4321
zanith studio
 
# point at a specific database (overrides zanith.config.ts)
zanith studio --connection postgres://user:pass@host:5432/db
 
# different launch mode — see /docs/studio/launch
zanith studio --mode staff --token <token>
zanith studio --mode viewer

Two levels, eight surfaces

LevelWhat it covers
**Workspace**Cross-database — every connection in one place. Activity, search, schema diff, command palette. See [Workspace level](/docs/studio/workspace).
**Database** (8 tabs)Tables · SQL · Security · Catalog · Schema · Migrate · Recover · Search. The first five have dedicated docs pages below; Schema/Migrate/Recover defer to [Migrate](/docs/migrate); Search defers to [Production · Search](/docs/production/search).

What's in this section

PageCovers
[Workspace level](/docs/studio/workspace)Connections, recent activity, schema diff, command palette.
[Tables surface](/docs/studio/tables)Browse, edit, FK drilldown, bulk operations, sensitive-data masking.
[SQL playground](/docs/studio/sql)Multi-tab editor, parameter prompts, plan history, watch mode, inline charts.
[Security tab](/docs/studio/security)Lock graph, RLS inspector, role list, permission matrix.
[Catalog](/docs/studio/catalog)Views, sequences, triggers, functions, indexes — first-class, with one-click ops.
[Launch + auth](/docs/studio/launch)Three deployment shapes — local, staff, viewer — with the auth model for each.

Where Studio sits architecturally

Studio runs in-process with the engine. Your zanith.config.tsimports the adapter; Studio uses the same adapter to talk to your database. Plugins you have registered (logging, multi-tenancy, audit) all run when Studio executes a query — there is no "backdoor" mode.

Marketing-shaped overview

For a marketing-shaped overview that pitches Studio to a team, see /studio. The pages under /docs/studio are the working reference.