🔗 MSP and Telco · Distributed · Multi-Tenant

Distributed Network Configuration Management for MSPs and Large Operators

rConfig Vector gives MSPs, telcos, and large enterprises a modern, distributed NCM platform for managing thousands of devices across many customers and regions. Centralise control, keep customers isolated, and run configuration backups, compliance, and automation at scale.

rConfig Vector logo representing distributed, scalable, multi-tenant network configuration management for MSPs and global operators
data flow · 1 manager · N collectorsoutbound tls

What is multi-tenant NCM?

Multi-tenant network configuration management is an NCM platform where one deployment serves many isolated networks at once. Each tenant has its own devices, jobs, audit trail, and access scope. rConfig Vector is built this way for MSPs, telcos, and large enterprises that manage configurations for many customers or regions from one place.

00 · Why Vector

Why MSPs and large operators choose rConfig Vector

Vector is designed for teams managing many networks, not just one. It gives you clean tenant separation, distributed collectors close to devices, and a single place to enforce standards, compliance, and automation for every customer.

  • Multi-tenant by design

    Segment customers, regions, or business units with clear boundaries and RBAC. Each tenant gets isolated inventories, jobs, and audit history, and your NOC keeps one console for the whole estate.

  • Distributed, close to the edge

    Deploy lightweight Vector collectors into customer sites, POPs, and regions. Run backups, checks, and scripts next to the devices, not across the WAN, to keep things fast, resilient, and predictable.

  • Centralised governance, simple ops

    Use one central manager to search, report, and prove compliance across every customer. Standardise policies once, reuse them everywhere, and keep your NCM story consistent for audits and QBRs.

01 · Architecture

A modern NCM control plane with collectors everywhere you need them

rConfig Vector separates the control plane from execution. The central manager sets the rules; collectors handle work where the devices live, giving you low-latency NCM and clear governance at MSP scale.

  • Tier 1: Central Manager

    One central UI and API to manage tenants, policies, jobs, and compliance. Inventory, history, and audit trails live here, giving your NOC and engineering team a trusted source of truth.

  • Tier 2: Vector collectors

    Stateless, horizontally scalable engines you deploy per customer, per region, or per network zone. They handle backups, config retrieval, command execution, and policy checks close to the devices.

  • Tier 3: Devices and services

    Routers, switches, firewalls, CPEs, GPON/FTTH kit, DC networks, wireless, IoT, and OT. Vector gives you one consistent way to back up, validate, and report on configuration state for all of them.

Built to keep MSPs and customers safe

Vector is self-hosted and designed for regulated environments. You control where collectors run, which networks they can see, and how credentials are managed. Each site runs the rConfig Vector Agent, the distributed Go collector. Tight RBAC, tenant isolation, and full audit data make it easier to answer hard questions from security, regulators, and customers.

✓Deployment flexibility

  • →Deploy central manager on-prem or in private cloud
  • →Run collectors in DCs, branches, POPs, or customer sites
  • →Support for HA patterns and regional failover designs
  • →No SaaS dependency. Data stays inside your own perimeter.
Suite

Components of the Vector Suite

Vector ships as three pieces that work together: a central control plane, a Go collector at every site, and a white-label portal for the customers you serve.

Alternatives

Why operators replace SolarWinds, ManageEngine, and script-based NCM with Vector

Vector is not another monolithic NCM bolt-on. It is a distributed, self-hosted control plane designed for MSPs and operators who need multi-tenant control, predictable performance, and a clean security story.

Comparison of rConfig Vector against SolarWinds NCM and ManageEngine, vendor stacks like Cisco Prime, and homegrown Oxidized / RANCID / script approaches across the capabilities MSPs and large operators evaluate.
CapabilityrConfig VectorSolarWinds NCM / ManageEngineCisco Prime / vendor stacksOxidized / RANCID / scripts
Multi-tenant by designyessupportednonot supportednonot supportednonot supported
Distributed collectors close to devicesyessupportedpartialpartially supportednonot supportedpartialpartially supported
Hierarchical RBAC for MSPsyessupportednonot supportedpartialpartially supportednonot supported
Self-hosted, no SaaS dependencyyessupportedyessupportedyessupportedyessupported
Modern, API-first architectureyessupportednonot supportednonot supportedpartialpartially supported
Built-in compliance & drift controlyessupportedpartialpartially supportedpartialpartially supportednonot supported
Search, diff & history across tenantsyessupportedpartialpartially supportedpartialpartially supportednonot supported
Aligned to NIS2 / DORA / ISO 27001yessupportedpartialpartially supportedpartialpartially supportednonot supported
Active roadmap & commercial supportyessupportedpartialpartially supportedpartialpartially supportednonot supported

