Deploy on push

Once an app is live, you don’t have to ask for a deploy every time you ship. Turn on auto-deploy and every push to the branch you’re watching rebuilds the app from the new commit and rolls it out — automatically, with every deploy on the record. It’s continuous delivery without a pipeline to write, a runner to keep alive, or a deploy key to rotate.

Turn it on

Auto-deploy is set per app, in the console:

1. Connect the repo’s GitHub account once — the nyxory GitHub App. That’s what lets nyxory hear about your pushes.
2. Open the app in the console and switch Auto-deploy on.
3. Pick the branch to watch — your main, a staging branch, whatever maps to that environment.

That’s the whole setup.

What happens on a push

Push to the watched branch and GitHub notifies nyxory; the nyxory agent picks it up, rebuilds the image from the new commit, applies it, and records the deploy. A failed build leaves the running version untouched — a bad push doesn’t take production down. You watch it land the same way as any deploy: in the console, or from your coding agent.

Good to know

• It’s a console setting. Auto-deploy is toggled per app in the console, along with the branch to watch — there’s no CLI or MCP switch for it today. Your coding agent deploys on demand; auto-deploy covers the hands-off path.
• Restores pause it. Restoring an app from a backup pauses its auto-deploy while the restore settles, so a push mid-restore can’t race it.
• One branch, one environment. Point a production app at main and a staging app at staging; each app watches its own branch, so the right commit always lands in the right place.

Related: Deploy from a private repo · Day-2 operations