Your monitoring, your IPAM, your IdP. rConfig plugs into all of them.
Device inventory from Zabbix, NetBox or Nautobot. Credentials from HashiCorp Vault. Sign in through the identity platform your team already uses. No duplicate data entry, no glue scripts holding the whole thing together.
rConfig
rConfig
rConfig
rConfig
rConfig
rConfigThree jobs handled by your existing tools. rConfig just uses them.
- 01Inventory sync
Your source of truth stays your source of truth
rConfig reads from Zabbix, NetBox, Nautobot or Statseeker and keeps its device list in lockstep. Add a device upstream, it appears in rConfig on the next sync. Retire one and the staging table flags it for review before anything breaks.
- 02Secrets
Credentials live in Vault, not our database
rConfig asks HashiCorp Vault for credentials when it needs them, uses them for the job at hand, and forgets them. Nothing sensitive stored on our side. Works with AppRole, Kubernetes auth and token auth.
- 03Identity
Sign in the way your team already signs in
SAML and OIDC through Azure AD, Okta, Google Workspace, Keycloak and Authentik. MFA, group based RBAC and provisioning at login come with the territory.
Ship today. Not roadmap.
Every connector below is in production, included in V8 Pro, Enterprise and Vector. No per connector licences, no extra modules.
Read the device list from the system that already owns it. rConfig keeps its managed estate in lockstep, no CSV exports.
- Official partnerLearn moreMonitoring
If Zabbix already knows every host on your network, rConfig doesn't ask twice. Hosts flow in on the schedule you set, new ones pick themselves up, and the integration is featured in Zabbix's own directory at zabbix.com/integrations/rconfig.
- Learn moreDCIM · IPAM
Treat NetBox as authoritative and let rConfig consume it. Scope the sync by site, tenant, role, platform or tag. Whatever NetBox says the network is, rConfig backs up.
- Learn moreDCIM · IPAM
Tag driven sync that respects Nautobot's API model. Runs alongside Golden Config if you want both, or stands in as a complete alternative if your team isn't ready to own Jinja, Nornir and GraphQL.
- New in V8.2.0Learn moreMonitoring
Statseeker watches the network. rConfig captures what's on it. Statseeker hosts now sync straight into rConfig as managed devices, no CSV exports required.
- Q2 2026More connectorsPlanned
LibreNMS, Observium, similar NMS systems are on the short list. Ask if yours should be next.
- Tell usYour monitoring tool?Customer request
Most customer requested sync connectors ship through rConfig Automate without waiting for the next major release.
Pulled at the moment of use, never written to rConfig's database. AppRole, Kubernetes and token auth supported.
- Read the docsSecrets
Pull device credentials at the moment of use. rConfig never writes secrets to its own database. Supports AppRole, Kubernetes and token authentication.
- On the benchCyberArkEnterprise PAM
Privileged access management with credential vaulting. Short lived device credentials pulled at the moment of use.
- On the benchDelinea (Thycotic)Secret Server
Secret Server integration for privileged credential storage alongside the existing Vault path.
Standard SAML and OIDC. MFA, group based RBAC and provisioning at login come with the territory.
- Read the docsSAML & OIDC SSOIdentity
The umbrella: standards based sign in that plugs into whatever IdP your team already runs. MFA, group based RBAC and provisioning at login come with it.
- Read the docs
Azure AD / Entra IDMicrosoftTenant wide sign in with group based RBAC and provisioning at login via OIDC or SAML.
- Read the docsOktaIdentity cloud
OIDC or SAML sign in with Okta group mapping to rConfig roles. SCIM provisioning on the short list.
- Read the docsGoogle WorkspaceOIDC
Google as the IdP with domain verification and organisational unit mapping to role groups.
- Read the docsSAML 2.0Protocol
Any standards compliant IdP: ADFS, Authentik, Duo, OneLogin, JumpCloud, PingFederate.
- Please requestMore IdPs comingCustomer request
Running something that isn't listed? Tell us — most customer requested IdPs are a configuration away, not a release away.
Backup, compliance and change events land in chat or fan out as webhooks to the downstream systems you run.
- Read the docs
.svg.png&w=96&q=75)
Microsoft TeamsChatOpsChatOps notifications for backup failures, compliance drift and unauthorised changes, with click through to the offending device.
- Read the docs
SlackChatOpsBackup, compliance and change alerts in the channel your team already lives in. Threaded per device so noise stays manageable.
- Read the docs
WebhooksAutomationFire JSON payloads into any downstream system when rConfig detects a change. Fan out to SIEM, CMDB, or your own automation.
One network, three teams, one source of truth each.
Monitoring, DCIM, and configuration each earn their keep by owning one question. rConfig is the system that answers “what changed, and who changed it” — without asking the other tools to move over.
Here’s the honest version. Monitoring tells you the network is up. DCIM tells you what the network is supposed to look like. Neither one answers the 2am question: who changed the core switch ACL, and can we put it back. That’s the gap rConfig fills, and we fill it without asking you to rip out the tools you already trust.
Running rConfig alongside Zabbix, NetBox or Nautobot means inventory stays in one place (theirs) and configuration intelligence lives where it belongs (ours). The NOC, the security team and the auditor end up looking at the same network from the angle each of them needs. Every integration on this page is included in V8 Pro, Enterprise and Vector. No per connector licences, no extra modules, no consulting engagement required to turn them on.
Government networks, global telcos, and the lab down the hall.
rConfig ships into regulated estates, ISP backbones, and solo engineer setups alike. The only thing that changes is the shape of the integration list.
Used in 120+ countries, from regional networks of a few hundred devices to global estates well north of 100,000.
On the bench, not the backlog.
Actively in development. Targets for the next two releases. If the connector your team needs isn’t on the list, ask.
AI assisted operations
Natural language interrogation of config history, drift explanations and remediation suggestions, surfaced through rConfig Automate.
ServiceNow
CMDB sync plus automated change tickets when rConfig detects an unauthorised configuration change.
Customer requested connectors
If the tool your team needs isn't on this page, talk to us. Most customer requested sync integrations ship through rConfig Automate without waiting for the next major release.
Run rConfig alongside what you’ve already got
Book a 30 minute session with an rConfig engineer. We'll run inventory sync against a slice of your real network, back up a sample of devices, and show you what compliance reporting looks like against policies that actually matter to your team. Tell us your rough go-live date and we'll tailor the walk-through.