Introducing Uplink: rConfig's guides and reference libraries
Introducing Uplink: rConfig’s guides and reference libraries
Section titled “Introducing Uplink: rConfig’s guides and reference libraries”These docs show you how to do each task in rConfig. Uplink shows you how it works and why.
Uplink is our guide site. You can find it at /guides/. It helps you pick the right plan for your network. It shows the good and bad sides of each choice. It also gives you real examples that we have tested.
What you’ll find in Uplink
Section titled “What you’ll find in Uplink”- Product guides for Vector and Iris: reference architectures, connectivity and access designs, and how each fits into the rest of your tooling.
- Reference libraries you can copy and adapt: tested policy definitions, connection templates, collection methods and optical (TL1) procedures.
- Architecture and operations guides: high availability, security, integrations, scale, and change and automation, each with the trade-offs explained.
- Playbooks: worked, real-world examples, such as an AI agent that explains which config change fits an alert, or a nightly drift check against approved configs.
Uplink is written for engineers, just like these docs. It does not pick sides between vendors. It does not repeat the install or setup steps either. Those stay here in the docs. Each guide links back to the docs pages it talks about. Each docs page links to its guide with a card, like the ones below.
Start with a library
Section titled “Start with a library”
Uplink: productsIris AI Center guidesHow Iris, the AI Center in rConfig, works with AI agents (Claude, Cursor, GitHub Copilot, Codex) and your wider network tooling (NetBox, Grafana, Zabbix) over MCP.Browse the Iris guides
Uplink: productsVector guidesArchitecture, connectivity and Vector Access guides for MSPs running rConfig Vector: the three reference designs, how agents connect, and where to go next.Browse the Vector guides
Uplink: reference libraryPolicy LibraryWorked rConfig policy definition examples with passing and failing configs, each backed by an automated test in the rConfig Pro test suite.Browse the Policy Library
Uplink: architectureHigh Availability guidesHow rConfig high availability fits together: active/standby and active/active nodes, database replication, shared storage, Redis, queues and failover.Browse the HA guides
How Uplink and the docs fit together
Section titled “How Uplink and the docs fit together”| rConfig docs | Uplink | |
|---|---|---|
| Answers | How do I do it? | How does it work, and which design should I choose? |
| Covers | Install, upgrade, configure, operate, troubleshoot, reference | Architecture, design choices, pros and cons, patterns, tested examples |
| Where | docs.rconfig.com |
docs.rconfig.com/guides/ |
| Search | Finds both | Can be limited to guides |
Both are on the same site and share one search, so a search from the docs also finds the guides.
Go to Uplink
Section titled “Go to Uplink”Open Uplink guides and references to see every library, filter by product or topic, and search the guides on their own. Have a guide or a tested example to share? See Contributing to Guides & References.