01 / Akuma
Your dashboard doesn’t answer today’s exception question.
Ask your database. Inspect the SQL and results.
For reporting and operations owners whose exception question changed after the dashboard was built, and the engineer who can approve a read-only source for them.
- Ask a scoped question about a connected PostgreSQL or MySQL source.
- In the interactive query workflow, Akuma can ask which definition you mean when it finds a question ambiguous.
- Inspect the read-only SQL, its rows, and the tables and filters it used.
AkumaKaizen Platform · Available today
Illustrative data
Your question
Which paid orders have waited more than 3 days without fulfilment, excluding cancelled and refunded ones?
4 orders need attentionas of 13 Sep 2026
This question named its own definitions, so it ran straight through. In the interactive query workflow, a question Akuma finds ambiguous may come back with options to choose from instead of SQL.
Next step: review these orders in your own fulfilment process. Akuma reads the database; it does not change orders or contact customers.
| Order | Paid on | Days waiting | Region | Status |
|---|---|---|---|---|
| ORD-10482 | 2026-09-05 | 8 | EU | processing |
| ORD-10497 | 2026-09-07 | 6 | US | pending |
| ORD-10511 | 2026-09-08 | 5 | APAC | processing |
| ORD-10530 | 2026-09-09 | 4 | US | pending |
Example order database · PostgreSQL · fictional names
Inspect the SQL and provenance
Written for this page to match the table; no Akuma call produced it.
SELECT o.order_number, o.paid_at::date AS paid_on,
DATE '2026-09-13' - o.paid_at::date AS days_waiting,
o.region, o.status
FROM orders o
WHERE o.paid_at IS NOT NULL AND o.fulfilled_at IS NULL
AND o.status NOT IN ('cancelled', 'refunded')
AND DATE '2026-09-13' - o.paid_at::date > 3
ORDER BY o.paid_at;Provenance comes from the executed SQL and the engine's own table list, never from the model's explanation. When present on a completed answer, provenance is labeled full, with tables and filters parsed from the SQL, or limited, with available table metadata and a stated reason.
Illustrative interface and data, not a screenshot. Akuma is available today through Kaizen Platform.
Prerequisites and next step
Live results need a connected PostgreSQL or MySQL source. No connection yet? Use an approved schema to draft SQL and run it in your own tools.
- Who does what. The reporting owner brings the question and its definition; an engineer or administrator supplies the approved source.
- Access. Connect with a database role that has only the read permission you intend. Dashboard queries run read-only, and API requests can scope tables, columns, row counts and timeouts.
- Connectivity and eligibility. Live sync supports PostgreSQL and MySQL. The connector rejects private-network and loopback hosts, and a source whose schema exceeds the eligibility limits is reported as too large rather than connected. These are the main checks, not a complete setup guide; confirm reachability with your engineer.
After you create an account: in the Akuma workspace’s Data Sources view, connect an approved PostgreSQL or MySQL source or save a manual schema, then ask a first question.