Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.nuon.co/llms.txt

Use this file to discover all available pages before exploring further.

When you deploy your app through Nuon, it runs inside your customer’s cloud account, not yours. Nuon makes this possible by layering infrastructure and execution components inside the customer’s environment, all orchestrated remotely by the Nuon Control Plane. Each deployment is called an Install. Install Architecture When an install is created, the layers build on each other from the bottom up:
  1. Cloud Account - the customer’s AWS account or Azure subscription. Everything Nuon deploys lives inside it. No cross-account access is required.
  2. Stack - an infrastructure template that provisions networking and the Runner. Nuon generates both a Terraform version and the platform’s native IaC version (CloudFormation on AWS, Azure Resource Manager (Bicep) on Azure; on GCP, only Terraform is generated since Infrastructure Manager is Terraform-native). The customer deploys whichever format fits their tooling, using their own credentials.
  3. Runner - picks up jobs from the Control Plane and executes all infrastructure operations locally inside the customer’s environment.
  4. Sandbox - the base compute infrastructure (Kubernetes, VMs, serverless) provisioned by the Runner.
  5. Components - your application (Helm charts, Terraform modules, manifests, container images) deployed on top of the Sandbox.
Everything is defined by the App Config, a set of TOML files that declare the stack, sandbox, components, inputs, secrets, and actions. Each install is an instance of this config deployed into a customer’s cloud with their specific values. For how an install progresses from creation through ongoing updates, see the App Install Life Cycle.