| Feature | pgquery | DBeaver Community |
|---|---|---|
| Runs as | Browser tab + one container | Desktop app (Java), per machine |
| Install on each computer | YesNothing to install | NoInstall and update everywhere |
| Works on a tablet or a locked-down laptop | Yes | No |
| One URL for the whole team | Yes | PartlyTeam features are paid |
| Databases | PostgreSQL | 100+ (MySQL, SQLite, Oracle, …) |
| Works offline, local files (SQLite, CSV) | No | Yes |
| SSH tunnel | No | Yes |
| Data import (CSV, Excel, …) | No | Yes |
| Export | PartlyCSV, JSON | YesMany formats |
| ER diagram | YesSVG / PNG plate | Yes |
| Visual EXPLAIN | Yes | Yes |
| Row Level Security editor | Yes | PartlyMostly via SQL |
| Performance and security advisors | Yes | No |
| Memory use | YesA browser tab | PartlyA JVM app |
| License | MIT | Apache 2.0 (paid Pro editions) |
Where pgquery wins
- No installs: open a URL from any machine, including ones where you can’t install software.
- One deployment the whole team shares, next to the database.
- Postgres-specific screens DBeaver doesn’t focus on: RLS policies, the advisors, pg_stat_statements.
- Light: a browser tab instead of a Java desktop app.
Where pgquery loses
- DBeaver speaks over 100 databases; pgquery only PostgreSQL.
- SSH tunnels, local files, offline work and rich import/export are DBeaver strengths pgquery doesn’t have.
- DBeaver is far more mature and has a large user base.
Which one to pick
- pgquery
- You work with PostgreSQL, want zero installs, and like the idea of one URL your team can share.
- DBeaver
- You work with several database engines, need SSH tunnels or local files, or prefer a desktop app.