Service Provider Network Management
Hold an entire service-provider estate, multi-vendor, multi-region, hundreds of thousands of devices, to one configuration standard you can back up, audit, and change with confidence.
INVENTORY · ESTATE Device & Vendor Inventoryfiber · access · radio · coreCOLLECTION Continuous Collectionevery device, every windowCOMPLIANCE · CMOPTIONAL Policy & Drift Engineoptional · activate when needed
EMEA-WHA Regional clusterdevices · sites · local collectionAMER-EHA Regional clusterdevices · sites · local collectionAPAC-NHA Regional clusterdevices · sites · local collectionRIM-OTHA Regional clusterdevices · sites · local collection
Tier 1 ISP runs its global, multi-vendor estate on rConfig, one configuration standard across hundreds of thousands of devices.
- ~200kdevices under management
Single Tier 1 ISP deployment, including core, access, and edge devices
- 150,000+CPE fleet design point
Built for six-figure estates, not just tested against them
- 1configuration standard
Across every region and vendor, from optical, to access, to radio, to core
- 24/7scheduled collection
Backup cadence that keeps drives confidence
Deployment figures are approximate and published with customer permission.
The service provider stack
Optical, access, radio, and core, every layer of the estate held to one configuration standard. Start anywhere in the stack and follow it to the capability that maps to your rollout.
Tier 1 ISP configuration management
Backup, audit, and change control across a ~200k-device Tier 1 ISP estate.
Configuration Compliance for Service Providers
Continuous policy checks, drift detection, RBAC, and carrier audit trails.
Managing 100,000 Network Devices
How collection, change, and the data model hold up at six-figure scale.
Network Backup for Large-Scale Networks
Parallel, versioned configuration backup that keeps closing its windows.
Multi-Vendor Configuration Management
One neutral plane across every vendor in the estate.
One estate, every vendor
A service-provider network is not one network. It is a national estate built over a decade, and the job is to make all of it behave as one.
Multi-vendor by default
A national core, edge, optical, and access estate, and almost none of it single-vendor.
Six-figure scale
Hundreds of thousands of devices, built up across every region over a decade.
Held to one standard
Every config backed up on a tight cadence and measured against a single baseline.
Change without an outage
Roll validated change across the estate without taking a region offline.
Manage the network you have, not the one a vendor wants you to buy
Neutrality only counts if it is structural. rConfig sells no network hardware, so it has no hardware line to protect and no reason to favour one vendor over another. Drivers are template-driven and customer-extensible, so adding a platform is a configuration change, not a wait for a roadmap.
That holds across every layer of the estate, fiber, access, radio, and core, on one neutral plane. See multi-vendor configuration management for how it works in practice.
Solutions and deeper reading
Every claim on this page traces back to a page of its own, from the reference architecture to the compliance regimes a carrier audit will name. Follow any thread to its proof.
Bring your estate up to one standard
See rConfig run against a service-provider-scale, multi-vendor estate. Book a working demo, or talk to our team about your network.