Managed Deployment Window

A release you are nervous about, run outside business hours by someone who has done it before. You hand us the version to ship; we rehearse the rollback first, run the release, verify the application afterward, and tell you which of those happened. If it has to go back, it goes back inside the window and you hear it from us rather than from a customer.

What you get

• A window outside your business hours, agreed with you in advance
• A rollback rehearsed before the release rather than improvised during it
• A backup or snapshot taken immediately before the change
• Post-deploy verification: the application answers, the critical paths work, the error rate is where it was
• A short written record of what shipped, when, and everything we checked

What this does not cover

• Writing or fixing the release. We ship the version you give us; if it does not work, the rollback is included and the fix is a Bug Fix Block.
• A second attempt. One window is one release — if the first is rolled back and you want to try again with a corrected build, that is a second window.
• A clean rollback from a database migration that cannot be reversed. Tell us before booking: an irreversible migration means the only way back is a restore from backup, with the data loss that implies, and we will put that in writing before we run anything.
• Deciding whether the release should ship. We will say what we think; the call is yours.

Who it fits

A release that matters to a team that would rather not do it alone at nine in the evening. If you ship more than once a month, a CI/CD Pipeline Setup at $540 costs less than a year of windows and leaves you able to deploy without us.