Turbine operates across four deployment postures. Release tracks, policy enforcement, and the evidence ledger behave identically at every tier — the posture changes, the guarantees do not.
Isolated environments on infrastructure operated by Turbine. Provisioned in under sixty seconds. Releases arrive on the stable track after fleet-wide validation.
A single-tenant deployment on dedicated hardware. Inference runs locally; data and tokens do not leave the environment. For organizations with sovereignty requirements.
Managed environments at the point of operation — screens, terminals, sensors, and kiosks. Devices enroll once and are managed for life.
Turbine operated within customer-controlled networks. Agents connect outbound only; no inbound access is required at any time.
| Managed Cloud | Dedicated | Edge | On-Premises | |
|---|---|---|---|---|
| Isolation | Dedicated environment | Dedicated hardware | Device-level | Customer network |
| Inference | Managed pool | Local, sovereign | Parent environment | Local or managed |
| Connectivity | Turbine network | Dedicated link | Pull, intermittent | Outbound only |
| Release track | Stable | Stable, post-soak | Per device class | Stable, post-soak |
| Availability | Generally available | Generally available | Generally available | Qualified deployments |
Turbine onboards a limited number of organizations each quarter. Selection favors operations prepared to run under agents.