How did revenue change month over month this year?
3 steps
June was the strongest month of 2026, up 11.5% on May.
June revenue
$58,420
vs May · +11.5%
+$6,020
Q2 total
$156,120
60k40k20k0
JanFebMarAprMayJun
Save as metricCopy SQL
1
2
3
4
5
6
SELECTdate_trunc('month', paid_at) AS month,
sum(amount) AS revenue
FROM payments
WHERE paid_at >= '2026-01-01'
GROUPBY1
ORDERBY1;
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 · Connect and understand
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 write better queries.
payments48,210 rows
iduuid
customer_id→ customers
amountnumeric
paid_attimestamptz
customers3,904 rows
iduuid
nametext
plantext
created_attimestamptz
02 · Ask and investigate
Ask the question you actually have.
Write in plain English. Ryuk generates and runs the SQL, then returns the result with a chart and a short explanation. Inspect the query whenever you want.
Which plan grew fastest in Q2?
SELECT c.plan,
sum(p.amount) AS revenue
FROM payments p
JOIN customers c ON c.id = p.customer_id
WHERE p.paid_at >='2026-04-01'GROUP BY 1;
03 · Save what matters
Turn an answer into a reusable metric.
Save useful queries with their charts, so you can check the number again without rebuilding the analysis or digging through old conversations.
June revenue
$58,420
+$6,020 (11.5%) vs May
Q2 total
$156,120
April to June 2026
May revenue
$52,400
Refreshes daily at 6:00
H1 total
$293,620
January to June 2026
04 · Explain and share
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.
PublishedSnapshot Jul 1, 2026
Q2 revenue review
Revenue closed Q2 at $156,120. June was the strongest month of the half, driven by renewals on the annual plan.
Illustrative workflow · Sample data
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 stay visible, so you can verify how every answer was produced.
Read-onlySessions enforced by the database
EncryptedCredentials encrypted at rest
InspectableSQL and source data stay visible
Access
Credits, approved per workspace.
Credits cover AI messages, query execution, new database connections, and PDF exports. We review every workspace and allocate credits for the use case.
Private beta
Creditsapproved per workspace
Tell us what you want to explore. Access and an initial credit allocation are approved for each workspace.
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.