The OpenText Network Automation Alternative for Network Configuration Management
Looking for an OpenText Network Automation alternative, or still calling it by its earlier name, HP Network Automation? rConfig is a like-for-like alternative: multi-vendor config backup, change detection, compliance, firmware and automation.
OpenText NA is priced on request and licensed per node inside the OpenText NOM suite, with compliance authoring held back for the Ultimate edition. rConfig publishes its prices, Core is free and open source with no device limit, and it runs entirely on your own infrastructure, benchmarked in public at 50,000 devices on a single host.
Self-hosted on Linux · Free, open-source Core · Prices published · Sources dated
The short answer
Yes, rConfig is a like-for-like alternative to OpenText Network Automation, formerly HP Network Automation. It covers multi-vendor configuration backup, change detection, compliance, firmware and automation, the same job Network Automation does. OpenText NA is priced on request and licensed per node inside the OpenText NOM suite, and compliance policy authoring sits in the Ultimate edition only. rConfig publishes its prices, and Core is free and open source with no device limit, running entirely on your own infrastructure and benchmarked in public at 50,000 devices on a single host.
Who replaces OpenText Network Automation, and why
Three reasons teams evaluating OpenText Network Automation, HP Network Automation or HPNA land on rConfig.
A price on the page
NA has no public price and licenses nodes, not devices. OpenText's own licence terms say a switch “may have three nodes”. rConfig's prices are published, in your currency, on the rConfig pricing page.
Architecture you can check
Our scale evidence is public, method included, rather than a suite-wide device count with no methodology behind it.
One product, one owner
OpenText Network Automation has had four owners since 2007: HP, HPE, Micro Focus, and now OpenText. rConfig has been built by the same team since 2010.
rConfig vs OpenText Network Automation, like for like
Every OpenText cell names its source. Sources checked: 26 September 2026. Where OpenText publishes nothing on a point, the cell says so rather than claiming OpenText lacks the capability. OpenText, Network Automation, HP and Micro Focus are trademarks of their respective owners. rConfig is not affiliated with OpenText, HP, HPE or Micro Focus. This comparison is provided for evaluation purposes and describes competitor capabilities in general terms. All sources are listed in the dated sources.
- What mattersProduct and packagingOpenText Network AutomationNA standalone, or inside NOM (Express, Premium, Ultimate). Packaged with NNM as Network Observability from 25.429rConfigCore, Starter, Standard, Enterprise. Vector for distributed and MSP estates18
- What mattersLineageOpenText Network AutomationrConfigBuilt by the same team since 2010, open source since 201228
- What mattersLicenceOpenText Network AutomationCommercial, closed source. Perpetual or subscription6rConfigCore free and open source. Commercial editions by device band18
- What mattersLicence unitOpenText Network AutomationManaged node. A switch “may have three nodes”4rConfigDevices18
- What mattersPublished pricingOpenText Network AutomationNone. Contact sales2rConfigYes, in your currency18
- What mattersFree edition or trialOpenText Network AutomationNot published17rConfigCore, no device limit18
- What mattersDeploymentOpenText Network AutomationrConfigSelf-hosted on Linux, containers or air-gapped, in every edition19
- What mattersDistributed collectionOpenText Network AutomationNA Satellite, licensed separately4rConfigVector Agent: outbound-only TLS, no inbound ports, up to 1,000 devices per agent23
- What mattersPublished scaleOpenText Network AutomationSuite claim, “120K configuration devices”2rConfig50,000 devices in 21 minutes on one host, method published2021 Reference architecture past 100,000 nodes22. See how rConfig counts devices and rConfig reference architecture.
- What mattersHigh availabilityOpenText Network AutomationNot published in the pages we reviewedrConfigHA and BCP patterns in Enterprise32
- What mattersVendor coverageOpenText Network AutomationrConfigCisco, Juniper, Arista, Fortinet, Palo Alto, Huawei, Nokia, MikroTik, HPE, Aruba and 200 more29
- What mattersOT, ICS and IoTOpenText Network AutomationNot listed in the driver pack material10rConfig
- What mattersBackup, diff, rollbackOpenText Network AutomationStores every config, compares it to running, rolls back1rConfigBackup, diff, rollback, real-time change alerts19
- What mattersComplianceOpenText Network AutomationPolicy authoring and auto-remediation in the Ultimate edition only. PCI DSS and DISA STIG content packs311rConfig
- What mattersFirmware and imagesOpenText Network AutomationSoftware image deploy (Premium and above)2rConfigScheduled push over SCP, TFTP or API34
- What mattersWorkflowsOpenText Network AutomationChange plans, scripts, Git, GitLab, Ansible1rConfigScripts, REST API, approval workflows19
- What mattersMonitoringOpenText Network AutomationPairs with NNMi in the same suite9rConfigNot a monitoring tool. Integrates with Zabbix, Checkmk, PRTG, AKIPS, Statseeker31
- What mattersMulti-tenancy and MSPOpenText Network AutomationNot published2rConfig
- What mattersAIOpenText Network AutomationAviator recommendations in OpenText Network Observability (26.2)8rConfigBring your own keys or a fully local LLM, runs inside your environment. MCP server for AI agent access30
- What mattersFootprintOpenText Network AutomationNamed references incl. Orange Spain, IPC, Nomura, Turk Telekom. No install base figure published12rConfig
| What matters | OpenText Network Automation | rConfig |
|---|---|---|
| Product and packaging | NA standalone, or inside NOM (Express, Premium, Ultimate). Packaged with NNM as Network Observability from 25.429 | Core, Starter, Standard, Enterprise. Vector for distributed and MSP estates18 |
| Lineage | Opsware NAS, then HP (2007), HPE (2015), Micro Focus (2017), OpenText (2023)13141516 | Built by the same team since 2010, open source since 201228 |
| Licence | Commercial, closed source. Perpetual or subscription6 | Core free and open source. Commercial editions by device band18 |
| Licence unit | Managed node. A switch “may have three nodes”4 | Devices18 |
| Published pricing | None. Contact sales2 | Yes, in your currency18 |
| Free edition or trial | Not published17 | Core, no device limit18 |
| Deployment | On premises, managed by you or OpenText. Private Cloud from 25.257 | Self-hosted on Linux, containers or air-gapped, in every edition19 |
| Distributed collection | NA Satellite, licensed separately4 | Vector Agent: outbound-only TLS, no inbound ports, up to 1,000 devices per agent23 |
| Published scale | Suite claim, “120K configuration devices”2 | 50,000 devices in 21 minutes on one host, method published2021 Reference architecture past 100,000 nodes22. See how rConfig counts devices and rConfig reference architecture. |
| High availability | Not published in the pages we reviewed | HA and BCP patterns in Enterprise32 |
| Vendor coverage | “3,500+ devices across 250+ vendors”. Driver packs generally released every two months110 | Cisco, Juniper, Arista, Fortinet, Palo Alto, Huawei, Nokia, MikroTik, HPE, Aruba and 200 more29 |
| OT, ICS and IoT | Not listed in the driver pack material10 | SCADA, PLCs, specialised OT equipment. Vector Agent supports air-gapped and OT networks2723 |
| Backup, diff, rollback | Stores every config, compares it to running, rolls back1 | Backup, diff, rollback, real-time change alerts19 |
| Compliance | Policy authoring and auto-remediation in the Ultimate edition only. PCI DSS and DISA STIG content packs311 | Policy checks and compliance status from Starter, continuous checks and audit-ready reports from Standard. NIS2 and DORA evidence exports (V8 Pro, Vector)1933 |
| Firmware and images | Software image deploy (Premium and above)2 | Scheduled push over SCP, TFTP or API34 |
| Workflows | Change plans, scripts, Git, GitLab, Ansible1 | Scripts, REST API, approval workflows19 |
| Monitoring | Pairs with NNMi in the same suite9 | Not a monitoring tool. Integrates with Zabbix, Checkmk, PRTG, AKIPS, Statseeker31 |
| Multi-tenancy and MSP | Not published2 | Hierarchical RBAC. Vector Prism branded portal with mandatory MFA2524 |
| AI | Aviator recommendations in OpenText Network Observability (26.2)8 | Bring your own keys or a fully local LLM, runs inside your environment. MCP server for AI agent access30 |
| Footprint | Named references incl. Orange Spain, IPC, Nomura, Turk Telekom. No install base figure published12 | 10,000+ active users, 60+ countries, 80M+ devices under management (our own estimate, no phone home)2821 |
Where OpenText NA is a better fit
What you gain moving off OpenText NA
A move off a legacy appliance-and-suite model is also a chance to gain a distributed, self-hosted architecture built for scale and privacy.
Distributed architecture, benchmarked in public
A Vector Server, Vector Agents per site over outbound-only TLS with no inbound ports, and Vector Prism as the branded MSP portal. rConfig backs up over 50,000 devices in under 21 minutes on one host, method published, with a reference architecture built past 100,000 nodes.2320
Air-gapped, SSO, API and containers, every edition
Single sign-on, a REST API, container deployment and air-gapped deployment are not held back for a top tier. They ship in Core the same as they ship in Enterprise.19
Private by design
Self-hosted, with no phone home. AI runs with your own API keys or a fully local model, so configuration context never leaves your environment unless you choose to send it.30
OT and IoT backups
SCADA systems, PLCs, roadside signage, legacy voice and other specialised OT equipment, including API backups for devices with no CLI, with IEC 62443 compliance pressure in view.27
Licensing and pricing, side by side
Facts only. Nothing here is a quote, and your own agreement governs your terms. Last verified: 26 September 2026.
rConfig
- Core: $0, No device limit
- Starter: $2,999, up to 300 devices
- Standard: $4,799, up to 1,000 devices
- Enterprise / MSP: Custom, beyond 1,000 devices
Every edition includes a support tier. See rConfig pricing for prices in your own currency and rConfig edition comparison for what each edition includes.
Ready to move off OpenText NA?
Run rConfig alongside Network Automation while you validate device access, backups and diffs, then retire NA's schedules on your own timeline.
Export your device inventory and credentials from NA.
Install rConfig Core or Enterprise.
Import devices and map credentials, or point rConfig at HashiCorp Vault.
Run a first backup and diff it against your last NA snapshot.
Run both in parallel for one change cycle before retiring NA schedules.
OpenText Network Automation alternative: common questions
Is rConfig a good OpenText Network Automation alternative?
Yes, for teams that want the same job, multi-vendor configuration backup, change detection, compliance, firmware and automation, run as self-hosted software with a published price. rConfig Core is free and open source, so you can trial it in full before deciding.
What is OpenText Network Automation?
OpenText Network Automation, formerly HP Network Automation, is a network configuration management product with a long ownership history. It started as Opsware NAS, which HP completed its acquisition of in 2007. HP split into HP Inc. and Hewlett Packard Enterprise in 2015, HPE transferred its software business to Micro Focus in 2017, and OpenText completed its acquisition of Micro Focus in 2023, which is how the product carries the OpenText name today.
Is HP Network Automation the same as OpenText Network Automation?
Yes. HP Network Automation, HPE Network Automation and Micro Focus Network Automation are the same product under its earlier owners, and it is often referred to by the short name HPNA. OpenText Network Automation is that same product under its current owner.
How much does OpenText Network Automation cost?
OpenText does not publish a price for Network Automation. It is licensed by managed node rather than by device, and OpenText's own licence terms say a switch may have three nodes. Configuration backup is in the Express edition of Network Operations Management, change plans and software updates are in Premium, and compliance policy authoring and auto-remediation are in Ultimate only. You contact sales for a quote.
Is there a free alternative to OpenText Network Automation?
Yes. rConfig Core is free and open source with no device limit, so you can run scheduled backups, version history, diffing and compliance checks on your own devices at no cost before choosing a commercial edition.
Does rConfig replace OpenText NNMi?
No. rConfig replaces the configuration side of what OpenText's suite does, config backup, change detection, compliance and firmware, not NNMi's network monitoring. Keep the monitoring platform you already run and let rConfig own configuration management.
Can rConfig back up OT and IoT devices?
Yes. rConfig backs up SCADA systems, PLCs, roadside signage, legacy voice and other specialised OT equipment, including devices with no CLI via API backups, and the Vector Agent supports air-gapped and OT networks. See the industrial and OT network management case study. OpenText's own driver pack material does not list OT, ICS or IoT vendor support.
How does rConfig scale compared with OpenText NA?
OpenText states a suite-wide claim of 120K configuration devices, with no published method behind the figure. rConfig publishes its own benchmark, backing up over 50,000 devices in under 21 minutes on a single host, with the method behind it published, and a reference architecture built past 100,000 nodes.
Does rConfig support MSPs and multi-tenancy?
Yes, through rConfig Vector. Vector adds hierarchical role-based access control and Vector Prism, a branded customer portal with mandatory multi-factor authentication, for MSPs and distributed estates. OpenText does not publish multi-tenancy details for Network Automation.
Where is OpenText NA a better fit than rConfig?
Three places. Where you want monitoring and configuration from one vendor, NNMi plus Network Automation in one suite. Where you specifically need OpenText's vendor security advisory content and driver packs across 3,500+ device types, since rConfig is not a vulnerability intelligence product. And where a long maintenance window matters to you: OpenText Network Automation 25.2 is in current maintenance to 31 May 2029. See where OpenText NA is a better fit above.
How do we migrate from OpenText Network Automation to rConfig?
Export your device inventory and credentials from Network Automation, install rConfig Core or Enterprise, import your devices and map credentials (or point rConfig at HashiCorp Vault), run a first backup and diff it against your last NA snapshot, then run both systems in parallel for one change cycle before retiring your NA schedules. Rebuild the compliance policies you actually enforce first, not the whole library. See the move section above, or the rConfig pricing page to choose an edition.
One product, one owner, one published price
V8 Core is open source. Run it in parallel with OpenText Network Automation, confirm the backups and diffs on your own devices, and switch on your schedule rather than under a licence deadline.
Compare rConfig with other tools
Sources, checked 26 September 2026
- OpenText, Network Automation product page ("3,500+ devices across 250+ vendors", physical, virtual and SDN networks, Git and Ansible integration)
- OpenText, Network Operations Management product page (NOM editions Express, Premium, Ultimate; "120K configuration devices"; contact sales, no published price)
- Micro Focus/OpenText documentation, Network Automation 25.4 CLI reference (compliance commands "available only with the Network Automation Software Ultimate edition license")
- OpenText, Additional License Authorizations for Network Operations Management software products (ALA 5200-2005, 31 Aug 2026: licensed by managed node, "a switch (one Network Device) may have three nodes"; separate Satellite licence; "use Network Automation only as a complete product")
- OpenText, Network Automation product overview (deployment: "On-premises software, managed by your organization or OpenText")
- OpenText blog, why OpenText leads in network management and network observability in 2026 (perpetual on-premises and subscription licensing)
- OpenText community, Network Automation 25.2 release post ("Current Maintenance ends May 31, 2029"; Private Cloud deployment option; DISA STIG firewall content)
- OpenText community, what's new in OpenText NNMi, NA and NOM (15 May 2026: release history 24.4 to 26.2; Aviator credited to Network Observability in 26.2; EPSS scoring added in 24.4)
- OpenText, NOM 25.4 release readiness documentation (Network Automation packaged with NNM as Network Observability from 25.4)
- OpenText Marketplace, device driver packs for Network Automation (driver packs "generally released every two months"; no OT, ICS or IoT vendors listed)
- OpenText Marketplace, security and compliance content for Network Automation (PCI DSS and DISA STIG packs, security advisory content)
- OpenText, Network Automation and Network Observability product pages, customer references (Orange Spain, IPC, Nomura, DATAGROUP, NXO France, Turk Telekom; no install base figure published)
- Network World, HP completes its acquisition of Opsware (September 2007)
- DatacenterDynamics, HP separates into HP Inc. and Hewlett Packard Enterprise (November 2015)
- Hewlett Packard Enterprise press release via GlobeNewswire, HPE completes transfer of its software business to Micro Focus (1 September 2017)
- OpenText investor release, OpenText completes acquisition of Micro Focus (31 January 2023)
- fitgap, OpenText Network Automation profile ("Free version unavailable", "Free Trial unavailable")
- rConfig pricing and editions
- rConfig edition comparison
- rConfig homepage FAQ, how fast rConfig backs up large networks (the 50,000 devices in under 21 minutes benchmark)
- rConfig, how rConfig counts devices
- rConfig reference architecture, built past 100,000 nodes
- rConfig Vector Agent product page (outbound-only TLS, no inbound ports, up to 1,000 devices per agent)
- rConfig Vector Prism product page (branded MSP portal, mandatory MFA, tag-based multi-tenancy)
- rConfig Vector product page (hierarchical RBAC, multi-tenant support)
- rConfig multi-vendor network configuration management solution page
- rConfig industrial and OT network management case study (SCADA, PLCs, IEC 62443 compliance pressure)
- rConfig about us (60+ countries, 10,000+ active users, 80M+ devices managed)
- rConfig V8 Pro product page (universal, multi-vendor device support)
- rConfig GenAI bring-your-own-model page (your own API keys or a fully local LLM, no rConfig-hosted model) and rConfig MCP server page
- rConfig integrations page (HashiCorp Vault: rConfig requests credentials at the point of need and does not store them)
- rConfig, High availability and BCP patterns (Enterprise edition)
- rConfig V8 Pro related resources ("NIS2 and DORA compliance evidence out of the box", in the context of consolidating off another NCM product)
- rConfig firmware management solution page (scheduled firmware deploy via SCP, TFTP or API, during approved change windows)
OpenText details are taken from opentext.com, OpenText documentation and community pages, Gartner Peer Insights, G2 and fitgap on 26 September 2026 and may change. OpenText, Network Automation, HP and Micro Focus are trademarks of their owners. rConfig is not affiliated with OpenText, HP, HPE or Micro Focus. rConfig capability claims link to the product pages that make them; edition limits and prices come from the rConfig pricing page. This page is written by rConfig for evaluation purposes and compares the two products on network configuration management only. Your agreement with either vendor governs your actual terms.