If you run a single small network, a vendor-bundled NCM module is probably enough. If you operate many networks across customers, regions, or business units, a distributed multi-tenant control plane is the only approach that scales without bolting on more firewall rules and more spreadsheets.

02 · Inherited from V8 Pro

Everything from rConfig V8 Pro, baked into Vector

Vector inherits the full rConfig V8 Pro feature set. Automated multi-vendor backups, fast search, diff and rollback, real-time change detection, and compliance checks, now scaled out across collectors and customers.

Explore V8 Pro features
  • Automated multi-vendor backups

    Scheduled, policy-driven configuration backups across routers, switches, firewalls, wireless, DC, and edge devices, now orchestrated across many collectors.

  • Search, diff & history

    Global search, per-device history, and line-by-line diffs across tenants. Quickly answer what changed, where, and when, even in busy MSP environments.

  • Safe rollbacks & change windows

    Use structured change workflows and rollback plans to support maintenance windows across many customers without relying on one-off scripts.

  • Compliance & drift control

    Apply baseline standards and compliance policies consistently, then reuse them per tenant. Detect drift before it becomes an incident or audit finding.

03 · New in Vector

Built specifically for MSPs, telcos, and multi-region enterprises

Vector takes everything from rConfig V8 Pro and extends it with multi-tenant controls, distributed collectors, and MSP-grade governance features. It is the NCM platform you can standardise on across all customers.

  • Multi-tenant segmentation

    Isolate customers, regions, or business units with dedicated inventories, jobs, and audit trails. All governed from one central manager.

  • Per-customer & regional collectors

    Deploy Vector collectors per customer site, POP, or region to run jobs close to devices, reduce latency, and keep changes inside the right network zone.

  • Hierarchical RBAC for MSPs

    Give your NOC global visibility while granting customers scoped access to their own devices, reports, and compliance status.

  • Collector health & job observability

    Monitor collector health, job queues, and per-tenant performance so you can see where work is running and where to add capacity.

  • Global policies, local enforcement

    Define standard policies, templates, and compliance rules once, then apply them selectively across tenants and regions.

  • Enterprise & MSP ready compliance

    Support NIS2, DORA, ISO 27001 and customer-specific frameworks with centralised reporting, drift detection, and per-tenant evidence.

  • Hybrid & multi-region deployment

    Run your central manager in a core DC or private cloud while placing collectors in customer sites, country zones, or regulatory jurisdictions.

  • Standardised runbooks & workflows

    Turn proven change and rollback procedures into reusable NCM workflows that your engineers and customers can trust.

  • Ready for AI & automation pipelines

    Vector’s API-first design makes it easy to plug into your existing tooling, from ITSM and observability to AI copilots and automation engines.

04 · Use cases

How rConfig Vector is used in production today

Vector is built for operators that live in the real world: SLAs, audits, outages, and growth. These are the patterns we see most often across our MSP, telco, and enterprise customers.

MSPs consolidating NCM

MSPs consolidating NCM across dozens of customers

Managed Service Providers often inherit a mess of tools: RANCID here, Oxidized there, Python scripts on someone's laptop, and a few legacy commercial platforms. Vector replaces that patchwork with a single, distributed NCM control plane.

âś“

Onboard new customers by deploying a dedicated collector and assigning a tenant

âś“

Apply baseline standards, policies, and compliance rules consistently across all customers

âś“

Give selected customers read-only or admin access to just their devices and reports

âś“

Use global search and reporting to prepare for QBRs and security reviews

In production · anonymised
  • European Tier-2 MSP

    14 customers, 4,200 devices

    Replaced a mix of Oxidized and per-customer scripts with one Vector deployment and tenant-scoped collectors, cutting customer onboarding from days to hours.

  • Regional ISP and FTTH operator

    3 POPs, 11,000 access devices

    Moved CPE and access-layer backups onto regional collectors, giving NetOps a single inventory and removing nightly WAN traffic spikes from the old centralised pull model.

  • Multi-region enterprise, regulated sector

    6 regions, 1,800 devices

    Standardised NCM across business units with per-region collectors and global compliance policies, producing the evidence pack their NIS2 audit needed in one export.

Maintained by the rConfig engineering team. Last updated: .

rConfig Vector – Frequently Asked Questions

Standardise NCM across every customer, site, and region

rConfig Vector is the distributed control plane for MSPs, telcos, and multi-region enterprises. Deploy collectors close to your devices, keep tenants cleanly isolated, and run one consistent NCM story across the whole estate.

We use cookies

We use cookies to ensure you get the best experience on our website. For more information on how we use cookies, please see our cookie policy.

By clicking "Accept", you agree to our use of cookies.

Learn more