Is iDBQuery priced per seat or per usage?
iDBQuery pricing is primarily seat-based, so you pay for the people who use it rather than metering every query, which keeps costs predictable as your team asks more questions. Larger and self-hosted deployments can be structured differently, so the exact model is confirmed with our team.
How a tool is priced shapes how freely your team will use it, and iDBQuery leans toward predictability.
- Seat-based core - you pay for users, so people can ask as many questions as they need without watching a per-query meter.
- Predictable budgeting - seat pricing makes costs easy to forecast, and it encourages the self-serve behaviour that makes iDBQuery worthwhile in the first place.
- Flexible at scale - enterprise, embedded, or self-hosted deployments can be packaged to fit how you consume the product.
- No pipeline tax - because there is no warehouse or ETL to run, you are not also paying separate infrastructure bills to make iDBQuery useful.
For example, a 30-person finance and operations team can put iDBQuery in front of everyone and let them all self-serve cited answers, with cost driven by headcount rather than a bill that spikes in a busy quarter. That matters because usage-metered analytics tools often discourage the very exploration that delivers value. iDBQuery's job is to get more people answering their own questions safely, backed by RBAC and query-in-place so broad access stays governed. The precise structure depends on your plan and deployment, including embedded SDK scenarios. Contact us or see how pricing works to confirm the model for your case.
Updated 2026-06-22