Skip to main content
NodePad Enterprise upgrades are designed to fail fast and fail safe. The full upgrade and rollback playbook ships with your deployment package and is matched to the posture you run.

​
How upgrades work

Pinned versions

You pin to a specific version. Tags are immutable, so the version you pin is the version you keep until you choose to move.

Pre-upgrade migrations

Schema migrations run before the new application version takes traffic. If migrations fail, the upgrade aborts and your existing version keeps serving.

Smoke-test window

Each upgrade includes a recommended smoke-test window — health checks, sign-in, canvas load, model streaming.

Documented rollback

Each release ships with the rollback procedure. Destructive migrations are flagged in release notes.

​
What you receive

The deployment package includes the full upgrade playbook with commands matched to your posture, a database backup procedure, and a rollback flow that covers both reversible and migration-incompatible cases.

Need the playbook?

Reach out to the team. The upgrade playbook is delivered with your deployment package.