Service
The whole fleet on supported, patched software, upgraded in planned waves
We automate the software upgrades across your network fleet: a readiness check, a backup, the upgrade, and checks that confirm each device is back to normal. The upgrades run in parallel, wave by wave, inside your maintenance windows, and HA pairs fail over so the service stays up.
Measured impact
What changes for your organization
- Today
Upgrades that take months
Each device is upgraded by hand, one window at a time, so a fleet-wide upgrade runs for months and the next release arrives before it ends.
With fleet upgradesThe fleet current, on schedule
Upgrades run in parallel waves inside your maintenance windows, so the whole fleet reaches the target release on a date you plan.
- Today
A growing patch backlog
Devices stay on old or unsupported releases because every upgrade costs engineer time, and known vulnerabilities stay open.
With fleet upgradesSupported, patched software
Every device runs a supported release, and a security patch reaches the fleet in the next campaign.
- Today
Every device a special case
Standalone units and HA pairs, physical and virtual, several models and releases: each one needs its own procedure and its own expert.
With fleet upgradesOne procedure for every variant
The same guarded sequence handles each kind of device in the fleet, so the result is consistent and any engineer can run it.
- Today
Outages during the window
A failed upgrade is found by users, and the way back is rebuilt by hand in the middle of the night.
With fleet upgradesService that stays up
HA pairs fail over during the upgrade, readiness checks stop a risky upgrade before it starts, and a backup is ready for rollback.
- Today
Proof pieced together
Which device runs which release, and whether it came back healthy, is collected from spreadsheets and device logs.
With fleet upgradesA record of every upgrade
The checks before and after each upgrade are kept, so the state of the fleet and every upgrade’s result are on record.
What we deliver
How it runs
The fleet’s size sets the number of waves; the sequence each device goes through stays the same.
Discovery
Your fleet, its releases and your upgrade process today, the target releases, and a plan of waves fitted to your maintenance windows.
Automation build
Readiness checks, backup, upgrade and post-upgrade validation for each kind of device in the fleet, built and tested in a lab.
Pilot wave
A first, small wave on production devices, with the results reviewed against the checks before the next wave starts.
Fleet waves
The rest of the fleet upgraded in parallel waves, each inside a maintenance window, with rollback ready for any device.
Handover
The automation documented and handed to your team for the next release, or run by us as an ongoing service.
Two ways to run it
An upgrade campaign
We build the automation for your fleet and run the upgrade to the target release with your team, then hand the automation over for the next one.
Upgrades as an ongoing service
We build the automation and keep running it, release after release, so the fleet stays on supported software year round.
Proof
- 500+ healthcare firewalls upgraded in less than 3 monthsAutomation for standalone firewalls and HA pairs, physical and virtual, with readiness checks, backups, comparison tests and up to 100 upgrades in one window.
- 10k+ firewalls upgraded a year by a Professional Services automation teamA Python library and Ansible Collection we built and run for a tier-1 firewall vendor, with 20+ pre- and post-validation checks and 100+ upgrades in a single window.
