Supported platforms
Cloud, on-prem, air-gapped
Run the same Spatial AI Operating System wherever your data and operations live — fully managed cloud, your own VPC, on-premise, or fully air-gapped. The deployment changes; the capability does not.
Core concepts
Sensitive operations often can't run in someone else's cloud, but self-hosted tools usually lag their SaaS versions. Nexma removes that trade-off: the agent, the solvers, and the world model are identical across every environment.
- Same OS everywhere. Jax, the Agent Computer, and the DataStore are the same build across deployments. On-premise and air-gapped are not stripped-down editions.
- You control residency. You choose the region or network where data lives and who can reach it.
- It scales the same way. From a single site to a national program, capacity grows without re-architecting, in any environment.
Deployment options
| Deployment | Where it runs | Best for |
|---|---|---|
| Managed cloud | Fully hosted by Nexma | Fastest path to value, no infrastructure to operate |
| Customer VPC | Inside your own cloud account and network boundary | Your identity, logging, and security controls |
| On-premise | Your own data center hardware | Strict data residency and access control |
| Air-gapped | Fully disconnected, no internet | Classified and DDIL environments |
In every case you get the full platform — the agent, the optimization solvers, and the typed world model — not a feature-gated subset.
How it works
The platform is packaged to deploy as a unit. The same components run whether they sit in a managed region or a disconnected enclave.
1 MANAGED CLOUD CUSTOMER VPC ON-PREM / AIR-GAPPED
2 ┌───────────────┐ ┌───────────────┐ ┌───────────────────┐
3 │ Same OS │ │ Same OS │ │ Same OS │
4 │ Jax │ │ Jax │ │ Jax │
5 │ Agent Computer│ │ Agent Computer│ │ Agent Computer │
6 │ DataStore │ │ DataStore │ │ DataStore │
7 └───────────────┘ └───────────────┘ └───────────────────┘
8 Nexma operates Your account, Your hardware,
9 and updates it your controls your network only- Managed cloud is operated and kept current automatically — zero infrastructure for your team.
- Customer VPC runs inside your cloud account and network boundary, under your SSO, logging, and security policy.
- On-premise deploys on your own hardware for full control over where data resides and who can reach it.
- Air-gapped operates the entire platform — including the agent and optimization solvers — with no outbound connectivity at all.
Deployment considerations
- Updates. Managed deployments stay current automatically; self-hosted and air-gapped deployments update on your schedule, on your terms.
- Identity and access. Integrate with your existing SSO and roles so access follows your established policy rather than a separate one. See Security and governance.
- Network isolation. Run within strict boundaries, including environments with no outbound connectivity; the Agent Computer's optimization solvers run locally rather than calling out.
- Field access. Nexma Mobile is offline-first, so disconnected crews keep working and sync when a link returns — important for on-premise and air-gapped operations.
- Data sources. External connectors via the SyncEngine depend on reachability; in air-gapped deployments, ingest happens inside the boundary.
The principle is sovereignty without sacrifice: choose the deployment your security and compliance demand, and get the full platform either way — no feature gap, no residency surprises.
Where to go next
- Review the controls that apply everywhere: Security and governance.
- Understand the runtime that runs identically on-prem and in the cloud: The Agent Computer.
- See how connectors behave across environments: Interoperability.
- Equip disconnected crews: Mobile overview.