Can iDBQuery handle many users at once?

iDBQuery is meant for teams, not just individuals, so concurrent use is a core design point rather than an afterthought.

• Team-scale self-serve. Many people can ask questions at the same time, each getting their own cited answers.
• Governed access. Role-based access, plus row-level and column-level permissions, means each user sees only the data they are entitled to — the same question can return appropriately scoped results per person.
• Deploy for your load. Run it in the cloud, in your own VPC, or on your own hardware sized to your organisation.
• Efficient querying. Because work is pushed down to your sources, concurrent questions lean on the databases already built to serve many queries.

The point of iDBQuery is to remove the analyst bottleneck, and that only works if the whole team can use it at once. For example, during a busy month-end, finance, sales and operations can all be self-serving answers simultaneously, each within their own permissions, without queuing behind a single data person. Admins keep central control through access policies and audit logs, so scaling to many users does not mean losing governance. If you are evaluating iDBQuery for a department or a whole company, concurrent, permission-aware access for many users is exactly the scenario it is built for.