Core
Perfect for getting started with NCM visibility.
- Automated Backups
- Basic Compliance
- Community Support
Network automation pushes changes. Configuration management safeguards them. Learn why you need both to run a reliable, secure, and compliant network, and how rConfig facilitates the perfect balance.
Automation Platforms can push changes at lightning speed, but speed without visibility is a risk. rConfig provides the safety layer, ensuring you know exactly what changed, who changed it, and if it broke anything.
To build a resilient network, it is critical to view Network Configuration Management (NCM) not as a legacy task, but as a specialized, high-value discipline of network automation.
General-Purpose Automation handles the broad execution of tasks, provisioning, bulk updates, and orchestration. It is powerful but often blind to the nuanced state of the network.
Automation-First NCM provides deterministic automation. It automatically captures state, validates intent, enforces policy, and ensures you have automated rollback capabilities. It is the guardrail that makes high-velocity automation safe.
Confusing automation with management invites risk. Understanding the role of each unlocks faster deployments, better security, and significantly reduced downtime.
Running massive automation scripts without NCM is like driving a racecar without brakes. If a script pushes a bad config to 100 switches, you have an automated outage.
NCM ensures you have a recent, working backup effectively insuring your automation efforts. If an automated change fails, NCM gets you back online instantly.
Automation changes things fast, which scares auditors. NCM logs every change and validates it against policy, satisfying compliance requirements even at high velocity.
Mature organizations decouple execution (automation) from validation (NCM). This separation of duties prevents errors and enables scalable, confident network operations.
They complement each other, but they are not the same. Here is how they stack up.
| Feature / Aspect | Network Automation | NCM (rConfig) |
|---|---|---|
| Primary Purpose | Execute changes and provision services efficiently. | Automate state validation, compliance, and intent verification. |
| Key Tasks | Scripting, bulk updates, ZTP (Zero Touch Provisioning). | Automated backups, continuous drift detection, policy enforcement. |
| Typical Tools | Ansible, Python, Terraform, Chef. | rConfig (Automation-First), SolarWinds NCM, Oxidized. |
| Risk Profile | High speed can lead to high-impact errors ('fat finger' at scale). | Mitigates risk through deterministic automation and rollback. |
| Value Add | Speed, consistency, reduction of manual toil. | Safety, assured state, and automated governance. |
rConfig unites the speed of automation with the reliability of NCM. Automate safely with a platform designed to watch your back.
Before you automate a change, rConfig takes a snapshot. If the script fails, you have an immediate rollback point.
Did your automation script miss a device? Or did someone make a manual change? rConfig catches all drift instantly.
Define 'golden' configurations. rConfig ensures that both automated and manual changes adhere to security standards.
rConfig includes a built-in task manager for running PHP/Python command scripts, bridging simple automation needs directly in the console.
Connect with NetBox, HashiCorp Vault, Zabbix, ServiceNow, and Slack to make rConfig the source of truth for your automation pipeline.
No per-device taxing. rConfig lets you manage scaling networks without worrying about licensing costs exploding.
HealthcareA hospital network needed to update firmware on 200 switches. They used Ansible for the rollout, but rConfig provided the pre-change backup validation and post-change compliance check to ensure no medical devices lost connectivity.
ManufacturingA factory automated the deployment of ACLs to 500+ IoT gateways. rConfig detected 12 devices that failed to apply the config correctly, alerting the team before production lines were impacted.
Financial ServicesA bank used scripts to rotate passwords weekly. rConfig tracked every version change, providing auditors with a perfect log of exactly when and how passwords were changed, satisfying PCI-DSS requirements.
Choose the right edition to balance your automation strategy.
Perfect for getting started with NCM visibility.
For growing teams needing automation & scale.
Full-scale governance for mission-critical networks.
Clarifying the role of NCM in an automated world.
Network automation focuses on executing changes, like pushing configurations or provisioning devices. NCM (Network Configuration Management) focuses on tracking those changes, maintaining backups, enforcing policies, and ensuring you can roll back if automation fails.
Ansible and Python are powerful automation tools, but they aren't dedicated systems of record. rConfig acts as your safety net, providing version control, compliance auditing, and automated backups that scripts alone don't offer.
No, rConfig complements them. You can continue using your scripts, but integrate rConfig to capture the state of the network before and after changes, ensuring you always have a 'known good' configuration to revert to.
Manual documentation becomes obsolete the moment a change is made. NCM provides dynamic, real-time documentation by pulling live configurations and highlighting differences automatically.
rConfig automates compliance checks against your configurations. It flags violations in real-time, helping you prove adherence to standards like PCI-DSS, HIPAA, and NIS2 without manual audits.
Not at all. rConfig is designed for rapid deployment. You can install it, discover devices, and start backing up configurations in minutes, not weeks.
rConfig gives you the safety net your automation strategy needs. Backup, audit, and track every change automatically.