A fast, native macOS client for Azure SQL, SQL Server, PostgreSQL and SQLite — with an AI assistant that doesn’t just write queries, it diagrams your schema and charts your results. Ships with a demo database, so you can start querying in seconds.
Four engines, one client
Native drivers for each — Azure AD / SQL / NTLM / Kerberos auth for SQL Server, full Postgres support, and zero-config SQLite. Pin databases to the tree and switch instantly.
Azure AD login, per-database pinning, and a guided connect wizard.
On-prem 2017–2025+, with SQL, NTLM or Kerberos authentication.
Full Postgres support over pgx — schemas, views, the works.
Open any .db file instantly. A demo music database is built in.
The AI assistant
Ask in plain English. PounceSQL knows your schema, so it writes correct SQL, runs it, and turns the answer into a chart, a Mermaid diagram, or a clean summary — right next to your editor.
artists → albums → tracks — as a Mermaid ER diagram. Foreign keys drawn from the live catalog.
Bar, line and pie charts generated from the rows the query returns.
Mermaid ER diagrams and flowcharts drawn from the live catalog.
Headline numbers and plain-English readouts from a result set.
Bring your own AI
No lock-in. Point PounceSQL at a direct API key, a local Ollama model, or a corporate AI gateway — with per-provider profiles and a model switcher. A PHI-safe indicator shows when your model is cleared for sensitive data.
OpenAI or Anthropic keys, stored encrypted in the macOS keychain.
Run models entirely on your machine — nothing leaves your Mac.
Point at your org’s gateway; PHI-OK / no-PHI shown right in the status bar.
A closer look






Install
macOS 13+ (Apple Silicon). Ships with a demo database — no server or login required to start.
brew tap pounceapps/tap brew install --cask pouncesql
Or download a notarized .dmg from
pounceapps/downloads. Full docs in the
wiki.
Under active development. Provided “as is”, without warranty. The AI assistant and MCP tools are read-only by default — non-SELECT statements run only if you enable them. Test against a non-production database first.