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

# BYOC Management Infra

> What Nuon runs in each customer's cloud account.

Every install runs on the same standard infrastructure in the customer's cloud account. The customer applies it with
their own credentials, and 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.

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


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