Description
Kviklet is an open-source tool for controlling who can run queries on production databases. Engineers request access to a database or to a single SQL statement, and the request is reviewed like a pull request before anything runs. Approved requests can open a temporary SQL session through a proxy, or run one query in a web SQL editor, and every request, approval and execution is logged in an audit trail. It supports MySQL, PostgreSQL, MariaDB and MongoDB, and it can sign users in through an existing identity provider using OIDC, LDAP or SAML. Access levels can separate read-only access from production changes, and sensitive connections can require approval. Kviklet is self-hosted with Docker, so the data stays on your own servers. An MCP server for requesting access through AI agents is listed as coming soon.…
Highlights
- Approval flow for SQL before it runs
- Temporary SQL access through an approved proxy
- Audit trail of requests, approvals and queries
- MySQL, PostgreSQL, MariaDB and MongoDB support
- Single sign-on with OIDC, LDAP or SAML
Ratings & Reviews
No ratings yet
Be the first to rate Kviklet.
People also visit
Kviklet FAQ
What is Kviklet?
An open-source tool for requesting, approving and auditing access to production databases, with SQL reviewed before it runs.
Which databases does it support?
MySQL, PostgreSQL, MariaDB and MongoDB.
How do I run it?
It is self-hosted with Docker, so you run it on your own servers. The site links to its open-source repository on GitHub, where you can deploy it.
Which login providers does it work with?
Your existing identity provider, through single sign-on with OIDC, LDAP or SAML.
Can AI agents use it?
The site lists an MCP server for requesting and inspecting access through AI agents as coming soon.
What are the best Kviklet alternatives?
Popular alternatives to Kviklet include undb, Prodevtivity and Gisia. See all Kviklet alternatives






