Skip to main content
October 15, 2026

BYOC telemetry

Every install’s logs, metrics, and traces in your backend.
  • Apps send OpenTelemetry to a private OTLP endpoint in each install
  • The runner forwards it to your relay, which exports to any OTLP backend
  • Records are stamped with verified nuon.org.id, nuon.app.id, and nuon.install.id
  • No backend credentials in customer accounts
  • Customers can disable the endpoint in their stack
  • Org default plus per-install overrides

Install telemetry

Set up install telemetry


Improved UI

Track rollouts and changes across every install.
  • App branches are each app’s landing page
  • Install pages show commits behind the tracked branch
  • Active deployments listed above history
  • Actions, runbooks, and deployments record who triggered them
An app branch overview tracking acme/payments with its latest run, overlaid by an install's deployment history showing its three most recent deployments Rolling out now. Ask us in your shared Slack channel to turn it on.

Deprovisioning

Choose what stays in the customer’s account on teardown.
  • [teardown] retain removes listed resources from state and leaves them running
  • The teardown plan marks each retained resource with a Retain action
  • The plan fails if a retained resource depends on something being destroyed
  • apply_on_teardown = false skips a policy during teardowns and keeps it on for deploys
  • Failed plan steps can be skipped
  • Deprovisions show on the install’s deployments page
components/database.toml
policies.toml

Retaining resources on teardown

Skipping policies during teardown


Other updates in this release

Scheduled runbooks

Runbooks can run on a cron schedule.

Runbooks

AWS cloud connections

AWS access through short-lived OIDC credentials. Select a connection when creating an install.

Cloud connections