> ## 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.

> ## Agent Instructions
> Nuon installs a software company's application into its customers' AWS, Azure, or GCP accounts. A runner in each customer account polls the Nuon control plane for jobs, so Nuon needs no cross-account access.
> In these docs, "you" is the software company using Nuon to ship its product, and "customer" is the company whose cloud account the product is installed into. Pages also call the software company the vendor.
> Page index: https://docs.nuon.co/llms.txt. To evaluate Nuon, read https://docs.nuon.co/get-started/introduction.md, https://docs.nuon.co/guides/deployment-options.md, https://docs.nuon.co/security.md, and https://docs.nuon.co/architecture/platform.md. To build with Nuon, start at https://docs.nuon.co/get-started/quickstart.md.
> To check which architectures Nuon supports (customer account, existing VPC or cluster, hybrid data plane, single-tenant, data residency, customer-managed keys, air-gapped), read https://docs.nuon.co/guides/byoc-architecture-patterns.md.
> Pages under https://docs.nuon.co/config-ref/ are generated from the config schema. Treat them as the source of truth for config file fields.
> Search these docs over MCP at https://docs.nuon.co/mcp.

# Installs

> One deployment of your App Template in a customer's cloud account.

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.

Nuon control plane

Runner calls out. Outbound only.

Customer cloud account AWS, Azure, or GCP

[Stack](https://docs.nuon.co/concepts/stacks.md)

[Runner](https://docs.nuon.co/concepts/runners.md)

[Sandbox](https://docs.nuon.co/concepts/sandboxes.md)

[Your components](https://docs.nuon.co/concepts/components.md)

For example:
API
Database
Storage bucket

* **[Stack](https://docs.nuon.co/concepts/stacks.md)**: the customer applies it first. It creates the network, permissions, and runner.
* **[Runner](https://docs.nuon.co/concepts/runners.md)**: runs every deploy, action, and runbook in the customer's account.
* **[Sandbox](https://docs.nuon.co/concepts/sandboxes.md)**: base compute for your components, such as a Kubernetes cluster.

## How an install deploys

The first [workflow](https://docs.nuon.co/concepts/workflows.md) provisions everything in order:

<ol />

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](https://docs.nuon.co/concepts/stacks/stand-alone-vpc.md).** Nuon creates a new network for the install.
* **[Customer VPC](https://docs.nuon.co/concepts/stacks/customer-vpc.md).** The install deploys into a network the customer already has.
* **[Customer cluster](https://docs.nuon.co/concepts/stacks/customer-cluster.md).** Your components deploy into the customer's existing
  Kubernetes cluster.

Each install also gets its own [inputs](https://docs.nuon.co/concepts/app-inputs.md), such as region or an API key. To create and configure
installs, see [Creating Installs](https://docs.nuon.co/guides/install-configs.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.