# Nuon features

> What Nuon gives a software vendor that installs and operates its product in customers' cloud accounts.
> Each feature links to its documentation page.

## Package your product as an app template

An app template is a directory of TOML files in git that maps your existing Terraform, Helm charts, Kubernetes manifests, container images and Pulumi programs to Nuon components. One template installs into every customer.

Docs: https://docs.nuon.co/concepts/apps.md

## Per-customer configuration and secrets

Inputs configure each install, for example region, size or domain. Secrets are supplied by the customer during setup and stored in the customer's own secret manager: AWS Secrets Manager, Azure Key Vault or Google Cloud Secret Manager.

Docs: https://docs.nuon.co/concepts/app-inputs.md

## Install into the customer environment

For each install Nuon generates a stack that the customer applies with their own credentials: CloudFormation or Terraform on AWS, Bicep or Terraform on Azure, Terraform on Google Cloud. The stack can create a new network or use a network or Kubernetes cluster the customer already has.

Docs: https://docs.nuon.co/concepts/stacks.md

## Ship updates with a git push

An app branch connects a git branch to your app. A push builds what changed and rolls it out across customer installs in ordered install groups, with a plan and an approval for each group. Pull requests can get a plan-only preview.

Docs: https://docs.nuon.co/concepts/app-branches.md

## Control changes with policies

Policies written in Open Policy Agent Rego or Kyverno are evaluated at build time and deploy time. A policy can deny the change or warn. Kyverno policies are available on AWS installs.

Docs: https://docs.nuon.co/concepts/policies.md

## Scoped permissions and break glass

Operation roles scope the runner to the task at hand. Break glass grants higher access for an incident and records when it was granted, what ran, and when it was removed.

Docs: https://docs.nuon.co/concepts/operation-roles.md

## Detect drift

Scheduled or manual drift scans compare what is running in an install with its config and list each drifted resource with expected and actual values.

Docs: https://docs.nuon.co/concepts/workflows.md

## Actions and runbooks

Actions run scripts inside an install for debugging and maintenance. Runbooks turn a multi-step procedure, such as a version upgrade or a database migration, into one repeatable artifact you run on any install.

Docs: https://docs.nuon.co/guides/runbooks.md

## Health checks across every install

Nuon checks the components running on each install regularly, so you can see live status per install.

Docs: https://docs.nuon.co/guides/health-checks.md

## Operate the fleet from an agent

The Nuon Model Context Protocol (MCP) server connects a coding agent to the control plane to read apps, installs, workflows, logs and health. It lists read tools only by default.

Docs: https://docs.nuon.co/guides/agents/overview.md

Related: https://nuon.co/what-is-nuon.md, https://nuon.co/architecture.md, https://nuon.co/llms.txt