Company
Tosso works on the part of telecommunications that is unglamorous and compounding: making equipment from different suppliers work together, and making the data they produce comparable. Both are slow to build and hard to copy.
How we work
Every product that writes to a live network inherits a change board, a security review and a carrier-grade on-call obligation. We read exports instead. This is the business model, not a limitation we hope to remove.
Cross-vendor numbers are labelled exact, directional or not comparable. Presenting a comparison without the grade is how a product loses an engineer’s trust permanently — so we grade everything, including the numbers that make us look worse.
Every finding traces back to the source file, the vendor-native counter names and the KPI definition version used. A diagnosis that cannot be reproduced by the vendor’s own engineer creates no leverage in that conversation.
We do not act as a channel for the RAN vendors whose equipment our reports assess. The moment that changes, the verification reports stop being worth reading.
Organisation
Owns O-RAN architecture direction, interoperability methodology and the technical roadmap spanning both the equipment line and the platform. Equipment specification, test methodology and diagnostic design all originate here.
Owns ingest, the vendor connector library, counter dictionaries, the canonical data model and the diagnosis engine. Unglamorous, compounding work — and the platform’s most durable asset.
Owns build, configuration, test and pre-ship verification at the facility, working to the reference configurations set by architecture.
Owns supply chain, dispatch, finance and regulatory compliance for the operating site.
Careers
Capability here is concentrated in a small number of people, and the pool of engineers who have done this work at carrier scale is genuinely small. We hire accordingly.
Sets O-RAN architecture direction across both business lines, defines the interoperability and normalization methodology, and translates operator and vendor requirements into equipment specification and platform design.
The role both lines depend onBuilds and maintains the vendor connectors, counter dictionaries and canonical model. Every vendor, every software release, every counter rename.
connector library · dictionaries · modelConfigures, tests and verifies equipment against reference configurations before dispatch, and supports customers bringing multi-vendor equipment into service.
build · configuration · verificationInterested? Write to info@selzr.com with a short note on the hardest integration problem you have personally solved.
Get in touch
Talk to us about a scoped investigation, an equipment programme, or an engineering engagement.