One price per command, a competitive rate per cluster of countries, or each market at what supply there costs, each with the edition of the layer that comes with it. Everything visible before you integrate, so the business case can be built before anyone from Plumma has spoken to you.
What you are buying
Two numbers on the invoice. The calls, and the layer.
The calls are supply. The layer is the routing, the console, the record of every decision, the contracting and the catalogue. They are priced separately because they move for different reasons, and which licence you need follows from how you buy the calls.
The calls
Priced three ways, and you pick the one you are in
One price per command anywhere, a competitive rate for a cluster of similar-cost countries, or each country at what the supply there actually costs plus a minimal markup. The three are set out below with the invoice each one produces.
The layer
Three editions, and the first one is free of charge
At the entry door there is no licence at all: a developer portal, keys and the API. Orchestration Lite is an annual base plus a seat per instance, priced for a team doing this for the first time. Orchestration Full is the enterprise edition and is the only one that lets you bring your own supplier contracts.
Terms that hold under every plan
Three of them, and they are in the contract.
01
Billed only when served
An integrated operator answers or you are not charged. Unserved calls appear on the invoice at zero rather than disappearing from it, and the unserved path never fails silently.
02
No exclusivity
We hold no exclusive arrangement with any aggregator or operator, and we will not sign one. Exclusivity upstream is what turns a router into a reseller.
03
Portability where you have it
Your configuration is yours. On Orchestration Full the layer runs on your own supplier credentials wherever you hold a contract, so that supplier invoices you directly and we take nothing on those calls.
How a call is priced
Pick the door, and the licence follows from it.
Each model carries its own edition of the orchestration layer, so the call price and what you can do with the console move together. All three are here before anyone from Plumma has spoken to you.
Operator contract held by
Plumma, in every market it serves
Plumma adds to the call price
A margin inside that price, set to be convenient rather than the lowest number available
What moves the number
The command, and nothing else.
Not the country, and not which operator answered.
Best when
You are a developer or a team proving something out, and you want keys today without talking to anyone.
What lands on your invoice
Orchestration licencenone
SIM swap, 4,100 callsone price
KYC match, 920 callsthe same price, any country
Unserved calls, 210not charged
One invoiceone number to forecast
Operator contract held by
Plumma, in every market it serves
Plumma adds to the call price
A margin inside the cluster rate, fixed for the contract term
What moves the number
Which cluster the number's country sits in.
Not which operator inside it answered, and not what that operator did to its own price this quarter.
Best when
You run real traffic across several markets and your budget owner wants a handful of numbers rather than a hundred.
What lands on your invoice
Orchestration Lite, annualbase plus seats
Cluster A calls, 22,400one rate for the cluster
Cluster B calls, 15,100one rate for the cluster
Cluster C calls, 3,700one rate for the cluster
Unserved calls, 1,840not charged
One invoicethree rates to forecast
Operator contract held by
Plumma, or you, market by market
Plumma adds to the call price
A minimal markup on the country's own cost, and nothing at all on supply you bring yourself
What moves the number
What supply in that country actually costs, and what you brought to it yourself.
Best when
You are at scale, the per-market number has to survive a finance review, and you hold supplier contracts of your own.
What lands on your invoice
Orchestration Full, annualenterprise licence
Italy calls, 61,000the country rate
Spain calls, 28,400the country rate
Brazil calls, 9,200your own supplier rate, zero margin
Unserved calls, 3,100not charged
One invoiceevery market priced as itself
And the edition of the layer that comes with it
No licence
Nothing to sign beyond the terms
Developer portal, keys and the API. No console and no routing control.
Pay as you go only.
Orchestration Lite
Annual base, plus a seat per instance or business unit
The console, the record of every call, and routing presets you select rather than configure.
Priced for a team doing this for the first time.
Orchestration Full
Enterprise licence, annual
Routing you configure, data enrichment, one contract and one invoice, compliance and DPO support.
The only edition that lets you bring your own provider, and what Enterprise is sold with.
Volumes above illustrate the shape of the invoice rather than quoting a price. Price points, the licence base and the seat definition are being set and are not published yet. Internally these three are the Single Price, Cluster Tiers and Country Price models, which is the wording that appears in an order form.
How we are paid
Nothing reaches us from a supplier, and nothing from you on supply you bring.
No rebate, no volume kickback, no marketing development fund, under any of the three models and at any size. A layer that takes a payment from the suppliers it routes between has no standing to tell you which one served you, and this sits in the shareholders' agreement rather than the brand guidelines, so taking supplier money would need a shareholder vote and not a sales decision in a short quarter. The same rule will run the other way on Clean Transparency, which is not available yet: where you hold your own contract with an operator or supplier, Orchestration Full will run on your credentials, that supplier invoices you at your rate, and we add no margin and no per-call fee on those calls. The licence is the only money that reaches us. It is available on Orchestration Full and nowhere else, because that is the edition where you can hold credentials at all.
How to compare
Nine questions to ask any vendor. Ours included.
01
Per-operator coverage
Is it disclosed inside each country, or only a country list? A country-level yes hides the operator-level no.
02
Independent suppliers
How many sit behind the endpoint? One supplier is an integration, not a route, and there is nothing to fall back to.
03
Whose credentials
Can you bring your own? If the layer holds them, the layer buys the call.
04
Per-call cost of supply
Is it disclosed to you? You cannot govern a cost you cannot see.
05
Does the layer earn on the call
Every intermediary says no. Ask what makes the answer checkable.
06
The fallback
Is it declared before you integrate? Undeclared, it becomes your incident.
07
Contracts signed
How many to reach this coverage? Confirm aggregation stayed removed.
08
The review artefact
Does it exist before the review opens? A vendor without it spends a quarter of your calendar.
09
The per-supplier statement
Regulated intermediaries elsewhere issue this as standard. Nobody in this one does.
The buying cohort
Every year we open a cohort, and take its volume to the suppliers as one buyer.
A mid-sized business negotiating with an operator group alone has nothing to negotiate with. Pooled with everyone else in that year's cohort, it has a volume no single member could commit, and Plumma takes that to suppliers and operators as one buyer at the table. What comes back is better rates and capabilities built to the cohort's demand, and both reach every member whatever its own size. The cohort is open to Business and Enterprise clients and to prospects in conversation with us. Members negotiate together and each still concludes its own supply terms. The structure follows Chapter 4 of the European Commission's 2023 Horizontal Cooperation Guidelines, the suppliers are told the cohort exists, and a competition opinion is taken before it convenes.
Five of the nine turn on artefacts we have not shipped.
Live means you can exercise it today. Designed and in build carry a date and nothing else.
Per-operator coverage disclosed inside each country, before you integrate
Live
Several independent suppliers behind one endpoint, with failover
Live
The declared fallback, documented per use case before you integrate
Live
One contract and one key for the whole footprint
Live
The routing ledger: per-call supplier, route, latency, outcome and cost in your own account
In build
The licence published as a number, with no contact-sales tierWaiting on a real operator rate card, because a number that moves later is worse than none.
In build
The pass-through audit right, letting your auditor inspect the supplier invoices behind your callsIn drafting.
In build
The per-supplier statement of what we received on your callsSecond half of the roadmap.
Designed
Bring your own supplier contract, running on your credentialsSecond half of the roadmap.
Designed
Start on the per-command price, or scope a licence.
Tell us the markets and the volume and we will tell you which of the three you are in, including when it is the one that costs you least.