Prisma Studio
Browse, inspect, and edit database records locally using the Prisma Studio visual interface.
Prisma Studio is a browser-based GUI for your database. It lets you browse tables, filter records, edit values, and navigate relations — without writing SQL.
Starting Prisma Studio
pnpm db:studioThis starts Prisma Studio at http://localhost:5555 and opens it in your default browser. It reads DATABASE_URL from your .env file.
Only run Prisma Studio against a local or development database. Never run it against a production database — it allows unrestricted read and write access to all tables, including cross-tenant data, with no audit trail.
What you can do
| Action | How |
|---|---|
| Browse all tables | Click any model in the left sidebar |
| Filter records | Use the filter bar above the table grid |
| Sort records | Click any column header |
| Edit a cell | Click the cell, type a new value, press Save |
| Add a record | Click the green + button in the toolbar |
| Delete a record | Select a row and click the Delete button |
| Navigate relations | Click a relation field to jump to the related record |
Typical use cases
Inspecting seed data. After running pnpm db:seed, open Studio to verify the seeded records look correct before writing application code against them.
Debugging a failed migration. If a migration created a column with unexpected values, Studio lets you quickly scan the data and manually correct outliers during development.
Verifying RLS is not silently hiding records. Studio connects with the service role and bypasses RLS, so it shows all rows. This is useful to confirm that data was actually written when a tenant-scoped query returned empty results.
When a withRls query returns zero results unexpectedly, open Studio to check whether the records exist at all and whether the tenantId column has the value you expect.
Navigating the Nebutra schema
The sidebar lists all Prisma models grouped alphabetically. Key tables to inspect during development:
| Table | What to check |
|---|---|
Organization | Seeded organizations and their id values for use in test queries |
User | Seeded users and their organizationId memberships |
Project | Verify tenantId is populated on every row |
AuditLog | Check that actions are being recorded correctly |
ApiKey | Confirm keys were issued with the correct scope |
Alternative: Supabase Studio
If you are using Supabase as your database provider, the Supabase dashboard includes a full-featured table editor that works in both development and production (with proper access control).
Access it at https://supabase.com/dashboard/project/<project-ref>/editor.
Supabase Studio advantages over Prisma Studio:
- Accessible from any machine (browser-based, no local process needed)
- Can run arbitrary SQL queries
- Displays RLS policies visually
- Shows real-time updates
Supabase Studio in production has access to all tenant data. Restrict access to it via Supabase's team role settings — only project owners and admins should have editor access to the production project.
Stopping Studio
Press Ctrl+C in the terminal where pnpm db:studio is running. The Studio process does not run in the background when stopped this way.
How is this guide?
Last updated on