explaingit

kulunkilabs/vibenetbackup

Analysis updated 2026-05-18

50PythonAudience · ops devopsComplexity · 3/5LicenseSetup · moderate

TLDR

A self-hosted tool that automatically backs up router, switch, and firewall configurations on a schedule, with change detection and version comparison.

Mindmap

mindmap
  root((repo))
    What it does
      Backup network configs
      Change detection
      Retention rotation
    Tech stack
      Python
      Docker
      SQLite
    Use cases
      Homelab backups
      Multi vendor devices
      Diff comparisons
    Audience
      Network admins
      Homelab hobbyists

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Automatically back up configurations from Cisco, Juniper, MikroTik, and other network devices on a schedule.

USE CASE 2

Store backups in local disk, Git, and SMB destinations at once with rotating retention.

USE CASE 3

See what changed between two device configuration backups in a diff view.

USE CASE 4

Get Slack, Discord, or email alerts when a scheduled backup job runs or fails.

What is it built with?

PythonDockerSQLiteNetmiko

How does it compare?

kulunkilabs/vibenetbackuphjcheng0602/paperwisepyvista/pyvista-cad
Stars505050
LanguagePythonPythonPython
Setup difficultymoderatemoderatemoderate
Complexity3/53/53/5
Audienceops devopsresearcherresearcher

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Docker Compose install requires setting a secret key and admin password before first run.

In plain English

VIBENetBackup is a tool for automatically saving copies of your network device configurations, the settings files that tell routers, switches, and firewalls how to behave. Losing those configurations to a hardware failure or misconfiguration can be a serious problem, so this tool keeps an ongoing backup history you can restore from. It connects to network devices from a wide range of vendors, including Cisco, Nokia, Arista, Juniper, MikroTik, HP/Aruba, Dell, pfSense, and Proxmox, using standard protocols like SSH and SCP, plus vendor-specific APIs for pfSense/OPNsense and Proxmox. You set up a schedule, and it pulls the current configuration from each device automatically. When a configuration changes, it detects the difference using a SHA256 checksum comparison and can show you a diff view of exactly what changed. Backups can be stored in several places at once: on local disk, pushed to a Git repository such as GitHub, Gitea, or Forgejo, or saved to an SMB network share, with optional gzip compression. A retention policy automatically removes old backups on a rotating schedule, keeping daily, weekly, and monthly snapshots so storage does not grow without limit. The tool runs as a web application with a Bootstrap-based dashboard where you can see your devices, trigger backups manually, browse backup history, and compare configuration versions side by side. It also has a full REST API for automation and can send notifications through over 100 services including Slack, Discord, Telegram, and email. Stored credentials are encrypted, and it supports connecting to devices at remote sites through an SSH jump host. It is written in Python and can be deployed with Docker or a one-line install script.

Copy-paste prompts

Prompt 1
Help me set up VIBENetBackup with Docker Compose to back up my homelab Cisco and pfSense devices.
Prompt 2
Show me how to configure an SSH jump host in VIBENetBackup for backing up devices at a remote site.
Prompt 3
Write a retention policy plan for VIBENetBackup that keeps daily, weekly, and monthly config snapshots.
Prompt 4
Explain how to use VIBENetBackup's REST API to trigger a backup for a specific device.

Frequently asked questions

What is vibenetbackup?

A self-hosted tool that automatically backs up router, switch, and firewall configurations on a schedule, with change detection and version comparison.

What language is vibenetbackup written in?

Mainly Python. The stack also includes Python, Docker, SQLite.

How hard is vibenetbackup to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is vibenetbackup for?

Mainly ops devops.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.