Skip to main content

What is Kvery?

Kvery is a web application that turns a plain SQL query into much more than a result set. With Kvery you connect to your databases, write a query in a modern in-browser SQL editor, and then save, schedule, share, and publish that query as a report, a REST API endpoint, or a tile on a live dashboard — without writing any backend code.

Kvery is built for people who already know SQL and want to ship data-driven tools quickly: developers, data analysts, founders, and operations teams.

What you can do with Kvery​

  • Connect to your databases. Kvery supports MySQL (and MariaDB), PostgreSQL, and Microsoft SQL Server. Connections can be secured with SSL certificates and tunnelled over SSH.
  • Write SQL in a real editor. The editor is powered by Monaco (the engine behind VS Code) with schema-aware autocomplete for your tables and columns.
  • Turn queries into forms. Add input fields to a query and Kvery renders a form so non-technical teammates can run it safely with parameters.
  • Publish queries as a REST API. Any saved query can be exposed at a stable hash URL and called over GET, POST, PUT, PATCH, or DELETE.
  • Build dashboards. Arrange query results — tables, cards, and charts — into a shareable dashboard.
  • Automate with schedules. Run a query on a cron schedule and email the results to a list of recipients.
  • Ask AI for help. Generate or refine SQL with an integrated AI chat and let Kvery write a query description for you.
  • Expose your queries to AI assistants. Kvery ships a built-in MCP (Model Context Protocol) server, so tools like Claude can discover and run your queries securely.

How Kvery is organised​

Everything in Kvery lives inside a Group. A group owns its database connections, its members and their permissions, its saved queries, its dashboards, and its settings (thresholds, IP whitelist, logs). You can belong to several groups and switch between them at any time.

Inside a group you mostly work in three places:

  1. Queries — the list of all saved queries, where you create, run, share, and schedule them.
  2. The Editor — a focused workspace for writing and testing SQL against a live connection.
  3. Dashboards — visual layouts that combine the results of several queries.

The rest of this documentation walks through each of these areas in detail. If you are new, start with Core concepts and then follow the Quick start.