Ask your dataPro
Ask a database a question in plain words: the query the model writes types itself into a panel you can fold, rows are counted while it runs, and the result appears as a bar, line or table view plus one sentence explaining it.
oxyn add ask-your-dataWeekly signups by plan
Aug 3 to Oct 19 · new workspaces
Writing SQL for your question
The preview stays free for everyone. Pro opens the code of every Pro component, screen, agent-app template, block and kit, plus the Pro CLI.
Rendered from Rust at build time · goes live when visible
When to use
- Answer a plain question about a database with a chart, while showing the SQL that produced it so the answer can be checked.
When not to use
- Replays a multi-agent run on one clock: use Agent timeline instead.
- One model at a glance: use Model card instead.
- A small automation on a single rail: use AI workflow instead.
Installation
Ask your data is part of Oxyn Pro; the preview is free. Pro items install with the oxyn CLI once your licence is signed in; until then Pro members copy the code from this page.
oxyn add ask-your-dataUsage
The preview is free. Pro opens the code of every Pro component, screen and template.
Examples
Signups
Weekly signups by plan as stacked bars.
Weekly signups by plan
Aug 3 to Oct 19 · new workspaces
Writing SQL for your question
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
Revenue
MRR by plan as lines, latest values in the legend (Oxyn extra).
Monthly recurring revenue by plan
Jan to Oct 2026 · end of month
Writing SQL for your question
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
No match
A question that matches no table offers suggestions.
Ask your data
Plain questions, answered from analytics
No table in analytics matches that question. Try one of these:
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
Failed
The query times out, with Try again.
Churn rate by plan
Last 12 weeks · share of paying workspaces
Writing SQL for your question
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
API reference
AskYourData
| Prop | Type | Default | Description |
|---|---|---|---|
nowrequired | ClockMs | — | Host clock. |
question | String | SUGGESTIONS[0] | Starting question. |
auto_run | bool | true | Ask the starting question on mount. |
keep_sql_open | bool | Default::default() | Keep the SQL open after the query starts. |
fail | bool | Default::default() | The query fails (error scenario). |
suggestions | bool | true | Show suggestions in the empty state. |
Read from the Rust signature and doc comments.
Keyboard interactions
| Key | Action |
|---|---|
| Enter | Ask in the field; while busy the same button stops |
| Escape | Stop a run from the field; clear the chart readout |
| EnterorSpace | Open or fold the Generated SQL row |
| ← → · HomeorEnd | Move the readout on the chart, or change the view |
Accessibility
- Screen readers hear each step: writing the query, running it, then what the chart shows and how many rows it used.
- Progress in the query header and the result area always pairs a glyph with text.
- The query header toggles its panel and reports expanded or collapsed; the plot takes focus and speaks the values under the guide.
- The result area is marked busy until the chart lands.
From the spec
The SQL row is a button with aria-expanded and aria-controls; the chart is a focusable group whose readout is announced; the stage is aria-busy while working; the run is narrated in the polite region. Every action returns the line the polite live region announces. The focus outline shows only for keyboard focus.
Motion & interaction
The SQL streams four words a tick and is tinted by token type; the panel folds once the query starts. Bars rise from the baseline, lines draw, the table swaps in place. Arrow keys move a readout across categories with a guide line.
Timing
Everything on screen is derived from the host clock now (no timers in the component), so playback, tests and the GPUI view agree.
| Transition | Duration | Easing |
|---|---|---|
| Think before SQL | 450 ms | — |
| SQL stream | 4 words per 34 ms tick | linear |
| Query | 1300 ms (RUN_MS), rows ease out | ease-out |
| Chart build | 460 ms (BUILD_MS) | ease-out |
| Reading stream | 3 words per tick | linear |
Reduced motion: loops and travel stop; each state shows its end pose and its words.
Responsive behaviour
- Under 520 px the source keeps only its mark and the view switch drops under the title.
- Narrow cards show every second date label; long query lines and the table scroll inside their own boxes with slim scrollbars.
Edge cases (spec)
Under 520 px (container query) the source keeps only its mark, the view switch takes its own row and every other x label hides. Wide SQL and the table scroll inside their own wells with thin scrollbars; the stage keeps its height so the card does not jump. Checked at 1440, 768 and 390 px in light and dark with no text overlap. Chrome is monochrome grey; colour is semantic only (success, warning, danger, info) plus the official coloured brand and model marks.
Notes for AI
- Import
AskYourDatafromoxyn_dioxusand includeSTATUS_INDICATOR_CSSplus the token stylesheet once. - A GPUI version exists:
AiKitViewinoxyn_gpui. - Props to set first:
now. - It reads a clock (
now) for live timers; pass one clock for the whole page rather than one per component. - Keep its states and timings as they ship; restyle it through the CSS variables rather than by hand.