Routes
It picks the path
Per call, across every operator and supplier behind the layer.
Network Signal Orchestration
One Network, All Mobile Network Operators
One API contract. Twenty-two commands. Live in 35+ countries across EMEA, the Americas and APAC, with data from 60+ operators.
The problem
Operators hold the signal. Reaching them is the hard part.
You can reach a mobile operator on your own. But there are hundreds of them, each with its own contract, its own technical integration and its own negotiation, three to six months apiece. What you cannot build alone is governance over all of them at once: one contract, one bill, one record of what happened.
What the customer sees
What a SIM swap looks like to your risk engine.
The number is real and the handset is real. The SIM changed nine minutes ago, and only the network knows that.
What changes
One agreement.
One key. One call.
One endpoint in place of the thousand-plus operator-specific ones an integration team would otherwise carry.
Operator by operator
- One agreement per operator, per market
- A key and a portal for each of them
- Every operator moves its spec on its own calendar
- You resolve the route before you can call
- An invoice per operator, per market
- Silence when no operator can answer
- A new country is a new project
- Coverage you map yourself
- Keys scattered across operator portals
Through Plumma
- Sign once. We hold the operator agreements
- One API key, issued in days
- Normalised before your risk engine sees it
- Routed per call, with failover
- One invoice, one SLA
- A declared gap, and the call is not billed
- A new country is the same key and the same API
- The operators already under contract, already mapped
- Every key in one console
Every call
What happens on every call.
01
One request
A typed command against an MSISDN. One endpoint, one key, one schema, in every country.
02
Governed route
Each call goes to the best operator for that number, on availability, latency and cost. The decision is recorded.
03
Answer, or declared gap
You get the result. If no operator can serve the number you get a declared gap, and the call is not billed.
04
Record
Which operator answered, which version, what latency, what it cost. In the dashboard today, exportable into your own audit when that ships.
Coverage
A perimeter that grows.
Without you renegotiating anything.
35
markets ready to call today, each with at least 50% network coverage
22
commands returning different data, all behind one endpoint, one contract and one integration
66
countries where at least one operator has launched a network API commercially
38
network APIs on the GSMA CAMARA roadmap, to be exposed as commands on the key you already have, with no new integration and no new contract
The first two figures are ours, as of October 2026. The third comes from the GSMA Open Gateway record and describes the footprint of the category, not of Plumma. The fourth is a roadmap, not a capability you can call today. Coverage is stated per command and per market, because a country-level answer would be a guess.
The command set
Twenty-two commands.
One POST.
Identity and trust
- sim_swap
- Whether the SIM behind the number changed inside the fixed 240-hour window.
- port_fraud_shield
- Porting activity that fits an account takeover in progress.
- divert_detector
- Whether unconditional call forwarding is set on the line.
- digital_footprint
- Where the number shows up across online platforms.
- device_swap
- Whether the handset behind the number changed, and when.
- scam_check
- Whether the number is reported in scam activity. United Kingdom at launch.
- location_verification
- Whether the device is inside an area you declare, with a match rate.
Onboarding
- kyc_match
- Whether the details given match the operator's own record, attribute by attribute.
- age_verification
- That the line holder is over a threshold, with no document and no camera step.
- tenure_period
- Whether the line has been held longer than the period you ask about.
- commercial_segment
- A consumer line from a business line.
Connectivity and reachability
- network_presence
- Whether the line is live and reachable right now.
- roaming_intel
- Whether the line is roaming, and on which network.
- deactivation_point
- When the line was last deactivated.
- line_classification
- Mobile, landline and VoIP, told apart.
- qdr_history
- The line's quality-on-demand history.
- location_retrieval
- Where the device last reported itself, as an area rather than a point.
Number intelligence
- current_carrier
- The operator serving the line today: name, MCC, MNC, SPID, OCN, LRN.
- issuing_carrier
- The operator that originally issued the number.
- porting_timestamp
- Whether the number has ported, and when.
- porting_logs
- The porting events behind that date.
- churn_tracker
- The line's history of deactivations, swaps, suspensions and reactivations.
Where our money comes from
The licence and a thin markup are the whole of our revenue.
No rebate from a supplier, no volume kickback, no marketing fund. A layer paid by the suppliers it routes between cannot credibly tell you which one served you.
How you buy
Three doors in. The layer behind them is the same one.
One price per command, anywhere
One price per command in any country, with no licence and payment in advance. A console for keys and a few other actions. For a team proving something out without talking to anyone first.
A rate per cluster, and the console with it
Countries grouped by what they cost, one competitive rate for each cluster, and the Orchestration Lite licence on an annual base plus a seat per instance. A handful of numbers to forecast rather than a hundred.
Each market at what it costs, and routing you own
Every market priced at the average cost of supply there plus a minimal markup, with Orchestration Full: routing you configure, data enrichment, and the one edition where you can bring your own supplier contracts and pay us nothing on those calls.
Pricing leverage
Once a year we pool our clients’ volume and take it to the suppliers as one buyer.
A mid-sized business has nothing to negotiate with on its own. Inside the year's cohort it has a volume no single member could commit, and the rates and the capabilities that come back reach every member whatever its own size. Business and Enterprise clients are in it, and so are prospects already in conversation with us. It is the reason a smaller client is worth having rather than tolerated.
What happens next
Send us your number ranges and we return the coverage map.
Your own base, by operator, gaps included. Yours whether or not you go further.