Kviklet
Fast, Compliant and Open-Source Prod Access
FreeOpen SourceDevOps8,639 impressions#10 of its week1 comment
Comments
>log in to comment- Wladislav Radchenko· 2y ago
This looks like a really neat project! I love the idea of simplifying data handling in Kotlin.
Kviklet provides secure, auditable production database access with request-approve-execute workflow.
- for
- Engineering teams that need controlled production DB access.
- pricing
- freemium · free trial
- license
- open source
Key features
- Single-statement review — Developers submit a SQL statement for approval before it runs in production.
- Database proxy (Enterprise) — Engineers use their preferred client through a temporary proxy while Kviklet records activity.
- Role-based access control — Define which roles can request and approve access per database connection.
- Audit log — Records who accessed which database, what queries were run, and when for compliance.
- SSO integrations — Supports OIDC, LDAP, and SAML (Enterprise) for single sign-on.
- API keys (Enterprise) — Programmatic access for scripts and integrations.
- Self-hosted Docker deployment — Runs in your own environment via Docker images or Helm chart.
- Kubernetes access (experimental) — Request and approve command execution inside Kubernetes pods with audit.
Use cases
- Review and approve critical SQL changes before they hit production.
- Provide temporary read-only access for engineers without DBA involvement.
- Enable developers to use their existing DB client via a secure proxy.
- Maintain compliance with ISO, SOC 2, PCI DSS, HIPAA, GDPR audit requirements.
Kviklet vs alternatives
 Kviklet |  Docker |  Railway |  Coolify |  Kubernetes | |
|---|---|---|---|---|---|
| Best for | Pull-request style DB access with audit trail | Container building and execution | Deploying apps and databases | Self-hosted app platform | Container orchestration |
| Pricing | Freemium | Subscription | Subscription | Free | Free |
| DevHunt upvotes | 2 | 0 | 0 | 0 | 0 |
| Launched | Oct 2024 | — | — | — | — |
- Kviklet vs Docker: Docker is a container runtime, not a DB access governance tool.
- Kviklet vs Railway: Railway focuses on app deployment, while Kviklet manages DB access control.
- Kviklet vs Coolify: Coolify is a self-hosted PaaS alternative to Heroku, not a production DB access workflow.
- Kviklet vs Kubernetes: Kubernetes orchestrates containers; Kviklet provides DB request-approval flows.
Kviklet FAQ
What are the three access paths Kviklet offers?+
Single-statement access, a database proxy (Enterprise), and an upcoming MCP for AI agents.
Which databases are supported?+
PostgreSQL, MySQL, MariaDB, SQL Server, and MongoDB (web UI only for MongoDB).
How is Kviklet deployed?+
It is self-hosted; Docker images and a Helm chart are provided for deployment in your own environment.
Can Kviklet be used for Kubernetes access?+
Yes, an experimental feature lets engineers request and approve command execution inside Kubernetes pods, with audit logging.
What compliance standards does Kviklet help meet?+
It supports audit trails for ISO/IEC 27001, SOC 2, NIST CSF, PCI DSS, HIPAA, EU GDPR, and EU DORA.
Summarized by DevHunt from kviklet.dev · Oct 4, 2026. Details may change; check the official site.
