An AI orchestration layer that runs live network operations across every customer, every vendor, from natural language — with per-customer isolation and MCP-driven control over the real device APIs.
Managed service providers carry the operational load of many independent networks. The work is repetitive, the context-switching is constant, and the tooling rarely spans vendors cleanly.
Every customer has its own topology, credentials, and change windows. Engineers rebuild mental context on each ticket, and that time doesn't scale with headcount.
FortiGate, Cisco, Juniper and Huawei each speak a different CLI and API dialect. Cross-vendor work means cross-vendor expertise, per engineer, per shift.
Reading state, correlating logs, drafting changes, validating them — the same motions repeated across every tenant, mostly typed by hand under time pressure.
Requests arrive in plain language. The orchestration layer resolves the tenant, builds a plan, and executes it against the real device APIs through MCP — then verifies the result before reporting back.
"Show blocked sessions on Customer B's edge firewall" or "add this address object to the guest policy" — no CLI syntax, no per-vendor recall.
The agent calls the actual FortiOS / vendor REST interfaces via MCP tools — reading state and making scoped changes, not producing config it can't apply.
Plan, act, then confirm the resulting state matches intent. The loop closes on verification rather than on a generated answer.
Capabilities span the day-to-day of network operations, delivered through MCP tool interfaces the agent can compose.
Read and modify firewall policy, address objects, interfaces and routing through scoped, auditable operations.
Pull live state, correlate logs and sessions, and walk a structured diagnosis instead of a blank CLI prompt.
Surface metrics and alerts where the team already works, and drive investigations from chat.
Tie operational actions to the systems of record so work is tracked, not lost in a chat window.
Live vendor support today, with an MCP integration surface that already reaches the surrounding operational tooling.
Each integration is exposed as an MCP tool interface, so the agent composes across observability, ChatOps, ticketing and source control in a single workflow.
The platform treats the language model as a swappable component. Route by capability, cost, or availability without rewriting the operational logic underneath.
Available as a reasoning backend in the same orchestration path.
Interchangeable at the model layer, selected per workload.
First-class support alongside the others, no privileged path.
Every tenant is a boundary. Credentials, context and scope stay bound to the customer they belong to, so an action for one network can't reach another.
Started as a single-vendor FortiGate automation concept and grew into a multi-LLM, multi-vendor, multi-tenant operations platform for managed service providers.
Reach out to Team Ctrl+AI for a walkthrough of the platform and the architecture behind it.