Workflows
A workflow is the lifecycle of an install or a component. It plans the change, surfaces a diff, runs through any approvals you’ve configured. Each workflow run’s logs and step state are visible in the dashboard, CLI, and TUI. How it works → WorkflowsHealth Checks
Nuon checks the health of every component on every install, with no agent to install. Helm chart and Kubernetes manifest components are checked about once a minute. Terraform components get a health status when you add an HTTP or TCP probe, or a custom check. When a component or an install becomes unhealthy, and when it recovers, Nuon sends an alert to Slack or a webhook. Each component and install keeps 90 days of timeline and uptime. How to → Health ChecksInstall Telemetry
Install telemetry is the logs, metrics, and traces your application produces while running in a customer’s cloud account. Nuon can forward this data to your observability backend so you can monitor performance and troubleshoot issues across installs. Forwarding is off until you set it up, and it needs a Nuon BYOC deployment. Without it, Nuon stores only the logs of its own operations and the output of your actions. Application logs stay in the customer’s account. How it works → Install TelemetryAudit Logs
Install runners on AWS, Azure, and GCP can forward deployment, action workflow, and sandbox audit events directly to a customer-controlled OTLP logging backend. The destination and credentials remain in the customer’s cloud account. Only Nuon audit events are forwarded, not application logs or general runner logs. How to → Export Runner Audit LogsActions
An action is a script you run on a live install. The runner executes it inside the customer’s account, so you need no SSH orkubectl access to the customer’s network. Define it in TOML, point it at a repo, and set environment
variables. It runs on a cron schedule, on a lifecycle event such as post-deploy-component or pre-reprovision, or on
a manual trigger. The output and run history stay in Nuon.
During an incident, run a one-off command with an adhoc action without changing your app
config. Chain actions and deploys into a repeatable procedure with a runbook.
Typical uses: database migrations, maintenance scripts, collecting logs, and custom
checks that the built-in health checks do not cover.
How it works → Actions
Database Migrations
There are three ways to run migrations across installs: a Kubernetes Job that an action starts after each deploy, an init container in your app’s pods, or an action that runs a container image on the install runner. Use an action with apre-deploy-component trigger when the migration must finish before new pods start. A failed migration action pauses
the deploy until someone retries or skips it.
How to → Database Migrations