Does Avalon do monitoring like SolarWinds?

No metrics collection, and that is a choice: monitoring should not stop at the network. We would rather drive a transverse tool, Zabbix or Centreon, that also watches servers and applications, than lock network indicators into one more silo. Avalon declares the devices it discovered there through a connector, host, groups, templates and SNMP profile included, so the inventory is never typed twice. It does alert on its own ground: it receives device syslog and emails you as soon as a line matches a watched pattern, and scheduled compliance audits report the deviations they found.

Can an existing configuration history be imported?

Avalon builds its own history from the first discovery of the estate. Importing a previous history is handled case by case.

How long does support for a new vendor take?

Usually five to ten days of development, excluding the firmware upgrade procedure, which requires a specific study.

A SolarWinds NCM alternative

SolarWinds Network Configuration Manager sits in a lot of estates, and it rarely arrives on its own: it is a module of the SolarWinds Platform, which requires a Windows server and a Microsoft SQL Server database in Standard or Enterprise edition, licensed separately. Its configuration templates and firmware upgrade jobs do the job as long as nothing goes wrong. Two reasons lead teams to look elsewhere: the need for a European product deployed on site, and what happens when an operation goes wrong across a whole estate.

Request a trial

The difference is in how the operation is conducted

A template describes what to send. It says nothing about the next forty minutes, across thirty devices, when one of them does not come back up.

Avalon implements its own upgrade procedures, platform by platform, and reports every step as it happens: image transfer, checksum verification, activation, reboot, then a check of the version actually in service once the device is back. Every step is recorded in the transaction, with its message and timestamp, and stays readable afterwards.

On top of that come the safeguards a template cannot express: a device protected by a redundancy group is refused rather than rebooted, a deployment window can be bounded in time, and the operation stops by itself beyond a number of failures you set, the rest of the batch marked untouched rather than attempted anyway.

Targeting based on the real state of the network

The selection rule is expressed against what the network actually contains, for example access ports carrying a given set of VLANs. That removes the longest phase of a project, the manual port inventory in a spreadsheet, and it stays repeatable to check that nothing has drifted.

Sovereignty and on-premises deployment

Avalon is published in France and deployed as a virtual appliance inside the customer network. No configuration data leaves their infrastructure, which meets the requirements of critical environments and public procurement.

Open and integrable

One hundred percent of the features are available through the API, with a NetBox integration and connectors to Zabbix and Centreon. Avalon fits into an existing operations chain made of Ansible, a source of truth and monitoring tools, instead of claiming to replace it.

Frequently asked questions

Does Avalon do monitoring like SolarWinds?: No metrics collection, and that is a choice: monitoring should not stop at the network. We would rather drive a transverse tool, Zabbix or Centreon, that also watches servers and applications, than lock network indicators into one more silo. Avalon declares the devices it discovered there through a connector, host, groups, templates and SNMP profile included, so the inventory is never typed twice. It does alert on its own ground: it receives device syslog and emails you as soon as a line matches a watched pattern, and scheduled compliance audits report the deviations they found.
Can an existing configuration history be imported?: Avalon builds its own history from the first discovery of the estate. Importing a previous history is handled case by case.
How long does support for a new vendor take?: Usually five to ten days of development, excluding the firmware upgrade procedure, which requires a specific study.

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

Compare on your network rather than on a datasheet

The trial runs for thirty days, covers up to 500 devices and sits on your own infrastructure. No meeting to book: you will compare on your own estate, not on a datasheet.