Don’t fly production without instruments
Core and DuckDB Quack get you a fast SQL server. Running one in production without instruments is like flying a plane with no cockpit — you can’t see who’s connected, what they’re running, or how fast. Enterprise gives you the instruments, and the controls to act on them.
Every Enterprise capability, in plain English
For each one: the risk of running without it, and what GizmoSQL Enterprise gives you instead.
Session instrumentation & auditing
Know who's connected and what they're running — right now.
Run Core or DuckDB Quack in production without this and you're flying a plane with no instruments. You can't see who's connected, how many sessions are open, what SQL is in flight, or who ran the query that hammered the cluster at 2am.
A live, queryable view of every session and statement — the user behind each connection, when they connected, and exactly what they ran — plus a durable audit trail for security reviews, incident debugging, and compliance.
- See every active session and the user behind it
- Full audit trail: who ran which statement, and when
- Answer “who ran this?” during an incident in seconds
Automatic query profiling
P99s, slow queries, and bad plans — captured automatically.
Without profiling you don't know which queries are slow, how latency is trending, or why a dashboard suddenly crawls. You're guessing — and your users have become your monitoring system.
Every statement's timing and execution plan is captured automatically. Track P50/P95/P99 latency, surface your slowest queries, catch regressions, and inspect the plan behind any statement — no manual EXPLAIN, no bolt-on APM.
- P50 / P95 / P99 latency across all queries
- Find your slowest statements and worst query plans
- Catch performance regressions before users complain
SSO / OAuth identity
Every connection tied to a real, named identity.
Shared credentials and static tokens mean you can't tell users apart, can't revoke one person's access, and can't tie a query back to a human being.
Authenticate through any OIDC provider — Google, Okta, Entra ID — so access follows your existing identity system. Onboard and offboard through your IdP; every session maps to a named user.
- Back GizmoSQL with Google, Okta, Entra ID, or any OIDC
- No shared logins, no client-side secrets
- Offboard a user in your IdP and their access is gone
Per-catalog permissions & multi-tenancy
Each team sees only the data it should.
Without fine-grained authorization, everyone who can reach the server can see everything — one connection string away from the entire dataset.
Per-catalog, per-user permissions and true multi-tenancy with per-tenant resource limits. Grant read, write, or no access on exactly the catalogs each team should see.
- Per-catalog read / write / none, per user
- True multi-tenancy with per-tenant resource limits
- Give each team exactly the access they need — nothing more
KILL SESSION
Stop a runaway query without taking everyone down.
When someone fires a runaway query in production, your only option without this is to restart the whole server — knocking every other user offline with it.
Terminate a specific session or statement on demand. Kill the one bad query and leave every other user untouched — no full-server restart, no collateral downtime.
- End a runaway session or statement instantly
- No full-server restart, no collateral outage
- Pairs with instrumentation: see the offender, then kill it
Statement queuing & timeouts
Protect the cluster from overload.
Without admission control, a burst of heavy queries can starve the server, blow out memory, and make everything slow for everyone at once.
Cap concurrent statements and queue the rest, and enforce per-query timeouts — so the server stays responsive under load instead of falling over.
- Cap concurrent statements; queue the overflow
- Enforce per-query timeouts
- Keep latency predictable under bursty load
Priority support
Talk to the people who build GizmoSQL.
Community support is best-effort — fine for tinkering, risky when a production system is down at the worst possible moment.
Direct, prioritized access to the GizmoData engineering team for production issues, upgrades, and architecture guidance — an escalation path for when it actually matters.
- Prioritized response straight from the core team
- Help with upgrades and production architecture
- A real escalation path when production is on the line
Roadmap influence
Shape where GizmoSQL goes next.
On Core, you take the roadmap as it comes — your priorities and the project’s may not line up.
Enterprise customers get a direct line into prioritization, so the capabilities you depend on move up the list — and early visibility into what’s coming.
- Direct input into feature prioritization
- Early visibility into what’s coming next
- A partner relationship, not just a vendor
What Enterprise unlocks
Core is free and open-source. Buying Enterprise unlocks the governance, auth, and support layer — at $300/vCPU/yr.
| Feature | Core | Enterprise |
|---|---|---|
| Open-source (Apache 2.0) | ||
| Deploy in your cloud / VPC | ||
| DuckDB or SQLite backend | ||
| Arrow Flight SQL | ||
| TLS / mTLS + JWT auth | ||
| Community support | ||
| SSO / OAuth | ||
| Session instrumentation & auditing | ||
| Automatic query profiling | ||
| KILL SESSION | ||
| Per-catalog permissions | ||
| Statement queuing | ||
| Priority support | ||
| Roadmap influence |