How it works

From access to history, with security.

Each collection is validated before it enters history. If a run is rejected, the last valid version remains available.

Operational flow

A simple process, from access to history.

Configure once. Then L3 Backups runs, validates, and organizes versions automatically.

Validate access and schedule the runs.

Review the results and access reliable versions in history.

When something goes wrong

Every interruption is recorded, may trigger retries, and does not replace reliable versions in history.

An incomplete or invalid run records the reason and does not replace reliable versions in history.

Retries, notifications, and alerts show when collection fails and when it returns to normal.

Execution steps and sent commands are recorded to support analysis and auditing.

Rotation happens only after a new valid version is accepted, avoiding the removal of reliable versions too soon.

Terms without jargon

Configuration backup: A copy of a configuration at a point in time for inspection, comparison, and manual recovery.
Validated backup: A collection whose response passed semantic rules before being accepted as a valid version.
Dry Run: A test of the template on the real device without creating a backup or changing history.
Host Key: The SSH server cryptographic identity, validated before credentials are sent.
Backup template: A reusable set of commands and parameters that defines how the configuration is collected.
Retention: The maximum number of versions kept per device — not a duration in days.
Comparison: A view of added, removed, or changed lines between two versions.

See how the process keeps the last valid version when a collection is rejected.

The 14-day free trial is for customers who have never subscribed. It starts after approval and assisted activation.