frequently asked questions
Pricing, data privacy, platform support, and the security warning macOS shows on first launch.
Yes. QuerySQL is free to download and use, and the source is publicly available on GitHub.
No. QuerySQL is a native desktop app — it talks directly to your local SQLite file or your own Postgres server. Nothing is proxied through a third-party service, and no query or table data ever leaves your machine.
QuerySQL ships prebuilt installers for Apple Silicon Macs (arm64,
.dmg) and 64-bit Windows (x64, .exe). QuerySQL is
built with Tauri, so a Linux build is possible from source — a prebuilt installer for
Linux isn't published yet.
QuerySQL isn't signed with a paid Apple Developer ID or notarized, so Gatekeeper warns on first launch. Open System Settings → Privacy & Security, scroll to the bottom, and click Open Anyway next to QuerySQL. You only need to do this once.
The Windows build isn't signed with a paid code-signing certificate, so SmartScreen warns on first run. Click More info, then Run anyway. You only need to do this once.
SQLite and Postgres. Open or create a local SQLite file, or connect to a Postgres server with host, port, user, password, database, and SSL mode. The Rust backend is written behind a dialect abstraction, so more databases could be added later — see the About page for how that's structured.
Edits in the table view — adding, editing, duplicating, or deleting rows — are staged locally first. Nothing touches the database until you click Commit, which applies every staged change as one transaction. Click Discard instead and it's as if nothing happened.
No. Postgres passwords are never persisted. Recent Postgres connections are saved without a password, so reconnecting from that list always re-prompts you for it. Everything else — recent connections, query history, theme — is saved locally on your machine.
Postgres has no stable per-row identifier equivalent to SQLite's rowid,
so for tables without a primary key, QuerySQL falls back to using every column together
as a composite identity when editing rows.
The source is publicly available on GitHub. It's built and maintained independently — if you find it useful, you can support development at buymeacoffee.com/mindkhichdi.
QuerySQL is free, native (built with Tauri and Rust rather than Electron or Java), supports both SQLite and Postgres in one app, and its table editor stages every edit for a transactional commit or discard. See the comparison page for a full breakdown.
Not officially distributed yet. Because QuerySQL is built with Tauri, which supports Linux, a build from source is possible today; a prebuilt installer depends on interest and is on the roadmap.
No. QuerySQL is built with Tauri, which pairs a Rust backend with the operating system's own webview instead of bundling a full Chromium runtime. That means a smaller install size and lower idle memory use than Electron-based clients like DBeaver or older versions of some competitors.
Yes. QuerySQL follows your system's light/dark appearance setting automatically and can also be toggled manually from the title bar.
It depends on what you need. DB Browser for SQLite is a long-standing, SQLite-only option. QuerySQL is a good fit if you also want Postgres support in the same app, a visual schema diagram, and staged/transactional row edits — all for free.
pgAdmin is the official free option and runs on macOS, Windows, and Linux, though its interface is a web app in a desktop wrapper. QuerySQL is a native alternative that's also free, adds SQLite support, and stages row edits as a single transaction before committing — see the pgAdmin comparison for details.
Not yet — QuerySQL currently supports exporting query results and whole tables to CSV or JSON. CSV import isn't available in the current version.