Architecture
How Nuon Works
A deep dive into the architecture that powers BYOC deployments at scale.
Architecture
How Nuon Works
Package your app with TOML config. The Control Plane orchestrates deployments. Runners execute in customer infrastructure and stream logs back.
Step 01
Define your app in TOML
Wrap your existing Helm charts, Terraform modules, and container images. Point to your repos and Nuon handles the orchestration.
[public_repo]repo = "nuonco/aws-eks-sandbox"directory = "."branch = "main"[vars]cluster_name = "{{.nuon.install.id}}"public_root_domain = "{{.nuon.inputs.domain}}"
Step 02
Manage all installs centrally
View every customer deployment. Push updates, monitor health, and detect drift without SSH-ing into customer environments.
Step 03
Runner executes in customer cloud
A stateless binary deploys into each customer's environment. It polls Nuon for jobs through egress-only connections and never accepts inbound traffic.
API
Queue
Store
Step 04
Stream deployment logs in real-time
Watch Terraform plan and apply. See Helm install your charts. Debug failures as they happen, not after a customer reports them.