App Branches · Available now

One git push.
Your whole customer fleet.

In the order you choose, with approval gates where you need them.

Get a Demo Get Started

Read the docs

The fleet problem

Deploying into one customer's cloud is manageable. Ten is where the model breaks down.

App Branches are the continuous delivery pipeline for your fleet of BYOC customers.

Staged rollout

Bring order to BYOC deployed applications

Sort your customers into groups so that your changes get tested first, then deployed to least sensitive customers, most sensitive customers last.

Deployment plan

early-access order = 1

tier=early-access

acme-prod

staging order = 2

env=staging

globex-eu
initech-mumbai

production order = 3

env=prod

soylent-prod
hooli-sydney
tyrell-prod

Git-push delivery

Connect a branch. Push. Nuon runs the rollout.

Point an app branch at a repo, a directory, and a Git branch. Every push to that branch starts a coordinated update workflow across your installs.

branch.toml

name = "main"

[connected_repo]
repo      = "chartbase/app-config"
directory = "."
branch    = "main"

[[install_groups]]
name  = "early-access"
order = 1
[install_groups.label_selector]
tier = "early-access"

[[install_groups]]
name  = "production"
order = 2
[install_groups.label_selector]
env = "prod"

What a run does

01
fetch commit
Nuon picks up the commit you just pushed to the tracked branch.
02
fetch app config
Your TOML app config is parsed and validated from the branch directory.
03
building components and sandbox
Components build once and are diffed against the previous successful run, so unchanged components are not rebuilt.
04
plan install group
Each deployment group gets its own plan showing exactly what would change, then waits at an approval gate.
05
deploy install group
On approval the group deploys. Groups run in the order you set, and any group can be skipped.

Pull request previews

See the diff before you merge

Open a pull request against a tracked branch and Nuon runs a plan only. Nothing deploys. It comments the config diff on the pull request, rewrites that comment in place on every push, and sets a commit status so the change can gate your merge.

Nuon Preview — chartbase

Section	Added	Changed	Removed
components.api	—	image_tag	—
inputs	log_level	—	—
components.worker	—	replicas	—

nuon/preview — plan succeeded

Plan only, never deploy

A pull request run is plan-only by design. There is no path from an open pull request to a customer's infrastructure.

Quiet when nothing changed

If a pull request does not touch the app config, the preview stops early and says so instead of posting noise.

Connect the GitHub App once

Previews start arriving as soon as your org has the Nuon GitHub App connected for that repository's owner, public repositories included.

App Branches concepts Set up a branch

Start Shipping to Customer Clouds

Offer BYOC for any deployment architecture

Start your Nuon trial and try our example apps in minutes. No credit card required.

Start Trial Read Docs

Join our Slack community

One git push.Your whole customer fleet.