Is iDBQuery a database?
No — iDBQuery is not a database; it is an AI layer that sits on top of your existing databases and files. It connects to your sources, writes and runs queries against them, and returns cited answers, without storing your data as its own system of record.
It is easy to assume a tool that answers data questions must be a database, but iDBQuery works the other way around.
- It sits on top of your data. iDBQuery connects to the databases, warehouses, spreadsheets, files and APIs you already have.
- It queries, it does not store. Rather than being a place you load data into, it reads what a question needs at query time and returns the answer.
- It is read-only by design. iDBQuery does not act as your system of record and does not write to your sources.
So the relationship is: your databases hold the data; iDBQuery is the intelligence that lets anyone ask them questions in plain language and get cited answers. This is why there is no migration or import step — you keep your existing systems and point iDBQuery at them. For example, your orders might live in PostgreSQL and your budgets in a spreadsheet; iDBQuery does not copy either into a new database, it federates them into one live model and queries them where they are. If you are wondering whether adopting iDBQuery means standing up and maintaining yet another database, the answer is no. It is a layer of understanding over the databases you already run.
Updated 2026-06-22