Distributed Network Operations for MSPs and Large Operators

rConfig Vector is a distributed, multi-tenant Network Configuration Management (NCM) platform designed for Managed Service Providers (MSPs), telcos, and large enterprises that operate many networks across different customers, regions, or business units. It combines the full NCM feature set of rConfig V8 Pro with a three-tier architecture that separates the central control plane from the collectors that run close to devices. Vector is ideal if you manage dozens of customers, multiple network zones, or geographically distributed environments and need standardised configuration backups, compliance, and change control without losing per-tenant isolation or control. Explore Vector use cases

rConfig V8 Pro is a powerful, single-instance NCM platform suited to organisations that want one deployment for up to 1,000 devices. It provides automated backups, search, diff, rollback, compliance checks, RBAC, and integrations. All from a single control plane. rConfig Vector takes that same core feature set and extends it for MSP and operator use cases. It introduces a central manager with support for multiple tenants, distributed Vector collectors, tenant-by-tenant isolation, hierarchical RBAC, and global policies that can be reused across customers and regions. Vector is the right choice when you need to run NCM as a shared service across many environments. See what’s included from V8 Pro

Yes. Many Vector deployments start as a consolidation project: replacing a mixture of Oxidized, RANCID, Kiwi CatTools, Ansible and Python scripts, or legacy NCM add-ons from other platforms. Instead of maintaining separate pipelines and cron jobs per customer or network, Vector gives you a centralised inventory, policy engine and audit trail across all environments, while still allowing you to run jobs close to devices via the rConfig Vector Agent at every site. You can migrate in stages, moving customers or regions to Vector one at a time while preserving your existing automation, then gradually standardising on Vector’s APIs, compliance engine and workflows for new services.

rConfig Vector is self-hosted and designed to support operators working under NIS2 compliance, DORA compliance, ISO 27001, CIS, and similar regulatory frameworks. It helps you demonstrate control over configuration, backups, change workflows, and access, which are all expected elements of modern operational resilience and cyber-security regimes. Because Vector’s central manager and collectors run in your own environment, you can align deployment with data residency, sovereignty, and segmentation requirements. Per-tenant audit trails and compliance reports make it easier to answer questions from regulators, customers, and internal risk functions. Learn more about compliance and regulation

Vector lets you define tenants that represent customers, regions, or internal business units. Each tenant has its own devices, jobs, policies and audit history. Vector’s hierarchical RBAC model allows your NOC and engineering teams to see and manage multiple tenants, while granting scoped access to customer administrators or limited support teams. This model is particularly valuable for MSPs who want to give customers visibility into their own configuration backups, change history, and compliance status without exposing other customers or internal-only data. View multi-tenant Vector capabilities

rConfig Vector is deployed as a self-hosted solution. You can run the central manager in your own data centre or private cloud, and place collectors wherever they make the most sense: customer sites, regional data centres, POPs, or specific network zones behind firewalls. Our team can help you design highly available deployments, regional failover patterns, and migration plans from existing NCM platforms. We also offer professional services for complex MSP and multi-region architectures, and you can see Vector pricing alongside the other rConfig editions. Explore Vector architecture options

Vector is licensed per managed device with a base subscription that includes the central manager and an unlimited number of collectors. Pricing tiers are designed around MSP scale, so onboarding additional customers does not require additional infrastructure licences, only device capacity. You can see Vector pricing alongside V8 Pro and V8 Core, or contact our team for a quotation shaped to your customer count, device count, and required regions. Request a Vector quotation

For a new Vector deployment, a first customer typically goes from installation to first successful tenant-isolated backups within one to two weeks. The first week covers central manager install, credential vault setup, and tenant model design. The second week covers collector deployment at the customer site, device import, and policy and report configuration. Subsequent customers onboard much faster: deploy a tenant-scoped collector, import devices, attach the global policies you have already defined, and grant scoped portal access. Most MSPs settle into a one to three day onboarding pattern per new customer once their tenant template is stable.

Vector exposes a documented REST API that lets you connect NCM events and inventory to ITSM platforms such as ServiceNow and Jira, and to PSA platforms commonly used by MSPs, including HaloPSA, Autotask, and ConnectWise. Typical integrations create change tickets from configuration drift, attach diff output to change records, and post compliance breaches into customer-specific queues. For platforms without a packaged connector, Vector’s webhooks and API tokens are designed to plug into iPaaS tools like n8n, Make, or Workato so you can build connectors without changing the core product.

Yes. Vector’s API-first design exposes inventory, configuration history, diffs, and compliance state as structured data that AI copilots and automation pipelines can consume. Common patterns include retrieval-augmented assistants that answer engineer questions from current configurations, agents that propose remediations from drift events, and pipelines that gate change automation behind policy checks. Because Vector runs in your environment, the configuration data and credentials never leave your perimeter. You decide which subsets of data your AI tooling can read, and on what cadence.

Vector is fully self-hosted, so you choose where the central manager runs and where collectors live. Common patterns include a single central manager in your primary region with collectors in EU and US tenants, or fully separate Vector deployments per jurisdiction when regulation requires that no metadata leaves the region. For EU operators with NIS2 obligations and US operators with sector-specific frameworks, this lets you align deployment topology with the rules you actually need to satisfy, rather than working around a SaaS vendor’s region map.

The Vector central manager supports active or warm-standby HA pairs with shared storage for inventory, audit history, and policies. Collectors are stateless and horizontally scalable, so you can run multiple collectors per tenant or per region behind health checks. Job state is persisted centrally, so a failed collector hands work off to a peer rather than losing scheduled backups. For multi-region deployments, customers commonly run an HA central manager in one region with read-replica or warm-standby in another, plus collector pools per region. Our team can review your topology and recommend a pattern that matches your RTO and RPO targets.