Can many people use iDBQuery at the same time?
Yes — iDBQuery supports many users querying concurrently, each in their own conversation and each governed by their own role, row, and column permissions. Because it pushes work down to your databases and warehouses, it scales with your infrastructure, so a whole team can self-serve answers at the same time.
Self-serve analytics only works if the tool holds up when the whole organisation uses it, not just one analyst.
- Concurrent conversations. Multiple people can ask questions simultaneously, each in an independent thread with its own context, so one person's follow-ups don't interfere with another's.
- Per-user governance. Concurrency is permission-aware: role-based access plus row- and column-level controls mean each user's queries are scoped to what they're allowed to see, even under load.
- Scales with your sources. Since iDBQuery pushes aggregation into your database or warehouse, heavy lifting happens on infrastructure you already size for analytics, and read replicas can absorb query load away from production.
This is what makes iDBQuery viable as a team-wide, self-serve tool rather than a single-seat assistant: finance, sales, ops, and leadership can all be asking questions at once. Deployment flexibility helps too — running in your own VPC or on your hardware lets you provision capacity to match your user base. And every one of those concurrent answers still arrives cited to source rows, so scale never comes at the cost of trust.
Updated 2026-06-22