Skip to content

Your database, in plain English

Ask your database.
See how it got the answer.

Ryuk writes and runs the SQL, then shows you the result, source data, and chart. Everything is ready to inspect, save, or share.

Private beta. Access is approved individually.

  • Read-only by design
  • Every query stays visible
  • Understands your schema
  • PostgreSQL + Turso

From question to decision

Ask once.
Keep the answer useful.

Ryuk does more than generate SQL. Explore your schema, investigate a question, save the result as a metric, and turn it into a report your team can revisit.

01 / Schema exploration

Ryuk learns how your data fits together.

Connect your database and Ryuk maps its tables, columns, types, and relationships. Explore the schema yourself while Ryuk uses that context to generate better queries.

acme_production Connected
customers3 fields
PKiduuid
·nametext
·emailtext
1many
orders3 fields
PKiduuid
FKcustomer_iduuid
·amountnumeric

The relationship is already there.
Every order belongs to a customer.

Illustrative workflow · Sample data

02 / Conversational analysis

Ask the question you actually have.

Write in plain English. Ryuk generates and runs the SQL, then returns the result with a chart and concise explanation. Inspect the query whenever you want.

How did revenue change in June?
Query complete
SELECT date_trunc(
 'month', created_at
), SUM(amount)
FROM orders
GROUP BY 1
ORDER BY 1;
6 rows returned
Monthly revenue USD
r

June brought in $58,420.
Up 11.5% from May. Your strongest month so far.

03 / Saved metrics

Turn an answer into a reusable metric.

Save useful queries with their visualizations, so you can check the number again without rebuilding the analysis or searching old conversations.

From your conversationMonthly revenue
Save as a metric
Monthly revenue Saved
$58,420 +11.5% vs. May
acme_production Query + visualization
04 / Reports and sharing

Build the report while the context is fresh.

Combine saved metrics with written analysis in a shareable report. Your team gets the number, the evidence, and the explanation—not another unexplained screenshot.

Your saved metric
Monthly revenue
Add the evidence.
Tell the whole story.
Revenue review Q2 2026

A stronger finish
to the quarter.

June revenue reached $58,420, up 11.5% from May.

Q2 revenue$156,120

Built for people with questions

Data questions shouldn’t become engineering tickets.

Founders

Check revenue, growth, retention, and customer activity without waiting for someone to pull the numbers.

Product & operations

Investigate behavior, monitor important metrics, and answer follow-up questions while they still matter.

Engineers & analysts

Skip repetitive queries while keeping the generated SQL visible and easy to verify.

Built to investigate, not modify

Your AI analyst shouldn’t have write access.

Ryuk runs PostgreSQL queries in read-only sessions enforced by the database itself. Generated SQL and query results remain visible, so you can verify how every answer was produced.

  • Database-enforced read-only sessions
  • Credentials encrypted at rest
  • SQL and source data remain inspectable

Before you connect
your database.

Can Ryuk modify my database?

No. PostgreSQL connections run in read-only sessions, so the database rejects statements that attempt to insert, update, or delete data. We still recommend using dedicated read-only credentials.

How do I know an answer is correct?

Ryuk shows the generated SQL and the data behind the answer. You can inspect the query, review the returned rows, and refine your question. AI-generated analysis can still be wrong, so verify important decisions.

Which databases can I connect?

Ryuk supports PostgreSQL and libSQL, including Turso. Approved users connect their own database with read-only credentials.

Do I need to know SQL?

No. Ask in plain English and Ryuk writes the SQL for you. If you do know SQL, the generated query is always available to inspect and verify.

What does a credit pay for?

Credits cover actions such as AI messages, query execution, new database connections, and PDF exports. Access and an initial credit allocation are approved for each workspace.

The next data question
doesn’t need to become a ticket.

Tell us what you want to explore. We review every workspace and allocate credits based on the use case.

Request access