Oxidized is a network device configuration backup tool. It's a RANCID replacement!
3.4k
Stars
1k
Forks
63
Open issues
30
Contributors
AI Analysis
Oxidized is a network device configuration backup tool designed as a RANCID replacement, supporting 130+ operating system types. It serves network administrators and infrastructure teams who need automated, extensible configuration backups with REST API control and multi-output capabilities (Git, HTTP, file). It is specialized for network operations and not a general-purpose backup solution.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Ruby-based network config backup tool serving ops teams with 130+ device OS support and Git-tracked change history.
Oxidized is a network device configuration backup and management tool written in Ruby, positioned as a successor to RANCID. It automates config retrieval from 130+ network operating systems, stores changes in Git with attribution, and exposes a REST API for integration. Adopted primarily by network operations teams in organizations already comfortable with Ruby infrastructure. Not a dominant market player, but maintains a stable user base and active maintenance as of mid-2026.
Created April 2013 as a RANCID replacement during the rise of configuration-as-code practices. RANCID was aging and written in Perl; Oxidized brought Ruby-based modularity and Git integration. The project grew to ~3,400 stars by 2026, reflecting solid niche adoption without explosive growth.
Early adoption in network engineering communities familiar with Ruby; steady addition of device models (130+ supported); gained traction through REST API and Git blame integration. Growth has plateaued to ~8 stars per week (recent trend), indicating mature, stable user base rather than expansion phase. No major acceleration visible in metadata.
Adoption not formally verified through public case studies or documented deployments in README. However, presence of enterprise-grade features (syslog integration, REST API, Git blame tracking, multiple output targets, hooks for Slack/AWS/GitHub) and 1,039 forks suggest real-world use. Network operations is a practical, mission-critical domain where tools gain adoption through word-of-mouth and RFC references rather than public testimonials. 3,441 stars in a niche category (network config backup) is consistent with meaningful production adoption, though not at enterprise SaaS scale.
Based on README, appears modular with pluggable sources (CSV, SQL, MySQL, HTTP), outputs (Git, HTTP, File, Git-Crypt), and hooks (Slack, AWS SNS, GitHub). Likely uses Ruby threads for concurrent device polling with configurable retrieval intervals. Architecture supports 130+ device models via extensible model system. Cannot verify implementation details from README alone.
CI/CD badge present (GitHub Actions) indicating active testing, but coverage percentage not documented in README. Quality assurance appears present but not quantified.
Last push 2026-07-02 (5 days before analysis date) indicates active maintenance. Maintainer explicitly requests help in README (open call for additional maintainers). This suggests healthy engagement but possible resource constraints. Project has existed 13 years with continuous updates, signaling genuine sustainability rather than dormancy.
ADOPT IF: your team runs mixed-vendor networks, uses Git for infrastructure tracking, prefers Ruby tooling, and needs reliable config backup with change attribution. AVOID IF: you require commercial support, need a GUI-first experience, or are in organization standardized on Python/Go for DevOps. MONITOR IF: you are evaluating network config management solutions and want to understand whether Oxidized fits alongside broader IPAM/automation strategies.
Independent dimensions
Mainstream potential
3/10
Technical importance
6/10
Adoption evidence
5/10
- Maintainer explicitly requests additional help; single-maintainer projects can face capacity bottlenecks during security issues or major upgrades.
- Ruby dependency may be friction in organizations transitioning to Go/Rust for infrastructure tooling; could limit future hiring of contributors.
- 130+ device models imply high maintenance surface area for model updates as vendors release new OS versions; unclear how frequently models are updated.
- REST API and Gitter chat indicate active user community, but no evidence of formal change management or deprecation policy; breaking changes could impact production users.
- No adoption metrics or customer list visible; if project lost primary maintainer, community adoption depth is unverified.
Oxidized will likely remain a stable, niche-appropriate tool for network operations teams already comfortable with Ruby and Git. Growth will remain modest (~8 stars/week) unless major rewrite in Rust/Go occurs or a large vendor adopts it officially. Risk of gradual adoption decline if Python/Go alternatives improve.
Explore similar
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Language
- Ruby
- License
- Apache-2.0
- Last updated
- 23h ago
- Created
- 161mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
Top contributors
Recent releases
Similar repos
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
ytti/oxidized
this
|
3.4k | +12 | Ruby | 7/10 | 23h ago |
 Ragnt/AngryOxide
|
1.9k | — | Rust | 7/10 | 9h ago |
 redox-os/ion
|
1.7k | — | Rust | 6/10 | 2mo ago |
|
redox-os/redox
|
16.4k | — | Rust | 7/10 | 17h ago |
 rustic-rs/rustic
|
3.1k | — | Rust | 8/10 | 4d ago |
 oxc-project/oxc
|
21.9k | — | Rust | 9/10 | 6h ago |
Oxidized explicitly positions as modernization; provides Git integration and REST API RANCID lacks. RANCID still used in legacy environments; Oxidized appeals to teams wanting configuration-as-code practices.
Netbox is a broader IPAM/inventory platform; Oxidized is config-backup focused. Teams often use both: Netbox for inventory, Oxidized for change tracking. Not direct replacement.
Napalm handles device abstraction and automation; Oxidized handles continuous backup + versioning. Complementary rather than competitive; could potentially be combined.
Terraform manages desired state; Oxidized captures actual state backups. Orthogonal tools serving different purposes in infrastructure pipeline.
AngryOxide appears to be Rust rewrite/alternative; has fewer stars but modern language choice. Metadata insufficient to confirm if direct replacement or different niche. Cannot evaluate from provided information.
