Radius self-hosted deployment gives teams the power to run applications on their own infrastructure while keeping the productivity of a modern PaaS. Built for developers who want the portability and repeatability of Radius, but without relying on a hosted environment, self-hosting shifts the balance back to local control.
With Radius, you define services, environments, and dependencies in code. The control plane runs in your Kubernetes cluster. Your workloads build and deploy with the same workflows as the managed version—only here, nothing leaves your network unless you want it to. This means compliance stays tight, latency stays low, and architecture stays under your direct command.
Self-hosted Radius starts with a straightforward installation:
- Provision a Kubernetes cluster (on-prem or your preferred cloud VM).
- Install the Radius CLI.
- Bootstrap the Radius control plane in-cluster.
- Deploy services using your existing application specs.
This mirrors the hosted experience, so teams migrating from Radius Cloud face no steep learning curve. Every component, from environment definitions to service binding, works exactly as documented. Upgrades follow standard Helm charts, giving you predictable version control and rollback capability.