Does iDBQuery replace my existing BI stack or work alongside it?

You don't have to choose. BI tools like Power BI, Tableau and Looker are built for governed, repeatable dashboards — the standing reports everyone watches. iDBQuery is built for the questions those dashboards trigger but can't answer: the one-off, the cross-source, the 'why did this move.'

• It connects to the same data, including your data warehouse, so there's nothing to migrate.
• It fills the gap between dashboards — ad-hoc questions, exploration of unfamiliar sources, and reconciling numbers across systems.
• Cited answers give it audit-grade trust your dashboards may not expose.
• Cross-source by design. It joins databases, spreadsheets, PDFs and APIs that separate BI dashboards usually keep siloed.
• It can also produce reports and dashboards of its own, so for some teams it covers more of the stack over time.

Think of iDBQuery as the conversational, investigative layer over everything you already have. Keep your BI investment, point iDBQuery at the same sources, and give the whole team a way to ask questions in seconds without filing a request or building a new view. Replace later only if it makes sense — there's no forced rip-and-replace.