HOW PRICING WORKS
Metered on what you use,
on one invoice
The developer platform is free. Each connectivity capability you activate carries a monthly fee and usage metered in its own unit, on one invoice. There is no minimum term, no commitment and no notice period.
The sandbox is free and stays free. Nothing there is rated and nothing is invoiced.
THE SHAPE
How the model is put together
This is the structure. The numbers that go into it are not set, and this page will not guess at them.
- Two parts, per capability
- A monthly fee for each connectivity capability you activate, and usage metered in whatever unit that capability counts. Activating a second one is a second monthly fee.
- Some charge per resource
- Where a capability issues something you hold rather than something you switch on, the monthly fee is per resource. Virtual numbers is charged per number. The capability page says which shape applies before you build against it.
- Metered
- Usage is recorded as it happens rather than estimated in advance or reconciled a month later.
- One invoice
- Every capability you have switched on, on a single bill, rather than one per supplier or one per silo.
- No minimum term
- One profile is an account. Nothing has to be forecast before you can start.
- No commitment
- No annual term and no notice period. A connectivity capability switched off today stops its fee and its metering today.
- No charge for the platform
- All ten developer capabilities are on for every account at no cost: keys, the API, SDKs, webhooks, the sandbox, the explorer, logs, events, documentation and test data. You are charged for connectivity, not for access.
- Nothing for the sandbox
- Simulated resources are free and stay free, and a capability you have only exercised in the sandbox carries no monthly fee. The fee starts when you activate it for live traffic. There is no card to enter to start.
WHAT YOU CAN CHECK
Every figure on the invoice traces to a record
Rated usage is queryable at the same resolution it is billed at, which is the only way a bill can be checked rather than accepted.
- Live usage
- Visible as it accrues, not at the end of the period.
- Per capability
- Attributed to the capability, the profile and the period, so a figure can be traced rather than argued about.
- Thresholds
- Set a ceiling and be told before it is reached. Usage controls can stop a resource rather than only warn about it.
- Reconciliation
- The dashboard and the invoice read from the same records, so they cannot disagree.
IN PRACTICE
What the model looks like from an account
The same four moves, whichever capability you start with.
You activate eSIM
Its monthly fee starts. Nothing else on the account changes, and nothing you have not activated appears on the bill.
You issue profiles
Each one meters in the unit eSIM counts. That usage is a second line beside the fee, not a replacement for it.
You add Roaming
A second capability is a second monthly fee, with its own usage in its own unit. The first is untouched.
You switch eSIM off
Its fee and its metering stop that day. Roaming carries on. There is no term to serve out and no notice to give.
The developer platform sits underneath all four and never appears on the bill, because it costs nothing. The sandbox does not start a fee: a capability you have only exercised there is not activated.
TWO SIDES
What you consume, and what you sell
If you resell, there are two transactions. They run on different rails and neither one is the other's cost line.
# Telyne invoices you. Metered, itemised, one invoice.
from Telyne
to your account
for every capability you switched on
unit whatever that capability meters
terms no minimum term, no commitment, no notice periodTwo transactions, and they do not meet. What you charge is not derived from what you are charged, and Telyne never sees it.
WHAT YOU CHARGE
Your prices are yours
If you resell, there are two transactions and they do not touch. Telyne invoices you for what your account consumed. You invoice your customers for what you sold them, through your own payment provider, at prices you set, and you are merchant of record for those sales.
QUESTIONS
Pricing on Telyne
Where are the rates?
Not set yet, and not guessed at here. The platform fee goes on this page in the open once it is decided. Per-capability rates sit in the dashboard behind sign-up, each in the unit that capability meters, because a gigabyte and a profile do not compare and a single table would imply they do. What is settled is the structure above, and that is what tells you whether the model fits.
Am I charged for what I provision or for what is used?
For what is used. A twenty gigabyte ceiling on a profile that used six is rated at six. A ceiling is a control, not a purchase.
What does the developer platform cost?
Nothing. Keys, the sandbox, SDKs, webhooks, logs, the explorer, documentation and test data are on for every account from the first minute at no additional cost.
Is there a minimum or a commitment?
Neither. One profile is an account, there is no annual term and no notice period, and a connectivity capability switched off today stops its monthly fee and its metering today. The developer platform has nothing to switch off, because it costs nothing.
Can I check the invoice against something?
Yes. Rated usage is queryable at the same resolution it is billed at, attributed per capability and per period, so every figure traces to a record rather than to a summary.
Get the rate card when it is ready
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.