What is Oxidized used for?

Oxidized is an extensible tool that backs up network device configurations on a schedule and is positioned as a replacement for RANCID. It is a good fit for teams migrating off RANCID and tracking who changed a router or switch configuration.

Is Oxidized open source?

Yes. Oxidized is open source under the Apache-2.0 licence. Its source code is on GitHub at ytti/oxidized and is written mainly in Ruby.

Yes. Oxidized is open source, so the software itself is free to use.

Can I self-host Oxidized?

Yes. Oxidized can be self-hosted on your own server or infrastructure; there is no official hosted version.

What is Oxidized an alternative to?

Oxidized is an open-source alternative to Auvik. Other open-source alternatives to Auvik include NetBox, NetAlertX and Scanopy.

Is Oxidized actively maintained?

Yes. The most recent commit to Oxidized was on 30 September 2026, and the latest release is 0.37.0, published on 20 May 2026. The project has 3.6k stars on GitHub.

Oxidized: open-source alternative to Auvik

About Oxidized

Oxidized is an open-source tool that backs up the configuration of network devices, such as equipment running IOS or JunOS. It is presented as a replacement for RANCID, the older tool many network teams have used for the same job. It is described as light and extensible, and it supports well over 100 different device operating system types.

It adjusts its worker threads automatically to hit the retrieval interval you configure. A REST API lets you move a node to the front of the queue, reload the node list, fetch configurations and view the version history and diffs of a device. It can also listen for syslog events from IOS and JunOS devices to trigger a fetch as soon as a configuration changes, and with the git output module, git blame then shows who made each change.

Node inventories can come from CSV files, SQL databases, SQLite, MySQL or an HTTP source, and configurations can be written to Git, git-crypt, HTTP or plain files. Hooks can send notices through services such as Slack, AWS SNS or XMPP. It is written in Ruby, licensed under Apache-2.0 and installable on Debian, Ubuntu, Red Hat family systems, FreeBSD or in Docker and Podman. The maintainer is asking for additional maintainers.

Key features

Scheduled configuration backups for network devices
Supports over 130 device operating system types
REST API for nodes, configurations and diffs
Syslog-triggered fetches on configuration changes
Git output with per-change author tracking
Hooks for Slack, AWS SNS and XMPP notices
Node sources from CSV, SQL or HTTP

Good fit for

→Teams migrating off RANCID
→Tracking who changed a router or switch configuration

Built with: Ruby
Tags: network; backup; configuration-management; rancid; ruby; self-hosted; nms; git

Oxidized: questions and answers

What is Oxidized used for?: Oxidized is an extensible tool that backs up network device configurations on a schedule and is positioned as a replacement for RANCID. It is a good fit for teams migrating off RANCID and tracking who changed a router or switch configuration.
Is Oxidized open source?: Yes. Oxidized is open source under the Apache-2.0 licence. Its source code is on GitHub at ytti/oxidized and is written mainly in Ruby.
Is Oxidized free?: Yes. Oxidized is open source, so the software itself is free to use.
Can I self-host Oxidized?: Yes. Oxidized can be self-hosted on your own server or infrastructure; there is no official hosted version.
What is Oxidized an alternative to?: Oxidized is an open-source alternative to Auvik. Other open-source alternatives to Auvik include NetBox, NetAlertX and Scanopy.
Is Oxidized actively maintained?: Yes. The most recent commit to Oxidized was on 30 September 2026, and the latest release is 0.37.0, published on 20 May 2026. The project has 3.6k stars on GitHub.