Site and cabinet inspection apps
Checks with photo evidence, working at the foot of a mast with no signal.
Telecoms
Telecom software for sites nobody visits twice
Site inspection, asset records and a monitoring platform you host yourself. Built on the self-hosted IoT platform we delivered to a client who owns every record.
2028Last due date for Code measures, 31 March
3Provider tiers in the Telecommunications Security Code
£1bnRelevant turnover above which a provider is Tier 1
40+Developers on staff
What this is
Security duties land on the network, and the network is outdoors
The Electronic Communications (Security Measures) Regulations 2022 and the Telecommunications Security Code of Practice put staged duties on public telecoms providers. The evidence for many of them sits in sites, cabinets and masts that engineers visit.
Where we have proof
a self-hosted, multi-tenant IoT platform that feeds the systems an operator already runs
Where we have not yet
We have no published telecom case. We say so on the first call and show the closest work.
Services
What we build for telecom teams
Asset and site registers
What is installed where, when it was last inspected and by whom.
Self-hosted monitoring platforms
Multi-tenant, white-labelled and deployed where your security team wants it.
Telemetry ingest
Readings from site equipment over MQTT, with a broker in front.
Integration with ERP, CMMS and SCADA
The inspection result has to reach the system the work order lives in.
Access and role models
Contractors see their sites and nothing else, with sign-in handled for you.
Rules
What the telecoms security regime sets out
These come from the DSIT page on the regulations and Code of Practice, published on gov.uk.
Regulations from 1 October 2022The Electronic Communications (Security Measures) Regulations 2022 came into force on 1 October 2022. Source: DSIT, Regulations and Code of Practice, gov.uk.
Code in force from 1 December 2022The Telecommunications Security Code of Practice came into force on publication, 1 December 2022. A version 1.1 was published on 14 July 2026. Source: same page.
Measures due 2024 to 2028Code measures are due for implementation between 31 March 2024 and 31 March 2028, the last due date. Source: same page.
Three tiersTier 1 is relevant turnover above £1 billion and Tier 2 is above £50 million. Tier 3 providers are not expected to follow the Code. Source: same page.
Case study
A platform the client owns outright
Industrial IoT
IoT Core Engine
The client wanted off third-party IoT SaaS without losing the enterprise features their own customers expected. We built a self-hosted, white-labelled platform on an open-source base, with role-based access, single sign-on and reporting built in, features SaaS vendors usually keep for the top tier.
Self-hostedOn-premise, private cloud or hybrid
Who we build for
The teams who call us
Network operators
Providers that must evidence security measures across many sites.
Infrastructure and tower companies
Asset owners with inspection teams spread across a region.
Field service contractors
Teams visiting sites on behalf of the network owner.
Telecom product vendors
Companies that need the monitoring platform under their own brand.
Related reading: energy and utilities software, manufacturing software and SaaS software.
FAQs
What buyers ask first
Do you have a telecom case?
Not yet published. We say so on the first call and show the closest work, which is a self-hosted multi-tenant IoT platform.
Do you give advice on the Code of Practice?
No. That sits with your security and compliance team and Ofcom. We build the records and systems they specify.
Can the platform run inside our network?
Yes. The platform we built runs on-premise, in a private cloud or hybrid.
Who owns the code and the cloud accounts?
You do, from the first commit. Repositories and cloud accounts stay in your name.
Send us one site type
Thirty minutes with the engineers on what you inspect, how the evidence gets back and where it has to land.