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

# Updates and Operations

> Ship a change to every install with a git push, change one install, and run migrations with actions and runbooks.

To update your installs, push a change to the git branch your app branch tracks.

<ol />

## Ship to every install

* **Push to git.** A push to the tracked branch runs the [app branch](https://docs.nuon.co/concepts/app-branches.md). It builds what changed,
  then plans and deploys it one [install group](https://docs.nuon.co/concepts/app-branches.md#install-groups) at a time.
* **Review before it ships.** Each install group waits for you to approve its Terraform plan or Helm diff, or approves
  itself when every [policy](https://docs.nuon.co/concepts/policies.md) check passes.

## Change one install

* **Edit its config.** Change that install's [config](https://docs.nuon.co/guides/install-configs.md), such as its inputs or a
  [component override](https://docs.nuon.co/guides/component-overrides.md).
* **Roll back.** [Re-apply an earlier config version](https://docs.nuon.co/guides/rollback-install-config.md) on that install.

## Run migrations and day-2 work

* **[Actions](https://docs.nuon.co/concepts/actions.md)** run scripts by hand, on a schedule, or around a deploy.
* **[Runbooks](https://docs.nuon.co/guides/runbooks.md)** chain deploys and actions into one procedure, such as a [database migration](https://docs.nuon.co/guides/database-migrations.md). Run one
  against a single install, or list it in the app branch's `post_deploy_runbooks` to run it on each install after its
  deploy.
* **[Operation roles](https://docs.nuon.co/concepts/operation-roles.md)** give each run only the access it needs.
* **[Break glass](https://docs.nuon.co/concepts/break-glass.md)** lets your customer grant more access when you need to service their install.
* **[Health checks](https://docs.nuon.co/guides/health-checks.md)** show whether every component is running, with alerts to Slack and
  webhooks.

Every run is a [workflow](https://docs.nuon.co/concepts/workflows.md) that records its steps and logs, so you can see what ran, when, and
against which install.


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