Keep the data queryable
Ask a new question without preparing the same files again.
A home for the data behind your answers
Bring files together through your AI assistant. Keep prepared data for the next question, the next batch, or a shared view.
Free during private beta. Bring your own assistant.
Setup guides for ChatGPT, Claude, Codex and more →
BRING THE RECORDS
Three files. One question that needs all of them.
“Which paid orders still need shipping? Save the combined data so we can use it again.”
“Here's the next batch. Use the same rules.”
ILLUSTRATIVE ANSWER
5 orders. €12,200.
Fully paid, with no shipment recorded.
| Country | Orders | Value |
|---|---|---|
| Spain | 2 | €6,400 |
| France | 2 | €4,800 |
| Portugal | 1 | €1,000 |
Why stop at a dashboard?
A chart answers one question. Ask your assistant to save the prepared records as a database table, and the same work can answer the next one.
Ask a new question without preparing the same files again.
Join saved records with another file when the question grows.
Give your assistant a focused result instead of whole files. Smaller answers can use fewer tokens.
Compare retained versions and repair selected data after a mistake.
Savings depend on the source, query, and assistant. History and recovery need retained workspace data.
Bring CSV or Parquet files, or connect Git, S3, ClickHouse, and public URLs. Your assistant can match records across sources and save the result.
Explore supported sources →Keep the conversation in your own AI client. Ask it to inspect the saved data, explain a result, or run the preparation on a new batch.
You choose when to refresh sources and run work.
Find your assistant's setup guide →Ask an earlier version a new question. Or restore the records an agent got wrong while keeping unrelated later changes.
Historical questions need retained data. Live sources do not automatically preserve old records.
Explore a historical question →Six connected stories. One fictional dataset, with checked results at every step.
Match three files. Find five orders worth €12,200.
Compare batches: two open orders become five.
One dataset for a conversation, a CSV, and a dashboard.
Test a €5,000 threshold without changing the accepted data.
Run the same question against two retained snapshots.
Repair two countries. Keep the later correction.
Two current outputs from the same prepared data. Fictional sample results.
ILLUSTRATIVE ANSWER
“Five paid orders still need shipping, worth €12,200.”
Spain accounts for €6,400, France €4,800, and Portugal €1,000.
Ask next: “Give me just the open orders as a CSV.”
Follow up in the same conversation.
Follow the conversation →OPERATIONS DASHBOARD · OPEN ORDERS
| Country | Orders | Value |
|---|---|---|
| Spain | 2 | €6,400 |
| France | 2 | €4,800 |
| Portugal | 1 | €1,000 |
Preview privately, then choose who can see it.
Explore the working dashboard →CSV export is available today. See more sample outputs →
Not available today. Planned directions may change; explorations are ideas for beta feedback.
“Email me the results when this report is ready.”
“Turn this analysis into a branded report.”
“Check every Monday. Alert me when open orders exceed €15,000.”
Let another application read selected prepared tables.
More file formats and delivery options beyond CSV.
Three steps to your first saved result.
Check assistant setup →Join the waiting list, or redeem a code if you already have one.
Create an agent credential, then follow your client's setup guide.
Tell your assistant which files to use, what to answer, and what it may change.
Private beta · Invitation only
Help shape how kudhub works for the things you need to understand.
Free during private beta. Prices will be published before anyone is charged.
Leave your email. We'll contact you when an invitation is available.
Already have an invitation? Redeem it →