Skip to main content
For an overview of what gets deployed into a customer’s cloud account, see Your App Deployment Diagram.
The Nuon platform consists of a Control Plane that remotely orchestrates Runners deployed into customer accounts. Runners are egress-only: they poll the Control Plane for jobs rather than receiving inbound commands. This allows the Control Plane to coordinate work across all installs without any access to the accounts Runners are hosted in. No cross-account access is required. runner-architecture

​
Install Runner

The Install Runner is a stateless Go binary deployed into each customer account as part of the Stack. It polls the Control Plane for jobs, executes them, and streams job logs back. The customer controls the Runner’s access and can disable it at any time through the Stack. See Runners for more detail.

​
Control Plane

The Control Plane orchestrates and monitors jobs across all Install Runners and provides a single view of every install.

​
Control API

The central interface for managing apps, installs, and jobs. The Dashboard and CLI are built on top of it, and you can integrate with it directly to build custom interfaces.
Nuon Cloud is multi-tenant with logical isolation per org. Nuon can also be deployed as a BYOC app into a customer’s own cloud account. See the Nuon BYOC repo for details.

​
Runner API

A separate API that Runners use to poll for jobs and write logs and metrics. This is distinct from the Control API used by vendors and operators.

​
Builds

Before components can be deployed to installs, they are built into OCI artifacts by the Control Plane. All installs of an app share the same artifacts, and the Control Plane is the only part of the platform that touches your source code.
Build artifacts are stored as OCI images in your cloud registry.