rConfig Iris
The most fully featured AI in network configuration management. Ten capabilities in one governed place: AI that reads your network and explains it, and rConfig made available to the AI tools your engineers already use. Read-only to your network, on the model you choose.
Ask your network a question. Get a clear answer.
Iris is the AI built into rConfig. It reads your network configs and explains them in plain words. It also lets the AI tools your team already uses read the same facts, safely. It never changes a device.
Ask about a config, a change, a failed check or a setting. The answer shows up on the screen you are already on.
Claude Code, Codex, Cursor and other AI agents can read your network facts. They can look. They cannot touch.
Your agents learn how rConfig works, so the scripts and reports they build are right first time.
Use the AI model you already trust. Run it in the cloud, or keep it fully inside your own network.
AI helps. Your engineers decide.
Iris explains and suggests. It does not change a device. Write access stays closed until you choose to open it.
Questions go straight from your server to the AI provider you picked. rConfig, the company, never sees your data.
Your existing roles decide who can use AI. Every question is logged, so there is always a record.
Each stage has to be useful by itself and earn the next one. A wrong answer said with confidence breaks trust, so we start careful.
Ask your network anything, in plain English
Type a question the way you would ask a colleague. Iris reads the configs and answers, and shows you the lines that prove it.
- Where: the config viewer, on the device in front of you.
- Across the estate: one question can cover every device.
- Shows its work: each answer points at the exact config lines.
- Great for new engineers: routing, ACLs and QoS explained line by line.
See what changed, and whether it matters
A diff shows red and green lines. Iris tells you what they mean. Small changes get a short note. Risky ones get flagged.
- Where: the config changes panel.
- Plain words: what changed between two versions.
- Sorts the noise: routine change or real risk.
- Knows the standards: CIS, NIST and ISO 27001 where they apply.
Know why a check failed. Write the next rule faster.
Iris explains each pass and fail in plain words. It can also draft a new CIS or NIST style rule for a person to check.
- Where: compliance results and the policy editor.
- Explains results: why a device passed or failed.
- Drafts rules: you review, then keep or bin.
- The one thing it saves: an approved rule, to rConfig's own policy store. Never to a device.
| Rule | Result |
|---|---|
| SSH timeout set | Pass |
| No Telnet inbound | Fail |
| AAA enabled | Pass |
Get rConfig itself running at its best
Ask how to tune your rConfig server. Iris answers from the official rConfig docs, not from guesswork.
- Where: the system optimisation settings.
- Grounded: answers come from docs.rconfig.com.
- Self-serve: no ticket, no waiting.
- Advice only: you make the change.
Let your AI agents read your network, safely
Claude Code, Codex, Cursor and Gemini CLI can ask rConfig for live facts, then carry on the job in your other tools.
- Seven read-only tools: inventory, configs, history, diffs, search and compliance.
- Look, do not touch: the server has no write tools.
- Same rules as people: the agent sees only what its token's user may see.
- Secure by default: streamable HTTP and SSE, with a bearer token shown once.
Teach any agent how rConfig works
Download the rConfig Skill and load it into your agent. From then on it knows rConfig's terms and rules, so it gets the job right first time.
- One package: download it from Iris, load it once.
- Built-in know-how: devices, tasks, policies, naming.
- Pairs with MCP: the Skill explains, MCP supplies live data.
- Made for: integrators, MSPs and automation engineers.
API docs your AI agents can read
Export the rConfig REST API as clean Markdown. Your agent reads it and writes calls that work, instead of guessing.
- Written for agents: Markdown that an AI model can take in.
- The whole REST API: everything needed to script rConfig.
- Matches your version: exported from your own instance.
- Right first time: real endpoints, not made-up ones.
Use the AI model you already trust
rConfig does not host AI models. You connect your own, from 13 providers. Pick a cloud service, or run a local model that never leaves your building.
- 11 cloud providers: use your own keys and contracts.
- 2 self-hosted options: Ollama, or any OpenAI-compatible server.
- Air-gapped ready: a local model makes zero outbound calls.
- No extra fees: rConfig does not charge per prompt.
You decide who uses AI. Every question is on record.
Iris works inside the access rules you already have. An admin picks the model. Each time someone uses AI, rConfig writes down who, what and when.
- Two permissions: one to use AI, one to manage it.
- One provider at a time: added, tested and switched on by an admin.
- A full record: user, capability, provider, model, tokens, IP and time.
- Off means off: no provider set, no AI anywhere in the product.
aicenter.viewaicenter.updateread-onlyaudit log| User | What they used | Model | Tokens | When |
|---|---|---|---|---|
| a.okafor | Config Analysis · edge-rtr-11 | Anthropic | 4,212 | 09:12 |
| s.nolan | Drift Narration · core-rtr-02 | Ollama (local) | 1,870 | 09:09 |
| a.okafor | Compliance · CIS L1, fleet | Anthropic | 6,034 | 08:55 |
| svc-claude | MCP · search_configs | token-scoped | n/a | 08:41 |
Know exactly what leaves your network
Each capability sends only what it needs. The list is published inside Iris, so your security team can check it line by line.
- Published per capability: on the Iris Privacy page.
- Smallest share: a diff, not the whole config, where a diff will do.
- Local model: nothing leaves at all.
- Built into the code, not just written in a policy.
| What is sent | Your question | Config text | The diff | Names and results |
|---|---|---|---|---|
| Config Analysis | ||||
| Drift Narration | ||||
| Compliance Narration | ||||
| Rule drafting | ||||
| Optimization |
A four-step path for AI on your network
Some vendors sell the top of the ladder. We show every rung, and we tell you which one we are on. Mapped to the TM Forum L0 to L5 scale, for enterprise and MSP networks.
Assisted Insight
The AI reads, explains and narrates your estate in plain language. Read-only by design.
TMF L1-L2Augmented Operations
You extend the AI's knowledge with your own conventions, golden configs and standards. Still read-only.
TMF L2Supervised Automation
The AI proposes changes. Nothing is applied without a human in the loop.
TMF L3Autonomous Operations
Governed jobs run end to end, inside bounds you set. The horizon.
TMF L4-L5The most fully featured AI in NCM. In your network, on your model, answering to your team.
Draft. Based on the rConfig V8 AI Center as documented on rconfig.com and docs.rconfig.com. See it on your own configurations: rconfig.com/ai.