Context
Regulated industries (nuclear, defence, aerospace) frequently can't use cloud-hosted tools at all. Some environments are air-gapped from the public internet entirely. This is a common deal-breaker for SaaS-only CDEs and a frequent reason we win against them.
Weaver runs anywhere a Linux container will run.
Explanation
Three deployment modes are supported, with no feature differences between them:
Cloud-hosted
We run a managed instance in your preferred cloud (AWS, Azure, GCP). Lowest operational overhead; appropriate for non-regulated environments and pre-production. We handle updates, scaling and uptime.
On-premise
We deploy into your own datacentre. You own the operating environment; we provide releases, support and architectural guidance. This is the default for nuclear and defence customers.
Air-gapped
Weaver runs on infrastructure with no internet egress. Updates are delivered as signed container images; telemetry is opt-in or disabled. The platform is designed for this case, there is no 'phone home' component required for normal operation.
There is no functional difference between cloud and on-premise Weaver. The same APIs, the same UI, the same standards compliance. The deployment topology is your operational choice, not a feature gate.