How is iDBQuery different from a dashboard?
A dashboard shows a fixed set of charts someone built in advance, so it only answers the questions it was designed for; iDBQuery answers any new question on the fly, in plain language, with every figure cited to its source. It can also generate live dashboards from a question when you want one.
A dashboard is a pre-built view. Someone decided which metrics to show, wired up the charts, and published it — which is great for monitoring known numbers, but limiting the moment you have a question it wasn't designed to answer. Then you're back to filing a request and waiting, or exporting to a spreadsheet.
iDBQuery flips that around:
- Any question, not just the pre-built ones. Ask whatever you need in plain language and get an answer immediately, even if no one anticipated the question.
- It writes the query for you. No dashboard designer, no SQL — iDBQuery figures out the query against one live model of your sources.
- Cited, not just charted. Every figure traces back to the exact source rows, so you can verify it rather than trust a tile.
- Follow-ups are natural. You can drill in and refine conversationally, instead of being confined to the filters a dashboard happens to expose.
- Across sources. A single question can span databases, spreadsheets, files and APIs that a typical dashboard would never combine without a pipeline.
Importantly, this isn't dashboards versus iDBQuery — iDBQuery can build live dashboards for you from a question. So you get the best of both: standing dashboards for the metrics you watch every day, plus the freedom to ask anything new the instant it comes up. The difference is that with iDBQuery the dashboard is an output you can create in seconds, not a bottleneck you have to queue behind.
Updated 2026-06-22