RDST
Readyset Diagnostics and SQL Toolkit finds the queries hurting your PostgreSQL or MySQL database and tells you what to do about them. Available as a desktop app and as a command-line tool.
Readyset Diagnostics and SQL Toolkit (RDST) connects to PostgreSQL and MySQL, finds the queries that are costing you the most, and explains how to fix them. It recommends indexes and rewrites, answers questions about your data in plain English, produces database health reports, and can put a Readyset cache in front of a query and benchmark the difference.
You do not need to be running Readyset to use RDST.
Two ways to run it
The desktop app and the CLI are built on the same engine and read the same local configuration. They are not two products, and they are not a full version and a lite version. Pick whichever suits how you work.
Desktop app
Point-and-click. Discover databases from your cloud account, watch health checks and analyses stream in, and read reports as formatted pages. Runs on macOS, Windows, and Linux.
Command line
Scriptable. Everything the app does, plus CI pipelines, cron-driven fleet audits, JSON output, and MCP access from Claude Code.
| If you want to... | Use |
|---|---|
| Look at a database you have never opened before | Desktop app |
| Read a health report as a formatted page instead of terminal output | Desktop app |
| Import every database in your AWS account by clicking through a list | Desktop app |
| Fail a CI build when a code change introduces a risky query | rdst scan --check |
| Audit two hundred databases on a nightly schedule | rdst fleet audit |
| Let Claude Code drive RDST for you | Claude Code integration |
| Pipe results into another tool | CLI |
Both read ~/.rdst/config.toml, the same query registry, and the same saved
health reports. A database you add in the app is available to the CLI in the next
command, and the reverse. Many people use both: the app to explore, the CLI to
automate what they found.
The same names, in two places
A few features are called different things in each, because the app names them for what they show and the CLI names them for the command you type.
| Desktop app | CLI | What it does |
|---|---|---|
| Slow Queries | rdst top | Ranks the queries consuming the most database time |
| Health Check | rdst audit, rdst fleet audit | Full health report for one database or many |
| Analyze Query | rdst analyze | Deep analysis of a single query with fixes |
| Ask | rdst ask | Natural-language question to safe, read-only SQL |
| Queries | rdst query list | The saved query registry |
| Comparisons | rdst cache | Deploy a Readyset cache and benchmark it against upstream |
| Code Scan | rdst scan | Extracts SQL from ORM code and analyzes it |
| Settings | rdst configure | Database connections, API keys, privacy |
How RDST relates to the rest of Readyset
| Tool | Role | Where it runs |
|---|---|---|
| Readyset | Real-time SQL cache for Postgres and MySQL | Alongside your database |
| Readyset QueryPilot | Automated cache discovery and deployment on top of Readyset | Readyset Cloud or self-hosted |
| RDST | Diagnose queries, check database health, and optionally drive Readyset caches | Your laptop, CI, or a diagnostics host |
RDST is the entry point most teams should reach for first. It surfaces which queries matter, why they are slow, whether Readyset can help, and if it can, deploys the cache for you.