What hardware do I need to run iDBQuery on-premise?

On-premise iDBQuery is designed to run on infrastructure you control, sized to your usage rather than a fixed spec.

• Standard compute - a Linux server or VM handles the application, connectors, and query engine; sizing scales with concurrent users and data volume.
• Storage - disk is provisioned for the app, caches, and any locally ingested documents; because iDBQuery queries in place, it does not need to warehouse full copies of your databases.
• Local AI option - if you want the language model to run entirely on your own hardware for an air-gapped setup, we help you size the additional compute needed for that model.
• Your OS and network - it fits into your existing patching, backup, and monitoring processes.

For example, a mid-sized team might start on a single well-specified VM and scale out as concurrency grows, while a defence or healthcare deployment might run on isolated hardware with a locally hosted model and no external connectivity. The right sizing depends on how much data you query, how many people use it, and whether the AI runs locally or is called from your boundary. This flexibility is core to iDBQuery's architecture: cloud, VPC, or fully air-gapped, with query-in-place, RBAC, and encryption throughout. We provide a sizing worksheet during planning so the hardware matches your real workload. Contact us to scope an on-premise deployment.