One platform, two teams
The control panel connects your view of your services with the engineering systems that deliver, observe and protect the network. Same records, different lenses.
Most carriers give customers a ticket form and a monthly PDF. We built the control panel because our own engineers needed one view of sites, hardware, circuits, addressing, services and routing state, and it turned out customers wanted the same underlying truth about their part of it.
Your portal and our engineering tooling read from the same records. When you look at a service, you are looking at the object our provisioning system built and our monitoring watches, not a summary copied into a customer database once a month. That is what removes the gap between what was ordered, what was deployed and what is happening now.
It runs on live data: SNMP counters and optics, sFlow for traffic composition, BGP and BMP for routing state, and our own inventory for topology and capacity. Where evidence is missing or stale, the interface says so rather than showing you a healthy-looking blank.
Port utilisation, as it appears in the panel
What is in it
The panel is organised the way an operations team thinks: the network, the services running on it, and what is being watched.
Service portfolio
Every active service with its identifier, location, bandwidth model and current operational state. The same record our provisioning team built it from.
Traffic analytics
Current and historical bandwidth, direction and utilisation, with service-specific sFlow analysis showing composition, ASNs and prefixes.
Orders
Browse the service catalogue, submit a structured request, and follow it from draft through review, build and delivery without chasing anyone.
Support
Open and track tickets with the affected service and account context already attached, so the first reply is not a request for more information.
Maintenance
Planned work with the services it affects, the window, progress while it runs, and the history afterwards.
Billing
Invoices and the recurring commercial picture of your service portfolio, in the same place as the services themselves.
Account management
Company details, technical and billing contacts, portal users and role-based access for your team.
Security
Multi-factor authentication, recovery codes and controlled permissions on sensitive actions.
From service request to daily operation
Customer intent and engineering delivery stay attached to the same record, all the way through.
Discover and request
You browse the catalogue and submit a structured order.
Review and design
Our commercial and engineering teams validate scope, capacity and delivery detail.
Build and document
Ports, addressing, LOAs, cabling, routing and the service record are prepared.
Activate and observe
The live service picks up traffic, status and monitoring context.
Support and evolve
Tickets, maintenance, upgrades and billing stay connected to that service.
What the platform is watching
| Source | What it contributes |
|---|---|
| SNMP | Counters, status, inventory, optics and supported power and environmental sensors |
| sFlow | Traffic composition, ASN and prefix analysis, direction and customer attribution |
| BGP / BMP | Sessions, current paths, changes, next-hops, attributes and route provenance |
| Topology | Ports, sub-interfaces, VLAN transport, LAG membership and backbone dependencies |
| Service context | The customer, product, site and commercial record affected by an event |
DDoS awareness
Detection health, incidents, protected assets and adaptive baselines are visible to you. Mitigation itself stays operator-controlled, so a false positive cannot take your own traffic offline.
Absence of data is not health
The interface distinguishes healthy detection from missing, stale or incomplete evidence. A quiet graph because nothing is happening looks different from a quiet graph because nothing is being collected.
The panel is not a reporting layer
It sits on the same automation that configures the network. When a service is provisioned, the record in the panel and the configuration on the router come from the same source, which is why they do not drift apart.
That is also why changes are quick. A request raised through the panel becomes a templated change rather than a hand-edited config, and it lands the same way on every device it touches.
Modules
The engineering side of the platform. An engineer can move from an affected customer service to its port, device, topology, traffic and BGP evidence without rebuilding the story across separate tools. Ask for a walkthrough before you order and we will show you the real thing rather than a slide.
Accounts for your team
Separate logins with roles, so your NOC can see telemetry and raise faults while finance sees commitments and invoices.
Search and jump
One search box across services, ASNs, IP addresses, customers and facilities. Type a prefix, land on the service that carries it.
Notifications
Maintenance notices, service events and alerts in the panel, with email for anything that needs your attention out of hours.
Have a look before you buy
We will give you a guided tour of the panel with real data from our own network, so you can judge it rather than take our word for it.