What's New in RDST: Free Inference and an Apache 2.0 License

A few months ago we shipped RDST, our command-line tool for analyzing query performance on Postgres and MySQL databases. It ranks the queries running against your database by what they cost, and helps you understand and fix the ones slowing you down. It works with managed targets like RDS, Aurora, and Cloud SQL. More recently, we packed it into a full desktop app available on Mac, Windows, and Linux and added natural-language querying, database-level health analysis, and index and rewrite suggestions.

RDST finds the queries costing you the most time on your own database, walks through why they're slow using real execution plans, and hands you specific index changes, query rewrites, or cache candidates that have been checked against your actual schema. When you'd rather just ask a question of your data than write SQL by hand, RDST does that too, and validates the SQL against your schema before it runs.

We've now expanded RDST with two big upgrades.

Free inference, no API key required

Previously, running RDST meant bringing your own Anthropic key and paying for your own tokens. Now, if you sign in with a Readyset account, RDST runs on hosted inference we cover across every AI-powered part of the app.

The default per-account allowance covers hundreds of real questions a month, which is enough for most day-to-day use. If you need more, email us and we'll raise your limit.

Anyone running an LLM against their production database queries has a right to know exactly what leaves their machine. Transparency about this has been important to Readyset since day one. The RDST privacy notice covers what gets sent to the model, what stays local, and what happens on our side of the hosted inference. If you find a scenario where our notice on privacy or LLM usage falls short, let us know.

Apache 2.0

RDST was previously distributed under the Business Source License, which limited commercial redistribution. Under Apache 2.0, that limit is gone. Open source removes the licensing conversation from adoption, so teams evaluating RDST for internal tooling no longer need to route the decision through legal review. Fork it, ship it inside your own tooling, embed it in an internal developer platform, or vendor pieces of it into your own project. The source is on GitHub and contributions are open.

Try it

Have questions or want to talk to other RDST users? Join us on the Readyset community Slack. Full RDST documentation is available on our docs site.