What uptime and availability does iDBQuery offer?

iDBQuery's cloud service is run for high availability, and enterprise plans can include an availability commitment. In self-hosted, single-server or air-gapped deployments, uptime is entirely in your control because iDBQuery runs on your own infrastructure with no dependence on our cloud.

Availability with iDBQuery depends on where you run it, and that's a feature rather than a caveat.

  • Cloud. The hosted service is operated for high availability, and enterprise agreements can include a defined availability commitment appropriate to your needs. Talk to us about the specifics for your plan.
  • Self-hosted, single-server and air-gapped. Here uptime is genuinely in your hands. iDBQuery runs on your own servers with no runtime dependency on our cloud, so its availability is governed by your infrastructure, your redundancy and your maintenance windows — not by a third party's status page.
  • Desktop and Embedded SDK. Analysis can run locally, so it keeps working even when connectivity doesn't.

There's an important resilience point in iDBQuery's design: because it queries your sources in place rather than depending on a nightly pipeline into a warehouse, there's no fragile ETL job whose failure quietly leaves you with stale or missing data. The live model reflects your sources as they are.

We deliberately don't advertise a single headline percentage on the public page, because the meaningful number depends on your deployment and plan. For a hosted enterprise deployment we'll agree an availability commitment in writing; for a self-hosted one, we'll help you architect for the uptime your organisation requires.

Updated 2026-06-22