Deployment
Choose the boundary your compliance team can sign off on.
The same platform runs three ways. Each model is a different trade between operational simplicity and isolation. Here is what each one needs from your team.
On-premise
Runs entirely inside your own data center.
Best for
Organizations that require data to stay on hardware they own and operate.
What your team provisions
- GPU or CPU compute sized to your model mix
- Network access controls you define
- Your own identity provider for SSO and RBAC
Private cloud
A dedicated environment inside your cloud account.
Best for
Teams that want isolation and control without running physical hardware.
What your team provisions
- A dedicated VPC or subscription in your account
- Your cloud KMS for key management
- Private networking to your data sources
Air-gapped
Fully isolated, with local models only.
Best for
Classified, regulated, or otherwise offline environments.
What your team provisions
- Local open models, no outbound API calls
- Offline update and model-loading process
- Hardened, audited host configuration
Not sure which fits?
Most teams start from a single question: where is your data allowed to live? On-premise and air-gapped keep everything on hardware you control, with local models doing the work. Private cloud is the middle path, isolation without running the metal yourself. We will help you map your data residency and compliance constraints to the right model, and you can move between them as your needs change.
Let us scope your deployment.
Share your target environment and constraints. We will come back with a concrete plan.