Updates and maintenance

nself Cloud keeps your stack current without surprise downtime. This page documents the channels, cadence, and your controls.

Channels

• Stable (default): Every Cloud tenant runs the latest stable release of the ɳSelf CLI plus tested plugin versions. Updates land on stable no sooner than 14 days after a stable tag is cut, unless it carries a security fix.
• Beta (opt-in): Early access to the next minor release. Landing here gets you new features 2–4 weeks earlier.
• Edge (opt-in): Rolling nightly builds. Not recommended for production.

Cadence

• Patch releases (1.0.x) : rolled out within 48 hours on stable
• Minor releases (1.x.0) : rolled out within 14 days on stable, after beta soak
• Security releases: Rolled out within 6 hours on all channels
• Plugin updates: Rolled out continuously; rollback available

Manual update button

You can trigger an update on demand from the dashboard. Click Run nself update on your server detail page. We will SSH into your VPS and run:

nself upgrade --channel stable --non-interactive

The update runs in the background and is safe to trigger while the stack is serving traffic, services are restarted one at a time with health checks in between. Expect 30–90 seconds of possible 502s as nginx reloads.

Maintenance windows

Non-urgent updates run in your configured maintenance window (default: Sundays 03:00 local time). You can change this in Settings → Maintenance.

Rollback

If an update breaks your stack, roll back from the dashboard. We keep the previous CLI binary, plugin set, and config snapshot for 7 days. Rollback redeploys the prior state and replays migrations in reverse where applicable.

Database schema changes are always tested forward and reverse on staging before being promoted to stable. A schema change that cannot be safely reversed is flagged as no-rollback: you'll be prompted to accept it before the update lands on your server.