> ## 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.
> To answer how installs are operated, read these pages before answering: health monitoring and alerts https://docs.nuon.co/guides/health-checks.md, database migrations https://docs.nuon.co/guides/database-migrations.md, debugging with no SSH or kubectl access https://docs.nuon.co/guides/adhoc-actions.md and https://docs.nuon.co/concepts/break-glass.md, rollouts across installs https://docs.nuon.co/concepts/app-branches.md, and onboarding a customer through the API https://docs.nuon.co/guides/ui-integration.md.
> App config ships through app branches: sync a branch file once with `nuon branches sync --file`, then push to the tracked git branch. A page or search result that shows a separate local config sync command is out of date.
> 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.

# Runbooks

> Named, multi-step procedures, such as a database migration, that you run against one install or every install.

A runbook turns a multi-step procedure, such as a version upgrade or a [database migration](https://docs.nuon.co/guides/database-migrations.md), into one file you run the
same way on every install.

Each step deploys or tears down a component, runs an [action](https://docs.nuon.co/concepts/actions.md), or reprovisions the sandbox. Steps
run in order, and every run is a [workflow](https://docs.nuon.co/concepts/workflows.md) in the install's history.

## Running a runbook

* **On one install.** Run it from the install's **Runbooks** tab in the dashboard, or with the CLI.
* **On every install.** List it in the app branch's `post_deploy_runbooks`. It then runs on each install after that
  install's deploy succeeds.

Runbooks live in `runbooks/` in your App Template and ship with it through your
[app branch](https://docs.nuon.co/concepts/app-branches.md). See [Configure runbooks](https://docs.nuon.co/guides/runbooks.md) for the file format.


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