An IoT connectivity platform
that thinks in fleets
Provision one device or ten thousand from the same call, and manage every profile from one place rather than one console per market.
Sandbox profiles are simulated and cost nothing. No card, no commitment.
True of every capability
- One call switches it on. No form, no approval step.
- One key covers everything. The same credentials across the platform.
- One invoice carries all of it. Every capability on a single bill.
- The sandbox works first. Build against simulated profiles from minute one.
- One click switches it off. Billing stops the moment you do.
Describe the fleet. We return the profiles.
Five choices. One call. The same object whether it issues one profile or ten thousand.FOOTPRINT
QUANTITY
PROFILE
RADIO
PER DEVICE
flt_Qb84nD500 of 500# A fleet of five hundred, as one call
POST /v1/fleets { "region": "europe", "count": 500, "form": "esim", "network": "lpwa", "limit_mb": 50 }
AT DEVICE SCALE
One device and ten thousand are the same call.
What changes with volume is the number in the request, not the shape of the integration.
Provision one
A single profile, to prove the integration on a bench unit.
Provision a batch
The same endpoint with a count. One response, one fleet id.
Act on the fleet
Suspend, resume or re-cap every profile in it with one call against the group.
Act on one
And still address a single device by its own id, without leaving the fleet.
Nothing about the integration changes between the first device and the last.
WHO IT IS FOR
For products where the customer is a device
A person notices a bad connection and complains. A device in a field does not, so what you need is the state of every one of them, queryable, without a console per market.
Nothing to sign before the first device. Provision a simulated fleet today, at no cost.
WHAT YOU GET
A fleet is addressable, and so is every device in it
Groups, states and events all come from the API, so a fleet of ten thousand is as queryable as a fleet of one.
- Provisioning
- One profile or a batch, from the same endpoint, returning one fleet you can act on.
- Grouping
- Tag by model, customer, site or anything else, and act on the tag rather than the list.
- Per device
- Its own allowance, its own state and its own history, addressable by id.
- Radio
- LTE-M and NB-IoT where the device is built for them, 4G and 5G where it is not.
- Events
- Webhooks on provisioned, first connection, threshold reached, suspended and resumed.
- Keys
- Test and live keys are prefixed, so the two can never be confused in a log or a commit.
- Retries
- Every call that changes something takes an idempotency key. Retry without provisioning twice.
- Errors
- One error shape everywhere, each carrying a link to the page that explains it.
- Reference
- A published OpenAPI spec. The server validates against it and the SDKs are generated from it.
DEVICE LIFECYCLE
Every state is queryable per device and per fleet, and every transition fires a webhook.
TWO WAYS TO BUILD
Choose your pathway. Same platform either way.
Neither route is faster than the other. They differ in what arrives afterwards.
Your screens, your way
Fleets, devices and events as endpoints. Build the operations view your engineers actually need rather than the one a portal gives you.
# Provision a fleet curl https://api.telyne.com/v1/fleets \ -H "Authorization: Bearer sk_live_4a11" \ -H "Idempotency-Key: fleet_0417" \ -d '{ "count":500, "region":"europe", "limit_mb":50 }'
# 201 Created { "id": "flt_Qb84nD", "provisioned": 500, "devices": "/v1/fleets/flt_Qb84nD/devices" }
A fleet is an object, not a spreadsheet.Act on the group or on one device by id, with the same authentication and the same error shape either way.
Our screens, inside your app
The fleet screens already built and themed to your brand: the device list, the per-device state, the suspend control, for when the people managing the estate are your customers rather than your engineers.
Built for a list that is long.The screens page, filter and act in bulk, because a fleet view that assumes twenty devices is useless at ten thousand.
undefined undefined
WORKS WITH
Switch on the next one the same way
Nothing new to sign and nothing new to integrate. The same call with a different noun.
QUESTIONS
IoT connectivity on Telyne
Do I need a different integration for ten thousand devices than for one?
No. The same endpoint provisions one device or a batch, and returns a fleet you can act on either as a group or device by device. What changes with volume is a number in the request.
Can each device have its own allowance?
Yes. A per-device ceiling can be set for the whole fleet at provisioning and then changed on any individual device afterwards, so one faulty unit cannot run up the bill for the rest.
What radio do the profiles use?
LTE-M and NB-IoT where the device is built for them, and 4G or 5G where it is not. It is a field on the request rather than a different product or a different agreement.
How is a device retired?
One call against its id, or against the fleet to retire the group. Billing stops when it does, and the device's history stays queryable afterwards so you can still reconcile the period it was live in.
Is this separate from eSIM and mobile data?
No. It is the same connection managed per device rather than per person: the profile comes from eSIM, the allowance from mobile data. One account, one key, one invoice.
Provision your first fleet before you have shipped a device
No approval step and nothing to sign. The sandbox is open now, and production access opens in the order requests arrive.
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.