Readyset Docs

AI access

Sign in to Readyset to turn on AI monitoring. Add your own Anthropic key for deep analysis and reports if you'd like.

Sign in to Readyset

AI monitoring needs a Readyset sign-in. While you're signed in, RDST checks each monitored database every few minutes and tells you when a query starts taking more of the database's time. The same sign-in covers deep analysis, nightly reports, Analyze and Ask, so there's no API key to manage.

The first time you open RDST, it asks you to choose how it uses AI. Pick Sign up or sign in.

The first screen, Choose how RDST uses AI, with Sign in to Readyset as the recommended choice and a link to add an Anthropic key below it

  1. Select Sign up or sign in. You can also find it later under Settings, on the AI tab.
  2. Continue with Google, GitHub, or an email sign-in link.
  3. Finish in your browser. The app shows Signed in as with your email.

RDST currently allows AI monitoring on up to 3 databases per account. Contact us for more. Monitoring beyond that runs locally without AI. The database limit applies across computers.

Your account also has a monthly AI usage limit. If it runs out, the app says You've run out of AI usage for now and offers Contact us.

Without a sign-in

Local monitoring works when you're signed out, tracking up to 10,000 queries per database and counting the rest in the totals. The chart, the query list and locally measured alerts keep working, including lost connections and stuck queries. The Database page and the turn-on dialog show Sign in to turn on AI monitoring and say that monitoring is local only.

The monitoring switch area warns You won't get automatic AI recommendations for this database. Its Sign in action lets you turn on AI monitoring.

You can open the Inbox and add a database without AI access. The full-screen AI choice still appears on first run.

Change checks, automatic deep analysis and report summaries wait until you sign in.

What uses AI

FeatureAI work
RDST AgentQuery classification, change checks every few minutes, automatic deep analysis, and report summaries
ActionsRanking open changes alongside change checks, and writing why each new change matters, at most 3 calls per database a day
Analyze nowQuery explanation, index recommendations, and rewrites
AskSQL generation and clarification
Nightly reportWritten findings and next steps

To use less AI, check for changes less often or deeply analyze fewer queries a day in the monitoring settings.

When a usage limit is reached

AI monitoring stops gracefully. Local monitoring keeps recording, the charts and query list keep updating, and locally measured alerts still work. The app says You've run out of AI usage for now and asks you to contact us. Use its contact action or email hello@readyset.io. AI monitoring resumes once the limit is raised.

If a database can't get an AI monitoring slot, choose Turn on local monitoring. Its AI change checks, automatic deep analysis, and written report summary stay off. See Monitoring limits.

Your own Anthropic key

An Anthropic key covers deep analysis and reports. It doesn't replace signing in: AI monitoring's change checks and query classification always run through your Readyset account, and automatic deep analysis and reports only run while you're signed in. With a key added, you can use AI monitoring on up to 10 databases. Contact us for more.

To add one, open the AI tab in Settings, or use Add Anthropic key on the first screen:

  1. Select Set key and enter the key.
  2. Select Test key to check it.
  3. Check the provider shown in Settings before running an analysis.

The key is stored in your operating system's keychain. Ask, Analyze, deep analysis and report summaries use it while it's selected.

Use the included AI switches back to your Readyset account. The CLI shares the saved provider choice. A saved Readyset preference takes precedence over ANTHROPIC_API_KEY. See CLI configuration.

What is sent

AI calls can include SQL, execution plans, schema metadata, and sampled parameter values used for deep analysis. Query result rows aren't sent. Agent activity shows AI calls and the kinds of data sent. The activity log doesn't store sampled values.