Does Oxidized have to be dropped to use Avalon?

No. Both can coexist during a transition, although the value of duplicate backups fades quickly.

Does Avalon require writing code?

Not for day-to-day use. Deployment and compliance rules are defined in the tool. The API remains available for those integrating it into an existing chain.

What if a vendor is not supported?

Integrating one usually takes five to ten days of development, excluding the firmware upgrade procedure.

When Oxidized and RANCID are no longer enough

Many network teams built their configuration backup on Oxidized or RANCID, and it works. What they got is a repository of configurations: it records faithfully, it judges nothing and it pushes nothing. Everything that comes after, compliance and deployment, stays on their plate.

Request a trial

What those tools do very well

Collecting configurations, versioning them and detecting changes. That is useful, proven and free of licence cost. There is no reason to drop them on principle.

Backing up is not deploying

Oxidized collects, versions and flags differences. It pushes no configuration, that is not its job. RANCID only does so through a loop of commands sent by its login scripts, with no notion of a transaction and no rollback.

Avalon builds on the configuration replacement primitives of the devices themselves: configure replace with a confirmation timer on Cisco, checkpoints on Aruba OS-CX. A switch that becomes unreachable mid-operation restores its previous configuration on its own, even when it is the link to Avalon that disappeared. A command-sending script can offer nothing of the kind.

The rest follows the same gap: firmware upgrades with checks and a stop on any anomaly, a map produced from the network itself, a history readable by the whole team.

Compliance checking against rules defined by the team
Configuration deployment targeted on the real state of the network
Upgrade campaigns with checks and a stop on any anomaly
A map generated from the network itself
A history readable by the whole team, not only by its author

A configuration repository does not tell you whether the network complies

A repository tells you what changed, not whether the observed state matches what was decided. The difference matters: a configuration can be identical to yesterday and still have been wrong for six months.

Avalon gathers the real state of the devices, VLANs, switchports, aggregates, network access control, DHCP snooping, hardware, and evaluates rules against it. A port outside the scope is reported as such rather than dropping out of the report, and an unreachable device is counted separately instead of coming back compliant for lack of data to contradict it.

Rules are composed visually from a source, filters and conditions, and run on demand or on a schedule, with a report and a summary e-mail.

Without giving up on-premises operation

Avalon is deployed as a virtual appliance inside the network, and one hundred percent of its features are available through the API. An existing chain made of Ansible and a source of truth keeps working, with Avalon as the executor rather than the replacement.

Frequently asked questions

Does Oxidized have to be dropped to use Avalon?: No. Both can coexist during a transition, although the value of duplicate backups fades quickly.
Does Avalon require writing code?: Not for day-to-day use. Deployment and compliance rules are defined in the tool. The API remains available for those integrating it into an existing chain.
What if a vendor is not supported?: Integrating one usually takes five to ten days of development, excluding the firmware upgrade procedure.

Offers

Avalon is available under a transparent yearly subscription, based on the number of managed IP devices alone.

Yearly subscription, no hidden fees
One license per device (switch stacks count as a single license)
Decreasing cost per device as your network scales
Guaranteed price stability, with no unexpected increases year over year
Every feature included, no add-on modules

Designed with network engineers

Benefit from a platform shaped through real-world deployments and continuous collaboration with network teams.

Real customers!

University Hospital of Limoges — Olivier H. Network Administrator

Airbus Atlantic — Mathieu S. Network & Security Architect

Keep your backups, add the rest

Thirty days, up to 500 devices, on your own site, no meeting to book. In one evening, compare what you get with what you have been maintaining for years.