Maintenance windows people actually agree to.
The wizard already knows the owner, the system's cadence, and what is booked that night. All that is left to decide is the night.
A dated, owned, approved window
The problem
The coordination is the work.
The list is ready and the deployment tool is ready, and between them stand thirty system owners and a calendar. That is two months of correspondence nobody records, ending in a window somebody may have approved.
What it looks like
One event
| Exposure tier | Cadence | Facing |
|---|---|---|
| B2B | 3 months | External |
| Tier 1 | 3 months | External |
| Tier 2 | 3 months | External |
| Tier 3 | 6 months | Internal |
| MGMT | 6 months | Internal |
Where a host's tiers disagree, the most external one wins: over-patching an internal box costs a window, under-patching an externally-reachable one costs exposure.
- 01
Update type
Each update type declares what it needs: which fields, which checklist, which mail template and which SMS. You define it once.
- 02
Hosts
Pick from the inventory, paste a list out of Excel, or arrive from a patch row with the hosts already selected. The same picker handles databases and network equipment.
- 03
Owner and contacts
The system owner is loaded from the inventory, and their phone and address from Active Directory. Whoever was involved last time is offered again.
- 04
The window
A date and a start and end. Regulaxy checks the connected systems and warns before the save if something is already booked at that time.
- 05
Confirm and send
A review screen, then two calendar invites, a scheduled SMS, and a ticket in your ITSM if the update type calls for one.
The scheduling wizard, host-selection step, one filter applied
Waiting on sign-off to publish the demo estate
The wizard asks for nothing that already exists somewhere else.
- Host inventory
- Active Directory
- Exchange
- ITSM ticketing
- SMS gateway
Show us your worst window.
Bring the one that keeps slipping. Thirty minutes, your estate, no slides.