Say what you want done with your data.
Read back every step, with real rows.
Ask in a sentence and Quacksmith drafts the flow. You read it on a canvas where every step shows its rows and every wire carries its count, accept it or correct it, then run it. Every run tells you what happened.
A sentence becomes a proposal
Chat reads the schemas you already have and drafts the flow. It is a proposal, never a saved flow, until you accept it.
The canvas is the readback
Every step drawn, with its real rows. Correct the picture where it is wrong — drag a wire, change a filter — and what runs follows.
Every run says what happened
What it wrote and where, or which step stopped and why — in a sentence, not an error code.
-- revenue_by_segment
SELECT
cs.segment,
cs.country,
date_trunc('month', t.booked_at) AS month,
sum(t.amount) AS net_revenue,
count(*) AS txns,
rank() OVER (PARTITION BY date_trunc('month', t.booked_at)
ORDER BY sum(t.amount) DESC) AS rnk,
sum(t.amount) - lag(sum(t.amount)) OVER (
PARTITION BY cs.segment, cs.country
ORDER BY date_trunc('month', t.booked_at)) AS mom_delta
FROM read_parquet('s3://warehouse/transactions/*') t
JOIN (
SELECT c.customer_id, c.country, p.segment
FROM public.customers c
LEFT JOIN read_csv_auto('plans.csv') p USING (plan_code)
) cs USING (customer_id)
WHERE t.status = 'settled'
AND t.booked_at >= DATE '2026-01-01'
GROUP BY 1, 2, 3
ORDER BY month, rnk;
Today, checking it means reading this.
Twenty-two lines, written the way a person actually writes them — not one step per line, but everything folded into one statement. Every join and every filter in it is correct. Not one of them will tell you what it threw away.
15,889 transactions fell out of that join. Nothing above says so. You would have to run it yourself, and know to go looking.
The same flow, drawn
Try it yourself
This is the studio’s own canvas, not a picture of one. Every wire carries the number of rows that crossed it. Drag a node, press one to read its rows, or switch to Ports to see every step’s columns on the block itself.
Read it as a run — the record the product keeps
Where the time went, and where the rows went
Started 30 Aug 2026 09:14· ran for 8.85s· every track below is that window
The durations and the start time here are illustrative — drawn for this page, not measured from a run. The shape, the grain and the order are the record’s own.
- transactions/*source_transactions 0→48,213,904 read 48,213,904 rowsParquet in S3, this year’s transactions
- public.customerssource_customers 0→812,455 read 812,455 rowsThe customers table, already in the project
- plans.csvsource_plans 0→14 read 14 rowsA fourteen-row plan-code to segment reference
-
settled · 2026filter_settled
48,213,904→43,908,177
dropped 4,305,727 rows — 9% of what came in most of any step
status = 'settled', booked this year - 3 columnsselect_customer 812,455→812,455 kept all 812,455 rowscustomer_id, country, plan_code
- segment from planslookup_tier 812,469→812,455 kept all 812,455 rows — the other 14 came in as the reference it readsTurns each plan code into the segment it belongs to — on the customers, before the transactions arrive
- on customer_idjoin_customers 44,720,632→43,892,288 joined to 43,892,288 rows 15,889 unmatchedInner join, transactions to customers
- sum by segment · monthaggregate_revenue 43,892,288→1,284 grouped 43,892,288 rows into 1,284Net revenue and transaction count per segment, country and month
- rank · MoM deltawindow_rank 1,284→1,284 kept all 1,284 rowsRank within the month, and the change on the month before
- revenue_by_segmentoutput_revenue 1,284→1,284 wrote 1,284 rowsWrites the result out
- after the last step time inside the run that no step accounts for
Each bar sits where that step ran, and is as long as it took.
The steps do not open on this page — press a node on the canvas above instead.
What you get
A flow you can read, before and after it runs.
What you just dragged is one flow, on one canvas. It comes with a draft you accept before anything is saved, a picture somebody else can check, and runs that say what happened.
Nothing is saved until you accept it
Chat drafts; you accept the proposal on the canvas, or correct it first. The AI never edits a flow behind your back.
A colleague can check it
Every step shows its rows and every wire its count, so the person who did not build it can review it without reading SQL.
Runs you read in seconds
Open a run and the answer comes first: did it finish, what it wrote, and if it stopped, which step and why. Every run in the project, in one list.
What it is
press a card to open it · scroll or use the arrowsCOMING 2027
Interested? We are building it now, and we would rather hear from you early than late.