| Feature | pgquery | Supabase Studio |
|---|---|---|
| Works with | YesAny PostgreSQL | PartlySupabase projects |
| Self-hosted as | One container | The Supabase stack (many containers) |
| Table editor | Yes | YesMore polished |
| SQL editor | Yes | YesWith an AI assistant |
| Row Level Security policies | Yes | YesWith templates |
| Schema visualizer | YesSVG / PNG plate export | Yes |
| Security and performance advisors | Yes | YesMore checks |
| Visual EXPLAIN | YesTree with time share | Yes |
| Auth, storage, edge functions | No | Yes |
| Own login | No | Yes |
| License | MIT | Apache 2.0 |
Where pgquery wins
- Works with RDS, Neon, Cloud SQL, a VPS or your laptop, with no Supabase project required.
- One container instead of the whole Supabase stack.
- Handy alongside Supabase too: compare environments or hand a teammate a read-only role.
Where pgquery loses
- On Supabase, Studio is better integrated: auth, storage, functions, logs and an AI assistant.
- Studio has more advisor checks and a more polished table editor.
- Studio has a login; pgquery needs your own access control.
Using Supabase? See how to connect pgquery to Supabase.
docker run -p 54280:54280 ghcr.io/hxndrik/pgquery