u/razein97

Image 1 — Stop Switching Database Clients — WizQl Connects Them All
Image 2 — Stop Switching Database Clients — WizQl Connects Them All
Image 3 — Stop Switching Database Clients — WizQl Connects Them All
Image 4 — Stop Switching Database Clients — WizQl Connects Them All
Image 5 — Stop Switching Database Clients — WizQl Connects Them All
Image 6 — Stop Switching Database Clients — WizQl Connects Them All
Image 7 — Stop Switching Database Clients — WizQl Connects Them All
▲ 0 r/SQL

Stop Switching Database Clients — WizQl Connects Them All

WizQl — One Database Client for All Your Databases

If you work with SQL and juggle multiple tools depending on the project, WizQl is worth a look. It's a single desktop client that handles SQL and NoSQL databases in one place — and it's free to download.


Supported databases

PostgreSQL, MySQL, SQLite, DuckDB, MongoDB, LibSQL, SQLCipher, DB2, and more. Connect to any of them — including over SSH and proxy — from the same app, at the same time.


Features

Data viewer

  • Spreadsheet-like inline editing with full undo/redo support
  • Filter and sort using dropdowns, custom conditions, or raw SQL
  • Preview large data, images, and PDFs directly in the viewer
  • Navigate via foreign keys and relations
  • Auto-refresh data at set intervals
  • Export results as CSV, JSON, or SQL — import just as easily

Query editor

  • Autocomplete that is aware of your actual schema, tables, and columns — not just generic keywords
  • Multi-tab editing with persistent state
  • Syntax highlighting and context-aware predictions
  • Save queries as snippets and search your full query history by date

First-class extension support

  • Native extensions for SQLite and DuckDB sourced from community repositories — install directly from within the app

API Relay

  • Expose any connected database as a read-only JSON API with one click
  • Query it with SQL, get results as JSON — no backend code needed
  • Read-only by default for safety

Backup, restore, and transfer

  • Backup and restore using native tooling with full option support
  • Transfer data directly between databases with intelligent schema and type mapping

Entity Relationship Diagrams

  • Visualise your schema with auto-generated ER diagrams
  • Export as image via clipboard, download, or print

Database admin tools

  • Manage users, grant and revoke permissions, and control row-level privileges from a clean UI

Inbuilt terminal

  • Full terminal emulator inside the app — run scripts without leaving WizQl

Security

  • All connections encrypted and stored by default
  • Passwords and keys stored in native OS secure storage
  • Encryption is opt-out, not opt-in

Pricing

Free to use with no time limit. The free tier allows 2–3 tabs open at once. The paid license is a one-time payment of $99 — no subscription, 3 devices per license, lifetime access, and a 30-day refund window if it's not for you.


Platforms

macOS, Windows, Linux.


wizql.com — feedback and issues tracked on GitHub and r/wizql

u/razein97 — 3 days ago
▲ 1 r/wizql+2 crossposts

Same Data, Half the RAM: WizQl's Reworked Backend Benchmarked

WizQl Benchmark — Follow-up: Reworked Backend

Since the last benchmark about a month ago, WizQl shipped a completely reworked backend with even more features and bug fixes. We ran the same stress tests again.

> These results apply across all databases WizQl supports — the reworked backend is not Postgres-specific. Whether you're on MySQL, SQLite, or any other supported database, the same memory and performance characteristics carry over.


Test Environment

Client machine MacBook Air M2 — 8 GB RAM, 256 GB storage

Server Windows PC on local network running PostgreSQL via Docker

Table schema

id       INTEGER  -- sequential
name     TEXT     -- random name
balance  INTEGER  -- random integer

2 Million Rows

Client Load Time Memory
TablePlus 16.150s 1.27 GB
WizQl 16.10s 592 MB

Load time is now effectively equal. But the memory story changed dramatically — WizQl uses 592 MB vs TablePlus's 1.27 GB. That's less than half: a 2.1× reduction.


27 Million Rows

Client Load Time Memory
TablePlus 229s 15.8 GB
WizQl 370s 6.06 GB

At this scale, TablePlus loads faster, but the memory gap widens significantly. WizQl uses 6.06 GB vs TablePlus's 15.8 GB2.6× less memory for the same dataset.


Ceiling Test — WizQl Only

> WizQl loaded 262,400,000 rows and reached 25 GB before the system ran out of memory. No artificial cap was hit — it simply used what the machine had.


The Trade-off

The reworked backend made a clear architectural choice: trade some raw speed at extreme row counts for dramatically lower memory pressure.

  • At 2M rows — near-identical performance at half the RAM.
  • At 27M rows — WizQl is the only client that remains practical on a machine with less than 16 GB free.

Because the new backend operates at the driver level — not the query layer — these gains are available universally across every database WizQl connects to, not just Postgres.

u/razein97 — 3 days ago