Every telecom service, one platform.Switch them on and off as you like.
Issue an eSIM profile, open a mobile data plan or bring an IoT fleet online with one API call, and manage usage, roaming and lifecycle through the same keys: one API, one dashboard and one bill, with no contracts and nothing to build.
19 telecom capabilities. One platform.
Switch on what you need, when you need it. Some of the most-asked-for are below; the full catalogue follows.
eSIM
Issue an eSIM profile with one API call, metered as it is used.
Mobile data
Plans and allowances across the same coverage.
IoT connectivity
Profiles managed per device rather than per person.
Usage controls
Caps, alerts and automatic suspension on any profile.
Physical SIM
Plastic, provisioned by the same call as a profile.
Roaming
Coverage as a field on the profile, not a separate product.
SIM lifecycle
Suspend, resume, transfer and retire, one call each.
UK MVNO
Your own UK mobile service, under your own brand, on the Vodafone network.
Virtual numbers
Telephone numbers your product owns, ordered in your portal and carrying calls and SMS in both directions.
API keys
One key per environment, identifiable on sight.
Each label is the capability's activation route. Its current state is on its own page, stated before you build against it.
One API design across telecom.
Same authentication, same pagination, same event envelope, same error shape and the same logs, whichever capability you are calling. Learn it once.
Every capability you switch on appears in the same dashboard and lands on the same invoice.
See the API design# The object shape, as the specification defines it.
curl https://api.telyne.com/v1/esim \
-H "Authorization: Bearer sk_test_..." \
-H "Idempotency-Key: 9f2c-4a11" \
-d region="GB" \
-d body="Your code is 481920"
// The object shape, as the specification defines it.
import Telyne from "telyne";
const t = new Telyne(process.env.TELYNE_KEY);
const msg = await t.messages.create({
to: "+447700900000",
body: "Your code is 481920"
}, { idempotencyKey: "9f2c-4a11" });
# The object shape, as the specification defines it.
import telyne
t = telyne.Client(api_key=os.environ["TELYNE_KEY"])
msg = t.messages.create(
to="+447700900000",
body="Your code is 481920",
idempotency_key="9f2c-4a11",
)
// One envelope for every capability. Same signature scheme throughout.
{
"id": "evt_9f2c4a11",
"type": "message.delivered",
"created": "2026-08-06T09:14:22Z",
"livemode": false,
"data": {
"object": "message",
"id": "msg_84jd0",
"status": "delivered"
}
}
// One error shape across every capability.
{
"error": {
"type": "invalid_request",
"code": "number_not_reachable",
"message": "That number could not be reached on any route.",
"param": "to",
"request_id": "req_2c81f"
}
}
Every example above is the object shape the published specification defines, the same one the server validates against and the SDKs are generated from.
- One object model
- One event envelope
- One error taxonomy
- Unified webhooks
- Sandbox from minute one
- Instant API keys
Telecom is fragmented by default.
Each capability arrives with its own supplier, API, contract, portal and invoice. The work of holding that together grows every time you add something.
Fragmented by default
- A separate supplier for each capability
- A different API and auth model for each one
- A separate contract and commercial negotiation
- A portal and a login per product
- An invoice per supplier, in a different format
- Support handed between vendors
- A new integration project every time you add something
Operated as one platform
- One platform account
- One API design across every capability
- One commercial relationship
- One dashboard and one login
- One itemised bill, split by capability
- One support entry point
- Capabilities added through the same operating model
Tick a service. It’s on.
Where a capability can activate instantly, it does. Where it genuinely needs configuration, evidence or a conversation, you see that before you commit, not after.
Capabilities
Everything available to your account, in one list.
enableenableenableAll 19 capabilities
Every capability runs on the same API design, appears in the same dashboard and lands on the same invoice.
Connectivity 8
Communications 1
Developer platform 10
Every capability is open in the sandbox to anyone, with no verification of any kind. Approval means that capability needs the business verified before it goes live — asked once for your account, at the point you first open one that needs it, and never again.
Everything you enable. One operational view.
Activation status, usage, spend, alerts, logs, billing and permissions for every enabled capability, in the same place and on the same invoice.
Every figure on this screen is invented demo data shown to illustrate the interface. Nothing here describes real traffic, real customers or real availability.
Built for teams who need telecom, not a telecom department.
Different businesses arrive needing one capability. Most end up needing three.
Put connectivity in your product with one REST API and a test key that works from the first minute, before any verification.
Suspend, resume, transfer and retire every client’s profiles with one call each, and set a spend cap on any of them.
Issue an eSIM profile that works on arrival, with coverage as a field on the profile rather than a separate roaming product.
One profile per device rather than per person, with a ceiling set for the whole fleet at provisioning and changed on any single device after.
Mobile data at every site on one account and one invoice, with a spend cap per location and one place to suspend a connection.
An estate to move, several suppliers to consolidate, or a requirement that does not fit a signup form. Start with a conversation.
White label is a separate commercial journey with its own products, terms and partner application.
Enable what you need. Pay for what you use.
The model is simple to state. The rates are not one number, and we would rather explain that than pretend otherwise.
Keys, the API, SDKs, webhooks, the sandbox, the explorer, logs, events, documentation and test data. Included with every account at no cost.
A monthly fee for each one you activate, plus usage in whatever unit that capability meters. Both itemised on one invoice.
Higher support commitments and contractual assurance are agreed per customer rather than listed.
A gigabyte in one country does not cost what a gigabyte costs in another, and a profile is not measured in gigabytes at all. Per-capability rates sit in the dashboard, each in the unit that capability meters. The platform fee is public once it is set.
What we can tell you today.
Here is what is true right now, and nothing that is not.
Telyne is operated by Novaqube Limited, registered in England and Wales. A named legal entity you can look up.
Scoped, revocable API keys, signed webhooks, encrypted transport and least-privilege access as the starting position.
Every provisioning action, permission change and key event recorded, so you can answer what happened and when.
If something is degraded or broken, you hear it from us in our own words rather than finding it yourself.
Retention is stated on the form that collects it and enforced on a schedule, and an export is yours to take without asking us.
Every capability on this site is labelled with its real state. We would rather lose a signup than mislead one.
Build once. Add telecom capabilities as you grow.
Join the waiting list and we will email you once, when it opens, with the rate cards and the capabilities that are ready first.
One email at launch. Nothing else, and unsubscribe in one click.
We send a link to confirm the address. Unconfirmed addresses are deleted after 30 days.
Complex requirement or an existing estate to move? Talk to us.