Customer experience

UXHub

Launch a branded self-service experience for plan purchase, activation, usage, billing, upgrades, and support.

YOUR BRANDPLANSSELF-SERVICESUPPORTExplore UXHub
Three hubs on one data model, one API, and one invoice.Read the API docs
MVNE PLATFORM · eSIM, IoT CONNECTIVITY, BILLING & AI VOICE

Turn Mobile Connectivity Into Your Next Product.

Bring your own network, customize plans, and own the customer experience. We handle telecom complexity.

88% faster
to launch a market
180+
countries
30+
operator integrations
CONNECTIVITY BEHIND
ButlrAngel WatchWeLinkRSVP WirelessNew Day LogisticsRocketPhoneEazybe
THE CONNECTIVITY CHALLENGE

Add connectivity.
Not telecom overhead.

Adding connectivity shouldn't mean managing operators, activations, and billing instead of growing your business.

  1. 01

    Multi-operator connectivity is fragmented

    Different operators mean different pricing, APIs, and processes. Managing them separately makes expansion harder and slower.

  2. 02

    Connectivity adds a new operational layer

    Multiple systems complicate SIM activations, plan changes, usage tracking, and support.

  3. 03

    Billing gets complicated fast

    Tracking costs and protecting margins become harder with varying operator rates, changes, and customer plan revisions.

THE PLATFORM

Four layers. One connectivity stack.

From operator access to billing and customer management, run your connectivity business on one platform.

Source and orchestrate connectivity

Access pre-integrated operators across 180+ countries through one API.

telecomhub / routing tablelive
OPERATORSIGNALLATENCYSTATE
US Operator 1US · LTE-M
28 ms
routing
US Operator 2US · LTE-M
31 ms
routing
US Operator 3US · LTE-M
36 ms
standby
US Operator 4US · LTE
44 ms
standby
US Operator 5US · Cat-1
52 ms
degraded
PATCH /v1/sims/8944…/routing {"policy":"cost+coverage"} 200 OK
THE CONNECTIVITY LIFECYCLE

One API from activation to billing.

Provision, manage, optimize, and bill connectivity across operators.

  1. 01

    Provision

    Order SIMs, provision eSIMs, assign plans, and activate service across operators.

    POST /v1/sims { profile, markets[] }
  2. 02

    Connect

    Connect devices, choose networks, and manage service across operators.

    PATCH /v1/sims/:id { routing: "auto" }
  3. 03

    Control

    Track usage, change plans, set alerts, and manage every SIM and subscription.

    webhook sim.usage.threshold
  4. 04

    Bill

    Rate usage, manage subscriptions, and automate customer billing.

    GET /v1/invoices?period=2026-08
THE ALTERNATIVES

Three ways to get connectivity. One of them scales.

Already working with carriers or building your own stack? See how Spenza compares on cost, flexibility, and operations.

Capability
Direct with a carrierTHE USUAL FIRST MOVE
Build it in-houseTHE IN-HOUSE BUILD
ONE PLATFORM, FOUR HUBS
Time to first market
Carrier contracts delay launch.
Build integrations before launch.
Go live with integrations and billing in place.
Adding new markets
A fifth contract, a fifth portal, a fifth invoice.
A fifth integration your team now owns forever.
A line in a config. Same dashboard, same invoice.
Cost per line at scale
Smartphone pricing on sensor traffic, and no lever to pull.
Better rates, if you win a wholesale negotiation.
Pooled plans and routing across 30+ operators. 30% typical reduction.
Changing networks
A truck roll and a physical SIM swap.
You build and maintain the multi-IMSI logic yourself.
Over the air, per device, no SIM swap.
Billing your own customers
Out of scope. You add a billing vendor.
Rating, tax, KYC, and payouts are all yours to maintain.
Branded checkout, invoicing, and reseller payouts included.
Powering AI agents
A separate CPaaS vendor and a separate invoice.
Another API, another number inventory to manage.
AgentHub. Same API, same billing rails.
When something breaks
A general support queue, at the tier your contract covers.
Every carrier escalation lands on your on-call rotation.
A named launch team and a shared channel from day one.

Already working with carriers or running your own stack?

Keep your existing operator relationships and customer setup. Move connectivity and billing to Spenza at your own pace.

Talk to us about migration
CUSTOMER PROOF

What changed after
they moved to Spenza.

Three business models, one platform. Each story shows where the team started, what they moved, and what changed.

All case studies

Butlr

88%

Faster time to market for a new country, against their previous carrier process.

STARTING POINT
New countries launched through their previous carrier process.
WHAT MOVED
High-bandwidth plans for smart building sensors across the US, UK, and France.
WHAT CHANGED
All three markets on one invoice, at lower total telecom cost.

Multi-country connectivity stopped being an operational burden and became a strategic asset.

FROM THE BUTLR CASE STUDY
3markets live: US, UK, France
1invoice across every country
Lowertotal telecom cost
RUNS ONTelecomHubControlHub
Read the Butlr story
88%

Faster to launch a new market than building the carrier stack yourself

180+

Countries with local operator access

30+

Pre-built operator integrations

30%

Typical connectivity cost reduction after routing and plan right-sizing

CONNECTIVITY BEHIND
ButlrAngel WatchWeLinkRSVP WirelessNew Day LogisticsRocketPhoneEazybe
WHY WE BUILT SPENZA

Connectivity should be a line in your config, not a year of your roadmap.

Carriers built their systems for handsets and monthly consumer plans. Everything since — a sensor in a shipping container, a watch on a child, an agent answering a support line — has had to be bolted onto that model one contract at a time.

Spenza exists so that work happens once, in one place, and every team that follows inherits it. That is the whole thesis, and it is why sourcing, cost, billing, and voice sit on a single data model rather than four products with a shared logo.

More about the company

What buyers ask before the demo.

More in the full FAQ and the developer docs.

What is an MVNE, and what does Spenza actually do?

An MVNE is the technical and commercial stack a company runs an MVNO or a connectivity business on, without owning network infrastructure. Spenza is that stack in four parts: operator sourcing and eSIM routing (TelecomHub), cost intelligence across every line and invoice (ControlHub), branded plans, checkout, billing and support (UXHub), and phone numbers, SMS and voice for AI agents (AgentHub). One data model, one API, one invoice.

Who runs on Spenza?

Device makers and IoT fleets, consumer brands selling a subscription alongside hardware, MSPs and resellers running an MVNO, travel eSIM brands, AI product teams that need a real phone line, and enterprises replacing phone stipends with managed lines. Angel Watch, Butlr, MSP-A, and Daito are on the platform today.

How does Spenza handle IoT fleets at scale?

Over API. SIM and eSIM provisioning in bulk, usage monitoring per line, threshold alerts, over-the-air operator switching with no physical SIM swap, and fleet-wide operations. LTE-M, NB-IoT, Cat-1, and LTE run across every aggregated operator.

Can we keep our existing carrier agreements?

Yes. Use the operators Spenza has aggregated, bring your own contracts, or combine the two. Every line shows up in the same dashboard, API, and invoice.

Can we give an AI agent a real phone number?

Yes, through AgentHub. Provision a local or toll-free number in 40+ countries, attach it to an agent, and handle SMS, voice, and realtime audio streaming over the same API and the same billing rails as the rest of your connectivity.

How fast can we launch, and how is it priced?

Teams reach live service roughly 88% faster than building the carrier stack themselves, with two to three engineering hours of integration. Pricing is per line, with volume tiers for large fleets. The calculator gives an estimate; a demo gives a projection for your fleet.

See Spenza in action

Share your connectivity needs. We'll walk you through operator options, deployment timelines, and estimated costs.