Skip to main content
An install is one copy of your App Template in a customer’s cloud account. Every install runs on the same standard infrastructure, which the customer applies with their own credentials. No cross-account access is required.
  • Stack: the customer applies it first. It creates the network, permissions, and runner.
  • Runner: runs every deploy, action, and runbook in the customer’s account.
  • Sandbox: base compute for your components, such as a Kubernetes cluster.

How an install deploys

The first workflow provisions everything in order: Terraform, Helm, and Kubernetes manifest steps pause on a plan for your approval before they apply.

Fit the customer’s architecture

The stack adapts to what the customer already has:
  • Stand-alone VPC. Nuon creates a new network for the install.
  • Customer VPC. The install deploys into a network the customer already has.
  • Customer cluster. Your components deploy into the customer’s existing Kubernetes cluster.
Each install also gets its own inputs, such as region or an API key. To create and configure installs, see Creating Installs.