Service providers & ISPs
Network configuration management for service providers
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.
$ rconfig collect --estate=global --vendors=all --standard=baseline › loading inventory ............ ok (200,300 devices) › reaching regional collectors ok (9 regions) › checking against baseline ... ok HOSTNAME SITE VENDOR BACKUP STATE agg-sin-9613 sin Ciena ok compliantbng-ord-9626 ord Fortinet ok compliantpe-syd-9639 syd Cisco 8s compliantp-lhr-9652 lhr Juniper ok collectingrr-jnb-9665 jnb Nokia 14s compliantdist-ams-9678 ams Arista live compliantcmts-lax-9691 lax Ciena ok compliantolt-nrt-9704 nrt Fortinet 3s compliantcore-nyc-9717 nyc Cisco ok compliantedge-gru-9730 gru Juniper ok compliant … 200,300 devices, one standard
148,000 collected
0 drift
- DEVICES
- ~200k
- VENDORS
- 12
- REGIONS
- 9
- STANDARD
- 1
Trusted across service-provider and telecom networks
PROOF AT SCALE
Tier 1 ISP runs its global, multi-vendor estate on rConfig, one configuration standard across hundreds of thousands of devices.
- ~200k
- devices under management
- 150,000+
- CPE fleet design point
- 1
- configuration standard
- 24/7
- scheduled collection
Single Tier 1 ISP deployment, including core, access, and edge devices
Built for six-figure estates, not just tested against them
Across every region and vendor, from optical, to access, to radio, to core
Backup cadence that keeps drives confidence
Deployment figures are approximate and published with customer permission.
The challenge
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.
Independence
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.
Fiber
Optical transport and backbone
Access
DSLAMs, OLTs, and CPE
Radio
Mobile and fixed wireless
Core, global
National and international core
Approach
Engineered for scale
Six-figure scale is a design point, not a stretch goal. One platform holds an entire carrier estate without the management plane becoming the bottleneck. Start with the architecture and the AI maturity model, see how it runs for a telecom provider, then use the map below to reach each capability.
- ReferencerConfig reference architectureThe stack engineered to run 100k+ device fleets.
- AINetwork AI maturity modelThe TM Forum L0 to L5 ladder, and where rConfig stands.
- TelcoNetwork automation for telecomHow carrier and telecom providers run rConfig.
- OpticalConfiguration Management for Optical NetworksHold the optical and transport layer, TL1 and all, to one standard.
- ProtocolTL1 Configuration ManagementNative TL1 for SONET, SDH, DWDM and OTN transport gear.
- VectorrConfig VectorThe read-only AI layer over your configuration data.
Twenty-five years experience inside carrier networks design and operations shaped how we built rConfig. It reflects how service-provider operations really work: multi-vendor, multi-region, accountable for every change. Independent by design, and built to manage the network you already run.
Stephen StackFounder & CTO, rConfigTHE STACK
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.
- Proven at scaleTier 1 ISP configuration managementBackup, audit, and change control across a ~200k-device Tier 1 ISP estate.
- Audit readyConfiguration Compliance for Service ProvidersContinuous policy checks, drift detection, RBAC, and carrier audit trails.
- Six-figure scaleManaging 100,000 Network DevicesHow collection, change, and the data model hold up at six-figure scale.
- Always recoverableNetwork Backup for Large-Scale NetworksParallel, versioned configuration backup that keeps closing its windows.
- Vendor-neutralMulti-Vendor Configuration ManagementOne neutral plane across every vendor in the estate.
Let's talk in carrier language
Six-figure device counts, a multi-vendor estate from optical to core, change windows measured in minutes, and audits that have to hold. If that is your network, it is the one rConfig was built for.
PROOF & REFERENCES
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.
- 01ReferencerConfig reference architectureThe stack engineered to run 100k+ device fleets.
- 02AINetwork AI Maturity ModelThe TM Forum L0 to L5 ladder, and the rung rConfig stands on today.
- 03SolutionCompliance and Security AuditingAutomated policy checks against CIS and custom internal standards.
- 04SolutionNIS2 ComplianceMeeting the EU's network and information security directive.
- 05AIAI for Service Provider NetworksThe AI hub, where Service Provider AI maturity aligns to the TM Forum framework.
TIER 1 EVALUATION
Evaluating rConfig for a Tier 1 rollout?
We will take your architects through the data model, the collection engine, and the change pipeline against your real device counts and vendor mix, under NDA.
TALK TO US
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.
Tell us your device count, vendor mix, and project timeline, and we will map a rollout to your estate.