Deployment

Choose where your AI runs.

Start with the models you need, place any private hardware deliberately, then decide how your team will connect. Three separate decisions create one deployment that fits your boundaries.

Get a deployment quote Compare the choices
  1. 01Model strategyCloud, private, or both
  2. 02Private hardwareWhere it lives and who runs it
  3. 03Access surfaceDesktop with optional mobile reach

Decision 01

Choose your model strategy.

Model strategy describes which models Alluqi can connect your team to. It is separate from where a private server lives.

Cloud-only

Cloud-only uses hosted cloud models from the providers you choose. It does not require you to operate a dedicated private server. Cloud-only requires neither a customer-owned nor an Alluqi-hosted dedicated private-inference server.

Best when broad model access and minimal local infrastructure matter most.

Private-only

Private models run on dedicated physical GPU-capable hardware selected for your workloads and data boundaries. Private-only inference is not processed by cloud model providers.

Best when model control and a defined private environment take priority.

Hybrid

Hybrid uses private/local models and cloud models together. Route each workload to the model that fits its sensitivity, capability, and operating needs.

Best when one model boundary cannot serve every use case.

Decision 02

Place your private hardware.

This decision applies to private-only and hybrid strategies. Cloud-only teams can skip it.

Customer-hosted

Your hardware. Your premises.

Use a customer-owned GPU server on-premises or in a location you control. The customer provides, owns, and operates the hardware while Alluqi configures the software around the agreed environment.

  • Hardware remains in your environment
  • Your team controls physical and network access
  • Your team handles hardware uptime and maintenance

Alluqi Managed

Your server. We run it.

A dedicated, single-tenant, isolated private-model server hosted, maintained, and operated by Alluqi for your organization.

  • Alluqi handles the server build and ongoing operation
  • Your private model environment is isolated to your organization
  • Capacity is planned around your approved workloads

Boundary to know: this is not on-premises. Traffic leaves your network to reach the isolated server. Alluqi Managed hosts your private-model server; it does not replace or resell the cloud-model providers you choose.

Agreement scope: Alluqi Managed is rented infrastructure under a custom monthly agreement, with no public rate. Encryption, access controls, the data path, backups, support, maintenance, capacity, upgrades, and availability are defined by that agreement.

Decision 03

Choose your access surface.

Your interface decision does not change the model strategy or move the server. It changes where authorized work can happen.

Primary workspace

Alluqi Desktop

Alluqi Desktop is the primary workspace and main access surface for model conversations, configured tools, and governed workflows on Windows.

Private early access

Alluqi Bridge

Alluqi Bridge is an optional mobile extension to your configured Desktop environment, giving approved users secure reach beyond the workstation while its connection is encrypted.

Bridge works with cloud-only, private-only, and hybrid strategies. Bridge does not determine where inference runs.

Request early access

Put it together

Compare common configurations.

These patterns are starting points. A hybrid strategy can use either customer-hosted or Alluqi Managed hardware for its private side.

Comparison of Alluqi deployment configurations
Decision point Cloud-only Customer-hosted private Alluqi Managed private Hybrid
Model location Cloud providers selected by you Your dedicated private server Your dedicated server in Alluqi's environment Private server plus selected cloud providers
Physical hardware No dedicated private server required Requires customer GPU-capable hardware Uses a dedicated Alluqi GPU-capable server Requires physical hardware for its private side
Hardware owner No customer-operated private server Customer Alluqi Customer or Alluqi for the private side
Hardware location Provider infrastructure On-premises or customer-controlled site Alluqi-hosted isolated environment Chosen private location plus cloud providers
Data boundary Requests leave your network for selected providers Private requests remain inside your environment Requests leave your network for your isolated server Boundary depends on the model selected for each workload
Maintenance responsibility Cloud providers maintain model infrastructure Customer maintains the physical server Alluqi builds, maintains, and operates the server Private host and cloud providers each maintain their side
Best fit Broad model choice without private infrastructure Strict local control with an infrastructure team Dedicated private inference without operating the server Mixed sensitivity and capability requirements
Candid tradeoff Data handling follows each provider's terms and controls You carry hardware cost, capacity planning, and uptime It is private and isolated, but traffic leaves your network More routing policy and operational complexity to govern

Private early access

Map the right path before you build.

Tell us which models, data boundaries, hardware responsibilities, and access surfaces matter. We will shape the deployment around those constraints.

Get a deployment quote Request access