NetKeep
What it is
NetKeep is a self-hosted tool for collecting, versioning, comparing, and protecting network device configurations for ISPs and infrastructure teams. It uses Oxidized 0.37.0 to collect configurations and keeps each collected version in permanent Git history. Users can search, download, and compare versions with unified or side-by-side diffs. NetKeep supports read-only inventory synchronization with LibreNMS and NetBox, and can notify through email, signed webhooks, or Telegram. Full backups can be encrypted and sent to local storage or S3-compatible services; private Git mirroring is also available. Access roles include owner, administrator, operator, and reader, with optional TOTP two-factor authentication and passkeys. Safe mode collects, compares, and exports configurations without applying changes to equipment, but arbitrary Ruby or unreviewed drivers weaken that protection. NetKeep is free and its original code is licensed under AGPL-3.0. Installation requires a Linux amd64 or arm64 server, Docker Engine 25 or newer, Docker Compose plugin 2.24 or newer, and persistent storage. Configuration backups may contain credentials and sensitive network details.
For and against
For
- Keeps collected versions in permanent Git history.
- Offers unified and side-by-side configuration diffs.
- Supports read-only LibreNMS and NetBox synchronization.
- Encrypted backups can go to local storage or S3-compatible services.
Against
- Requires a Linux amd64 or arm64 server.
- Requires Docker Engine 25 or newer and Compose plugin 2.24 or newer.
- Community support is best-effort with no SLA.
- Backups may contain passwords, tokens, and network details.
The verdict
NetKeep provides versioned configuration collection and comparison with role-based access and backup options. Its server prerequisites and the sensitivity of configuration backups deserve attention before deployment.
Who it suits
NetKeep suits ISPs and infrastructure teams that need configuration history and comparisons in a self-hosted deployment. It is appropriate for teams able to meet its Linux and Docker requirements and manage sensitive backups.
Plans and prices
NetKeep
Self-hosted · Linux amd64 or arm64 server · AGPL-3.0
Read 4 Oct 2026 · github.com
On the record
- Access controls
- The product offers owner, administrator, operator, and reader roles, plus optional TOTP two-factor authentication and passkeys.github.com · read 4 Oct 2026
- Backups
- Full backups can be encrypted and sent to local storage or S3-compatible services, with private Git mirroring also available.github.com · read 4 Oct 2026
- Collection
- It uses Oxidized 0.37.0 as its configuration collection engine and stores collected versions in permanent Git history.github.com · read 4 Oct 2026
- Configuration history
- Users can search, download, and compare configuration versions with unified or side-by-side diffs.github.com · read 4 Oct 2026
- Data protection
- The maker warns that configuration backups may contain passwords, tokens, SNMP communities, and sensitive network details, and recommends encrypted storage and restricted administrative access.github.com · read 4 Oct 2026
- Deployment requirements
- Installation requires a Linux amd64 or arm64 server, Docker Engine 25 or newer, Docker Compose plugin 2.24 or newer, and persistent storage.github.com · read 4 Oct 2026
- Integrations
- NetKeep supports read-only inventory synchronization with LibreNMS and NetBox.github.com · read 4 Oct 2026
- License
- NetKeep's original code is distributed under the GNU Affero General Public License v3.0.github.com · read 4 Oct 2026
- Notifications
- Notification channels include email, signed webhooks, and Telegram.github.com · read 4 Oct 2026
- Purpose
- NetKeep collects, versions, compares, and protects network device configurations for ISPs and infrastructure teams.github.com · read 4 Oct 2026
- Safe mode
- In safe mode, NetKeep collects, compares, and exports configurations without applying changes to equipment; arbitrary Ruby or unreviewed drivers weaken this guarantee.github.com · read 4 Oct 2026
- Support
- Community support is best-effort with no SLA; commercial implementation, migration, or operational support is arranged by email.github.com · read 4 Oct 2026
