Admin studio
An admin panel from your schema.
Browse tables, inspect live queries, tail logs, and run ad-hoc mutations at /studio against any Pylon deployment. It's admin-gated in production and works the same in dev, staging, and prod.
- Browse and edit every table with the schema as the UI
- Inspect live queries and the change log as writes happen
- Tail structured logs and run ad-hoc mutations
- Admin-gated in production; zero setup in dev
How it works.
TablesLive queriesLogs
Order1,284
Customer412
Invoice980
/studio · admin-gated in prod
Studio reads your entity definitions and renders the right editor for each field: date pickers for datetimes, references for ids, and rich-text editors for richtext. It tracks your schema without a separate admin framework or model registration.
What you’d otherwise wire up.
Each line is a piece teams normally assemble for this one capability. On Pylon it is part of the runtime.
- A database GUI pointed at production credentials
- A log aggregator just to read local output
- Ad-hoc scripts to inspect which subscriptions are live
- An internal admin app built to make one-off edits
Build it on Pylon.
One framework for your schema, sync, auth, functions, realtime, and SSR. Free to start.