ProductsBackcheck
Backcheck
Know when a device has drifted. Fix it without losing the box.
Network changes fail quietly. A route is added during a change window, an old setting comes back, or a firewall rule no longer matches the approved baseline. Backcheck is the safety net for that problem.
Operators mark one configuration as authoritative. Backcheck compares it with what is actually running, flags policy violations, and keeps every snapshot as a versioned baseline. Putting a device back starts as a dry run unless someone explicitly chooses to apply the change. After a live change, Backcheck checks that the device is still reachable and healthy. If those checks fail, it rolls the change back.
Approved baselines
Keep one authoritative configuration for each device, taken from the running configuration, an inventory source, or an uploaded file.
Drift and compliance
See what was added or removed, and flag settings that break the rules for that device.
Safe changes
A dry run is the default. A live change is followed by a health check and an automatic rollback if the device stops answering.
Version history
Baselines are kept and numbered, so two versions can be compared without changing the device.
Credentials stay out of the console
The product refers to stored credentials and never displays the secret.
Roles and audit
Separate access for administrators, operators, and viewers. Device jobs and changes are recorded.
Alerts
The team is notified when a job finishes or fails.
One console
A dashboard, device inventory, configuration differences, job history, policies, and logs.
Configuration compliance and safe rollback for Cisco and other network vendors, with a dry run by default and an automatic health check.