What are iDBQuery's contract terms and billing options?

iDBQuery offers flexible contract terms, typically monthly or annual, with annual plans usually billing by invoice for larger and enterprise deployments. Billing can be arranged to fit your procurement process, including purchase orders and standard payment terms, and enterprise agreements can add custom terms.

Contract and billing terms are set to fit how your organisation actually buys software.

  • Term length - choose monthly for flexibility or annual for better value and budgeting predictability.
  • Invoicing - larger and enterprise plans are commonly billed annually by invoice, supporting purchase orders and your standard payment terms rather than card-only checkout.
  • Enterprise agreements - custom contracts can accommodate security addenda, a DPA, specific renewal and notice terms, and your procurement paperwork.
  • Scoped to deployment - terms reflect whether you run in the cloud, your own VPC, or on-prem.

For example, a company standardising on iDBQuery for several teams might sign an annual agreement billed by invoice against a PO, with a DPA attached and agreed renewal terms - all handled through their procurement process. The aim is to remove friction from buying, not to lock you in: pricing and packaging are explained transparently so you know what you are agreeing to. This sits alongside the substance that matters most - the architecture and controls, including query-in-place, RBAC, and encryption - which is where iDBQuery leads rather than on contract lock-in. Specific terms depend on your plan and deployment. Contact us or see how pricing works to get an agreement drawn up for your organisation.

Updated 2026-06-22