Deployment methods
Where each part of SUPERWISE runs, and which part you deploy yourself
SUPERWISE® has two parts that run in different places. SUPERWISE hosts the control plane as a SaaS service. You run the Sentinel gateway, which inspects your AI traffic, in your own environment.
Where does each part run?
| Part | What it does | Where it runs | Who operates it |
|---|---|---|---|
| Control plane | The SUPERWISE app: registers your Sentinels, serves each one its policy, and receives their operational metadata for Live activity and the dashboards. | SUPERWISE's multi-tenant cloud on Google Cloud, in the us-central1 region. Each customer has its own tenant, and no data is shared across tenants. | SUPERWISE, with automatic updates and patches. |
| Sentinel gateway | Checks each prompt against your guardrails and forwards it to the model provider. | Your PC, your network, or your own cloud account. | You. |
Prompts and responses go from the gateway straight to the model provider. They never pass through the control plane. See Architecture and Data privacy.
Where can I run the gateway?
| Option | Runs on | Guide |
|---|---|---|
| Sentinel for Windows | A Windows 10 or 11 PC, as a desktop app and Windows service | Sentinel for Windows |
| Sentinel CLI local gateway | Windows, macOS, or Linux, in Docker Desktop | Install on macOS and Linux (CLI) |
| Docker | Any host that runs Linux containers | Deploy with Docker |
| Helm | Any Kubernetes cluster | Deploy with Helm on Kubernetes |
| AWS | Amazon ECS Express Mode in your AWS account | Deploy on AWS (ECS Express Mode) |
| Google Cloud | Cloud Run in your Google Cloud project | Deploy on Google Cloud (Cloud Run) |
| Azure | Azure Container Apps in your subscription | Deploy on Azure (Container Apps) |
Every option connects outbound to the same control plane. For what each one needs, see Deploy a gateway.
See also
- Security: how the platform protects your data.
- Architecture: how the control plane and gateways fit together.
Updated 18 days ago
Did this page help you?