The Mobees messaging core

Pillar 02 Messaging & Entitlement

An RCS-ready messaging core that replaces end-of-life stacks without a Tier-1 price tag or a Tier-1 lock-in. Six components that ship separately and work better together: SMSC, MMS Suite, RCS Provisioning, RBM Gateway, a GSMA TS.43 Entitlement Server and a Cell Broadcast Centre for public warning.

  • Cloud-native and Kubernetes-orchestrated, on your cluster or ours
  • Deployed one component at a time, in front of or behind what you already run
  • Multi-tenant from the ground up — built for MVNEs, not retrofitted
  • Every component ships with ProBee instrumentation, so you can see it working
  • Standards-first: 3GPP, GSMA RCS Universal Profile, TS.43, SMPP, MAP, MM1–MM9, TS 23.041

SMPP

MAP

SMSF / SMSoIP

MM1–MM9

RCS UP 2.x

GSMA TS.43

Google RBM / Jibe

Cell broadcast

Multi-tenant

Kubernetes

Zero-downtime cutover

The replacement window is open

Two things happened at once. The generation of messaging platforms sold in the 2000s reached end of support, and RCS stopped being optional: with iOS support shipped, the last structural barrier to cross-platform RCS is gone and operators who want it need entitlement, provisioning and business messaging components they never had to buy before.

Most operators do not want to solve that with another decade-long contract with a Tier-1 vendor. They want the specific components they are missing, integrated into what they already run, in weeks.

That is the entire premise of this product line. Buy the piece you are missing. Keep the rest. Nothing here requires you to replace anything you are happy with.

The components

Ordered the way customers usually buy them.

Show more
Entitlement Server

Entitlement Server

GSMA TS.43. The component Apple RCS, VoWiFi, VoLTE, eSIM transfer and watch pairing all depend on. Small ticket, short project, hard requirement.

Show more
Show more
RCS Provisioning

RCS Provisioning

Capability discovery and provisioning traffic at operator scale, with the observability that RCS rollouts are normally missing.

Show more
Show more
RBM Gateway

RBM Gateway

SMPP to RCS Business Messaging. Your existing A2P ecosystem reaches RBM without a single aggregator changing their integration.

Show more
Show more
Cell Broadcast Centre

Cell Broadcast Centre

3GPP public warning across 2G to 5G SA: EU-Alert, CMAS and ETWS from a CAP feed, with per-cell proof the alert went out.

Show more
Show more
SMSC

SMSC

Cloud-native short message service centre with 5G SMSF and SMSoIP, MAP and SMPP. The foundation under everything else.

Show more
Show more
MMS Suite

MMS Suite

MMSC, load balancer, transcoding agent and MM1/MM4/MM7 gateways. Built for replacing an end-of-life MMSC cleanly.

Show more

The MVNE network layer

MVNE platforms are strong where the BSS is: onboarding, rating, billing, partner and product management. The gap is almost always the same one. The network layer underneath — messaging, RCS, entitlement, A2P — gets referred out to the host operator or to a third party, and the margin goes with it.

Every component in this pillar is multi-tenant by construction: per-tenant configuration, routing, number ranges, branding, quotas, CDRs and assurance data. It sits behind an existing BSS through documented REST provisioning APIs, so onboarding a new MVNO stays a BSS workflow.

  • Per-tenant SMSC, MMSC and RCS provisioning with isolated routing and quotas
  • Per-tenant TS.43 entitlement — the requirement that blocks iOS RCS
  • Per-tenant A2P and RBM with separate aggregator relationships
  • Per-tenant CDRs and PX assurance data, so the SLA you sell is evidenced
  • Provisioned through your BSS, not through our admin console

How a replacement actually runs

PhaseWhat happensRisk control
ShadowNew platform deployed alongside the incumbent, receiving a mirrored copy of live traffic. It answers nothing.Zero production exposure. Behaviour compared message by message.
CanaryA defined slice — one prefix, one tenant, one interconnect — cut over for real traffic.Single command rollback. Blast radius defined in advance.
RampTraffic share increased on an agreed schedule, with PX monitored on both platforms simultaneously.Objective, wire-level comparison rather than vendor assertion.
CutoverRemaining traffic moved. Incumbent kept warm for an agreed period.Rollback remains available until you decide it is not needed.
DecommissionLegacy platform retired, licences terminated, data archived.Contractual savings start only when you are genuinely finished.
The same sequence we have used on every messaging replacement we have delivered. It is slow on purpose.

What our customers say

References are anonymised at the customer’s request. Named references and written reference letters are available under NDA.

Core network operations, Tier-1 MNO (DT group)

„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.”

Head of Platforms, MVNE serving 300k+ subscribers

„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.”

Delivery director, systems integrator, CEE

„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.”

Which component are you missing?

Most conversations here start with entitlement, because it is the one with a deadline attached.