ABOUT TELYNE
Telecom is sold one
supplier at a time
Every capability arrives with its own contract, its own portal, its own credentials and its own invoice. The cost of assembling them falls on whoever wants more than one, and that cost is the reason most products only ever have one.
THE PROBLEM
The integration cost is the whole problem
Nobody sets out to run five supplier relationships. They end up with them because each capability was bought separately, at a different time, by a different argument.
- Five contracts
- Each with its own term, its own notice period and its own minimum.
- Five integrations
- Each with its own object model, authentication scheme and error format.
- Five invoices
- Arriving at different times, in different formats, reconciled by hand.
- No shared view
- What a customer costs across all five is a spreadsheet somebody maintains.
WHO PAYS IT
The cost lands on whoever wants more than one
Nobody sells the integration. It is what is left over after everyone has sold you their part.
WHAT WE DECIDED
One integration, and the rest is switching
The decisions below are the ones everything else follows from. They are constraints we accepted rather than features we added.
- One API
- There is one platform and one API. Every convenience is built on top of it and none can do anything it cannot.
- One of everything else
- One object model, one authentication scheme, one event envelope, one error taxonomy, one invoice.
- Operations included
- Rating, reconciliation and billing are ours rather than left to you. Reselling connectivity without them is just reselling connectivity.
- Honest state
- A capability that is not open says so before you build against it, on its own page, rather than at the end.
- Sandbox first
- Prove it fits before anyone signs anything.
HOW WE TALK ABOUT IT
What you will not find here
These are rules we hold ourselves to on this site, and they are the reason some pages say less than a competitor's would.
QUESTIONS
About Telyne
What does Telyne actually do?
It puts one API, one key and one invoice in front of capabilities that are normally bought one supplier at a time, and the developer platform you integrate with them through.
Are you a reseller?
The platform is ours: the object model, the developer platform and the routing decisions. Underneath it, specialist providers carry traffic, which is where they belong and not something your integration has to know about.
Why is there so little detail on some pages?
Because we will not write what we cannot stand behind. Where a number, a date or a name is not confirmed, the page says less rather than inventing one, and this site is checked against that rule.
When can I use it?
Production access opens in the order waiting-list requests arrive. The sandbox is what to use in the meantime, and the integration you build there is the one you ship.
Be told when it opens
Join the waiting list and we will email you once, when it opens, with 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.