Deployment options.
A Bridge deployment is three separate decisions: the model strategy, where private hardware lives, and which apps people use. Keeping them separate keeps the boundaries honest.
Decision 1 — model strategy
- Private-only runs models on dedicated, physical, GPU-capable hardware selected for your workloads and data boundaries. Nothing is processed by a cloud model provider.
- Hybrid is private-only plus web search. Your model still runs on your own hardware; you supply an API key from a search provider so it can look things up online.
Hybrid means web search, nothing more. The search terms leave your network. Your files, code, prompts, and answers do not. It does not mean mobile access, and it does not describe who owns the hardware.
Decision 2 — private-hardware placement
Every deployment needs this decision — a private model has to run on something:
- Customer-hosted. A customer-owned GPU server on-premises or in a location you control. You provide, own, and operate the hardware; Alluqi configures the software around the agreed environment.
- Alluqi Managed. A dedicated, single-tenant, isolated private-model server hosted, maintained, and operated by Alluqi for your organization, under a custom monthly agreement with no public rate.
On-prem means the hardware running the model is installed in your environment or another location you control. An Alluqi Managed server is hosted outside that environment — traffic leaves your network to reach it — so it is not on-prem.
Decision 3 — which apps people use
The desktop app is the primary workspace. Bridge Mobile adds native account access, controlled pairing, and encrypted continuation of active desktop sessions. Your interface decision does not change the model strategy and does not move the server.
Side by side
| Decision | Customer-hosted private | Alluqi Managed private | Hybrid |
|---|---|---|---|
| Model location | Your hardware | Dedicated Alluqi-hosted server | Your hardware, plus web search |
| Hardware owner | You | Alluqi | You, or Alluqi |
| Data boundary | Your network | Single-tenant isolated server outside your network | Your network; search terms go out |
| Best fit | Strict on-prem boundary | Private models without operating hardware | Work that needs current information |