What's included
- The systems MSPs actually run — Fortinet FortiGate, MikroTik RouterOS, Cisco IOS and IOS-XE, Cisco Small Business (SG/CBS), HPE Aruba (ArubaOS-Switch/ProCurve and CX), Ubiquiti EdgeOS (EdgeRouter and UniFi Security Gateway), pfSense, OPNsense, Juniper Junos, and Linux or any other device with a command you choose. DrayTek Vigor gets a snapshot of its main settings, because DrayOS has no command that prints the whole configuration.
- Read-only by design. For the built-in systems the agent only sends commands that print the configuration — it never changes a device.
- Only real changes count. Lines that change on every export — timestamps, secrets the device encrypts again each time, pager prompts — are left out, so a new version is kept only when the configuration really changed. The last 50 versions and every version of the last 30 days are kept.
- Compare any two versions side by side or unified, with a few lines of context or the whole file, and download any version as a text file.
- Alerts that show what changed. A configuration change opens an alert — a warning by default; off, warning or critical per device — and its email has a View the changes button. Backups failing two days in a row and a changed SSH host key raise alerts too.
- Planned work stays quiet. Use Expect a change, for 1 to 72 hours, before working on a device: what changes in that window is stored as expected, without a change alert, and a closing backup at the end becomes the new reference.
- Credentials stay in the vault. The sign-in is picked from the client's credentials vault, never typed in the form. The queued command carries only the run's number; the agent fetches the job over HTTPS with its own credential and never logs or keeps the password.
- SSH host keys pinned. A device's key is remembered on first use; if it changes, backups fail and a critical alert opens until an administrator checks the device and trusts the new key.
- Secrets handled with care. MikroTik exports leave secrets out unless you turn them on for that device; pfSense and OPNsense configurations always contain secrets, so only administrators open them — and every view is recorded in the audit log.
- On a schedule, or now. One backup a day per device, at its own time; Back up now for any technician, Test connection for administrators.
How it works
- 01
Choose the collector
A Windows computer of the same client, with the agent, that reaches the device over SSH. Link an SNMP device you already monitor, or add the device on its own.
- 02
Choose the sign-in from the vault
Pick the device's system and the account kept in the client's credentials vault; Test connection checks it before the first backup.
- 03
Let it run
Every day the collector reads the configuration, and SLApp keeps a version when it changed.
- 04
Compare when something breaks
Open the versions, compare yesterday's with today's, and download the one you need.
What it needs
- A Windows computer of the client with the agent, kept up to date (it updates itself), on a network that reaches the device over SSH.
- SSH enabled on the device and an account for it in the client's credentials vault — plus the enable password for the Cisco and ArubaOS-Switch devices that ask for one, and shell access on pfSense and OPNsense, whose configuration is read from config.xml.
- Administrators add, edit and remove devices, test connections, trust new keys and open versions with secrets; technicians see the versions and comparisons, back up now and announce expected changes.
Network configuration backups
Daily configuration backups of firewalls, routers and switches over SSH, with versions, comparison and change alerts.