MSP & IT providers
White-label engineering under your brand
Co-managed NOC/SOC, L2/L3 escalation and project engineering — your clients stay yours.
The problem
The client asks for what your team does not have
The tender asks for BGP, firewall architecture or overnight monitoring — and your team has one engineer who is already busy. Hiring takes months and carries risk, while handing the client to a competitor is final.
- You need the specialist only periodically
- The night shift is burning the team
- A large project outgrows the in-house resource
- You cannot show the client someone else's logo
What we deliver
White-label engineering under your brand
The partnership model
What stays with you, what comes to us, and how that looks to the client.
Escalation matrix
Severity, contact points, and when the call comes to us rather than to you.
Tooling under your brand
Monitoring and reports in your name — the client stays yours.
Engineering on demand
A certified engineer on a specific project, under subcontract and confidentiality.
Reporting
Incident, change and status reporting in the format you pass to the client.
Knowledge transfer
Documentation and training for your team — dependency is not the goal.
Architecture
Architecture
- 01ClientThe relationship runs through you
- 02Your first lineYour brand, your process
- Helpdesk
- Runbooks
- 03MonitoringIn your name, built by us
- Zabbix
- Prometheus
- Grafana
- LibreNMS
- 04L2/L3 escalationA certified engineer on demand
- BGP
- FortiGate
- Juniper
- 05ValidationThe change is proven in the lab first
- EVE-NG
- Rollback test
- 06ReportingYour format, your logo
- Incident report
- Change log
Operator consoles
Operator consoles
These exact systems run on the group's own infrastructure — the screenshots are processed before publication.
One map — MikroTik, Ubiquiti and Cambium together
A small or mid-sized operator's network is rarely single-vendor: MikroTik in the core, Ubiquiti on the wireless links, Cambium at the access layer. This map carries, per link, what operations actually runs on — wireless clients on the sector, CCQ, noise floor, airMAX quality and capacity, distance, frequency, Rx/Tx and uptime. The tower power nodes sit on the same map: battery voltage is a metric like any other here, and it explains half of the night-time outages.
WireGuard Portal — peers managed in one place
WireGuard is fast, but by default it is administered through config files — and by the twentieth peer that is a problem. The portal centralises key and peer management, adds self-service provisioning and shows who is connected right now. Interface state, MTU, DNS and keepalive on one screen.
IPAM — the address space in one system
A live phpIPAM deployment: subnet hierarchy, VLAN domains, VRFs, devices and locations in one searchable database. Only the aggregate statistics are public — customer names, individual subnets and locations are not on the frame, and should not be.
Capabilities
Capabilities
Every item is marked: verified production experience, or engineering capability.
White-label NOC
CapabilityL2/L3 escalation
ProvenProject engineering under subcontract
ProvenCo-managed monitoring
CapabilityBuilding the monitoring stack
ProvenZabbix, Prometheus, Grafana and LibreNMS — in daily use on our own network and deployed for clients in the same shape.
- Zabbix
- Prometheus
- Grafana
- LibreNMS
Lab and validation
ProvenThe migration plan is proven in EVE-NG before it touches your client's network.
- EVE-NG
- Rollback test
Technology stack
Technology stack
- Monitoring
- ZabbixPrometheusGrafanaLibreNMS
- Logging
- GraylogWazuhOpenSearch
- Network
- CiscoJuniperMikroTikFortiGate
- Validation
- EVE-NG
- Communication
- TelegramEmailRunbooks
Engagement model
Engagement model
Co-managed
NetWizard and your in-house team together, with split responsibility.
Retainer
Monthly engineering hours — specialist access on demand.
Project
A one-off scope: audit, migration or implementation with a fixed outcome.
Use cases
Use cases
A tender demands a competence
The bid needs BGP or firewall architecture. We come in as subcontractor, work under your brand, and the client relationship stays yours.
Nights and weekends
Your engineers work days. We take overnight monitoring and first response on an agreed escalation matrix.
The project is bigger than the team
A migration or a datacenter build needs parallel hands. We add engineering resource for the length of the project and hand over the documentation.
FAQ
FAQ
Will you approach our client directly?
No. The model is subcontracting: communication runs through you and our name appears only if you want it to. That is fixed in the contract.
Do you lock us into your tooling?
No. We work with what you already have; when we deploy something new it is open tooling, it stays in your infrastructure, and it comes with documentation.
How do we start?
Usually with one concrete task — monitoring for a single client, or one project. Once the process works, the scope widens.