Service assurance that starts in the signalling plane
ProBee probes read your live traffic — SS7/SIGTRAN, Diameter, SIP, SMPP, HTTP/2 — and turn it into predictive Protocol Experience (PX) metrics that your assurance, analytics and closed-loop automation can consume from day one.
Deutsche Telekom · T-Mobile Polska · Play Polska · Cosmote Greece · A1 Bulgaria · Vivacom Bulgaria
telco-grade systems in production
proven protocol integration modules
years running inside operator cores
regions: Europe, Middle East, Asia
Three audiences, one protocol layer underneath all of them.
Packet-level visibility into what your counters cannot show: which subscribers, which protocol dialogues, which peer, which node. Predictive alerts before the NOC ticket, on a stack your operations team already runs.
A complete, multi-tenant network layer under your BSS: SMSC, MMSC, RCS provisioning, RBM and a GSMA TS.43 entitlement server — plus per-tenant assurance so you can evidence the SLA you sell.
We are not an OSS/BSS vendor and never will be. We supply the protocol layer under your platform: the probes that generate KPIs, the network functions your MVNE customers ask for, and the southbound adapters your API catalogue needs.
We cut the catalogue. What is left is what we are genuinely best at, and what our customers actually buy.
Passive probes and active tests on one timeline. ProBee watches every protocol dialogue on the wire and predicts degradation; BeeTest proves the service works end to end from a real device. Both publish into the assurance platform, data lake or Grafana you already operate — we generate the KPIs, you keep the cockpit.
Predictive, protocol-level probes. PX metrics, anomaly detection and root-cause context from live signalling.
Active end-to-end service testing from real and emulated terminals, scheduled and correlated with probe data.
Managed assurance, PX baselining, model tuning and 24/7 protocol-level L3 support around your probe estate.
How ProBee data reaches your SQM, PM, fault management and closed-loop automation. Open interfaces only.
A cloud-native, RCS-ready messaging core that replaces end-of-life stacks without a Tier-1 price tag: SMSC, MMSC, RCS provisioning, an SMPP→RBM bridge, a cell broadcast centre for public warning, and a GSMA TS.43 entitlement server — the component every operator now needs for RCS on iOS, VoWiFi, VoLTE and eSIM transfer.
GSMA TS.43: RCS, VoWiFi, VoLTE, eSIM transfer, ODSA and watch pairing. The wedge for Apple RCS.
Control and observability over RCS provisioning traffic, at operator scale.
SMPP→RBM bridge: every aggregator already speaks SMPP, few speak RBM.
Public warning across 2G to 5G SA, with per-cell proof the alert went out.
MMSC, MMS load balancer, transcoding agent and gateways — built for EOL replacement.
CAMARA and GSMA Open Gateway are won or lost on the southbound. The northbound REST API is the easy half; the hard half is wiring SIM Swap, Number Verification, Device Location and KYC Match into HLR, HSS, UDM, PGW and the IN. That is the work we have been doing for eight years.
Small enough to move fast. Proven enough to run at Deutsche Telekom.
Integration in weeks and production in months is our normal delivery profile, because there is no account layer between you and the engineer writing the code.
Prometheus, Kafka, SNMP, syslog, REST, Grafana. Nothing we build requires you to buy the next thing we build, and source-code escrow is on the table from day one.
3GPP, GSMA (TS.43, RCS UP, Open Gateway), CAMARA and TM Forum-aligned data models. We fit your architecture; you do not refactor around us.
Kubernetes-orchestrated, containerised, horizontally scaled real-time systems. On your cluster, in your cloud, or on bare metal in your core.
Subscription and managed-service pricing, a fixed-price proof of concept with defined success criteria, and a documented path to production.
SS7/SIGTRAN, MAP, INAP, CAMEL, Diameter, SIP, SMPP, MM1–MM9, HTTP/2 5G core. Twenty-plus integration modules already proven in production.
Three anonymised deployments — what was broken, what we built, what changed.
End-of-life MMSC swapped for a cloud-native stack with zero-downtime cutover and full message-level observability.
ProBee probes on SS7 and Diameter; degradation detected ahead of the complaint queue, in the operator’s existing Grafana.
A multi-tenant network layer under an existing BSS, delivered per tenant without touching the BSS.
References are anonymised at the customer’s request. Named references and written reference letters are available under NDA.
„We were finding signalling degradations from the complaint queue. ProBee moved that left by roughly forty minutes — we now see the retransmission pattern build before the first customer calls. It is the same Grafana our NOC already lives in, so nobody had to learn a new console.”
„Our BSS was complete and our network layer was not. Mobees dropped in the messaging core and the TS.43 entitlement server behind our existing provisioning, per tenant. We stopped referring those deals out.”
„They are the people we call when a transformation programme hits SS7 or CAMEL and the schedule is already tight. Small team, no layers, an answer the same week.”
A thirty-minute technical call with an engineer, not a qualification script. If it is not our problem, we will say so.
