Carrier-grade signalling and core software, built in-house by the team that helped standardise telco. 148M+ subscribers across 30+ countries run on the AMTP platforms.
Ouroboros has been founded in Paris in 2004. The company is headquartered at Dublin, Ireland, and built around a French-origin and further Eurafrican engineering team with deep roots in telecom signalling.
That depth is not a marketing line. The founders contributed to the ISO and ITU-T standardisation of ASN.1, one of the formal roots of the signalling that mobile networks still run on today. When the team writes a signalling stack, it is writing from the standard, not from a third-party interpretation of it.
The company was also there at the start of machine-to-machine connectivity. Ouroboros took an active part in the first M2M MVNO in Europe, MobiquiThings, which Sierra Wireless acquired in 2015. The lessons from running real subscribers on a real network, at the point where M2M was still new, shaped how the platform is built today.
Since then the work has scaled. The platform now carries 148M+ subscribers across 30+ countries, backed by 384 man-years of R&D. Both the physical and the virtual product lines are developed in-house. There is no outsourced core, no white-labelled stack underneath.
Every Ouroboros product runs on one foundation: the AMTP, the Advanced Mobile Telecommunication Platform.
AMTP carries three things. It holds the signalling stacks, the formal protocol layers that let network elements talk to each other. It runs the core engine that processes every transaction on the network. And it exposes open APIs so the platform integrates with other vendors’ equipment rather than forcing a single-vendor network.
That last point matters to most operators. A network is rarely built from one supplier. The open API layer means Ouroboros elements sit alongside existing nodes and interwork with them through standard interfaces, so an operator can replace one component without rebuilding the rest.
Because the same platform underpins every product, an operator that starts with one element gains the same engine, the same standards compliance, and the same integration model across everything they add later.
The team is small and technical, which means decisions are fast and the people who answer your questions are the people who wrote the code. When a requirement changes, the platform adapts in weeks, not quarters.
The platform has been carrying production traffic since 2004 at 99.999% availability. That figure is not an aspiration. It is the record of a network that has been running for over two decades.
Products deploy on the infrastructure the operator already runs: bare metal, VMware, KVM, Docker, Kubernetes, or public cloud. Elements can be bought individually or as full stacks, and they interwork with third-party equipment through standard interfaces.
Two commercial models, chosen to fit how an operator wants to account for the cost. Both run on the same platform. The choice is financial, not technical.
A subscription model that aligns the cost of the platform with subscriber growth. There is no upfront capital commitment, so an operator does not pay for capacity before it carries revenue. This is the model most MVNOs and growing operators choose.
A one-time licence for operators that prefer to own the asset outright and account for it as capital. Common where procurement or regulatory structure favours ownership.
Every deployment comes with a tailored SLA. The support level is chosen per network, and the service levels are written into the contract. The SLAs are run by Wizardry Towers, a dedicated Ouroboros company based in Mauritius. Issues are logged as observation reports in the online support tool, with a phone line for critical incidents, and handled by severity, from a blocking error to a minor question.
Business-hours support, Central European Time, on a best-effort basis. For lab, pilot and small networks.
Business-hours support, Central European Time, with committed response and workaround targets for major and medium issues.
Support 24 hours a day, 7 days a week, with committed response and workaround targets for every severity.
Support 24/7 with the fastest commitments, and Ouroboros engineers acting directly on the operator's equipment, without needing the operator's technical staff.
Sets the technical direction of the platform and leads the engineering work. The standards background that shaped ASN.1 runs through how the products are built.
The team writes from the standards it helped author. That is the difference between a vendor that implements a protocol and one that understands why the protocol is written the way it is.
A core network does not get second chances. The work is held to the standard that 148M+ subscribers in production demand.
Operators get straight answers about what the platform does, what it costs, and how it integrates. No claims the team cannot back with a production reference.
Whether you are launching an MVNO, replacing an end-of-life core element, or planning a migration from 2G/3G to 4G/5G, the first conversation is with the engineers, not a sales script. Tell us where your network is today and we will tell you honestly whether we are the right fit.