Stem Connect
For network operators

Network operations for ISPs, VNOs and network owners

Running a network is a different problem from using one. These are outsourced operations services for organisations that own or resell network infrastructure across Africa — monitoring it, managing it, and reporting on it as an extension of your own team.

Four services that layer. Take the one that matches what your team does not want to carry.

Before you read on

Looking for connectivity for your own business?

This page is for organisations that run a network as their business. If you are buying connectivity and support for your own sites, the page you want is Managed Site, or Multi-Site Network across several locations.

The four services

Each builds on the one before it, so you can start where your own capability runs out rather than replacing what you already do well.

Stem NOC

Monitoring and incident control.

  • • 24/7 monitoring
  • • Alert triage
  • • Incident identification
  • • Ticket creation
  • • Notification and escalation
  • • Availability reporting

Stem Network Operations

NOC plus active operational management.

  • • All Stem NOC capabilities
  • • Configuration management
  • • Supplier management
  • • Capacity monitoring
  • • Change control
  • • Incident coordination
  • • Root-cause reporting
  • • Performance reporting

Stem VNO Management

End-to-end operational management for a virtual network operator or ISP.

  • • NOC and service assurance
  • • FNO and supplier management
  • • Provisioning support
  • • Capacity management
  • • Interconnect management
  • • Transit and peering oversight
  • • SLA management
  • • Billing reconciliation support
  • • Operational automation
  • • Management reporting

Stem Network Control

Dashboards, reporting and operational workflow automation.

  • • Network inventory
  • • Custom operational dashboards
  • • Performance and availability reporting
  • • Supplier scorecards
  • • Incident dashboards
  • • SLA reports
  • • Customer or management portals
  • • Workflow and notification automation
How it works

We operate, you own the customer

Your brand, your relationship
We work behind it. The customer contract, the pricing and the brand stay with you.
Your suppliers, managed
FNO and supplier management, interconnect, transit and peering oversight handled as part of the service.
Escalation that ends somewhere
Defined ownership and escalation rather than a ticket queue, with root-cause reporting after the fact.
Evidence you can show
Availability, SLA and performance reporting, plus supplier scorecards, in a form you can put in front of your own customers.

Frequently asked questions

Common questions from operators weighing up what to outsource.

Who is this for?

ISPs, VNOs and network owners who run a network of their own and want the operations of it handled by someone else. It is not the service a business buys for its own offices — that is Managed Site, and it is a separate proposition with a separate buying path.

What is the difference between Stem NOC and Stem Network Operations?

Stem NOC watches and escalates: monitoring, alert triage, incident identification, ticketing and availability reporting. Stem Network Operations adds the doing — configuration management, change control, supplier management, capacity monitoring, incident coordination and root-cause reporting. If you have people who act on tickets and want the watching outsourced, NOC is the fit. If you want the acting outsourced too, it is Network Operations.

Can you run a network under our brand?

That is what Stem VNO Management is. It covers the operational side of running as a virtual network operator end to end — service assurance, FNO and supplier management, provisioning, interconnect, transit and peering oversight, SLA management and billing reconciliation support. The customer relationship and the brand stay yours.

Do we have to take the whole stack?

No. The four services layer, so you can start with monitoring and add operational management later, or take Network Control on its own for reporting and dashboards over operations you already run. Where you start depends on what your own team already covers.

Tell us what you run

How many subscribers or sites, which FNOs you sit on, and what your own team covers today. That is enough for us to say which of the four is the right starting point and what it would take to stand up.