Products

Three independent products, built to interoperate.

Metis is the XPaaS service orchestration platform for customer-facing telecom services, built so customers serve themselves — ordering, configuring and changing their own services without raising a ticket, while your teams keep oversight.

Themis is a standalone compliance product for number portability and number acquisition. It holds port-in, port-out and new-number allocation inside regulatory obligation, across your own numbers and third-party providers.

Agora is a standalone commerce platform for eSIM, built to sell through layers — direct to subscribers, through distributors, and through the resellers beneath them — each layer with its own catalogue, pricing and margin, governed from the top.

All three work with each other and with third parties, rather than living inside one another. Each stands alone — designed to operate independently, or together from the same deployment.

Scope

Four orchestration domains. We are one of them.

"Orchestration" now describes four separate problems in telecom, sold to four different buyers, with four different measures of success. A radio vendor, a billing specialist and an AI voice company all claim the word. Before evaluating any orchestration platform, including this one, it is worth establishing which one it actually means.

Network resourcesOut of scopeAccess, transport, wireless, optical, spectrum. Capacity allocation, routing, failover, energy. Not us.

IT, OSS and BSSOut of scopeBilling, CRM, assurance, alarms, order management, revenue. Not us — we integrate with yours and never replace it.

Services & communicationsNeotelosVoice, messaging, numbers, eSIM, network APIs, consent and context — the customer-facing services an operator sells. This is where all three Neotelos products sit.

Compute & workloadsOut of scopeGPU and accelerator scheduling, model placement, training and inference capacity. Not us.

The four domains run at different tempos. Radio decisions resolve in milliseconds; a regulated number port resolves over days. We play at the tempo of the customer request — and we will tell you plainly where our responsibility ends.

Counsel & craft

Metis

In production

XPaaS · X is whatever you sell next

Ships with

Subscriber self-service portalService operations consolePublic or your own cloud

The service orchestration platform operators run on.

Metis is a service orchestration platform composed of four modules. Take a single module to solve one problem, or orchestrate them together into a broader offering — the same platform and the same two surfaces underneath either way.

Why self-service. Most operator cost sits in work a customer would rather do themselves. A plan change, a new user, a number reassignment — each becomes a ticket, a queue and a delay, and the cost of serving a customer rises with every service you add. Self-service breaks that link: adding products stops adding headcount. It also changes what you can sell, because services too small to justify manual handling become viable once nobody has to touch them.

Module 01

Unified Communications

UCaaS

Serves business customers. Voice, video, messaging and presence delivered as one managed service, with each business administering its own users and numbers.

Module 02

Communications Platform

CPaaS

Serves developers at your customers. Programmable messaging, voice and verification reached as APIs, with keys, quotas and usage visible to the customer and governed by you.

Module 03

Numbers

MSISDN management

Serves your own operations. Inventory, allocation and reservation of the numbers you hold, so ranges, porting status and assignment are one record rather than a spreadsheet.

Module 04

eSIM / IoT

ICCID / MSISDN

Serves connected devices and their owners. Low-level ICCID and MSISDN management for operator SIM, eSIM and device fleets, at the network level rather than the commercial one.

Run one module, or orchestrate them together — Metis is leveraged individually or as a whole.

Supported engines

Metis is the orchestration and experience layer, not the media or messaging engine underneath. It drives the engines you already run, so modernising the customer experience does not mean replacing the network you have. Where you have no engine, we bring one.

Voice & UC applicationRibbon AS · Mida

Microsoft Teams enablementRibbon Connect · Nuwave

Messaging & CPaaSTwilio · Infobip (Beta) · Jambonz

Numbering & wholesaleDIDWW · BICS

Adding an engine does not change the customer experience or the operations console. The engine is a sourcing decision; the surfaces stay yours.

No BSS transformation programme

Metis does not replace your billing, CRM or inventory, and no operator should be asked to swap those to modernise a customer portal. Metis is the orchestration and experience layer above them: it originates the order, then hands each step to the system that already owns it.

Catalogue — publish the offers your BSS already defines, so self-service sells what your catalogue says.
Orders — Metis captures and sequences; fulfilment calls land in the OSS that provisions them.
Billing — usage and subscription events emitted to your billing stack. Metis never becomes a second source of billing truth.
Identity — accounts and entitlements reconcile with your CRM, so self-service acts on the record your staff see.
Provisioning — delegated to existing OSS flows where they exist, driven against the engine where they do not.
Assurance — faults raised in self-service open in the ticketing system your support teams run.

You modernise the customer-facing layer without a BSS transformation programme. The systems of record stay; the experience in front of them changes.

Independent products

Two more products, each vendor-agnostic by design.

Themis and Agora don't depend on Metis. They integrate with the XPaaS modules where it helps, and with third-party providers where the operator already has them.

Independent product

Themis

Not yet deployed Regulation & Order

Ships with

Porting request portalCompliance & audit consolePublic or your own cloud

Integrates with XPaaS Numbers · third-party number APIs · portability providers

Porting compliance, provable after the fact.

Themis is a standalone product focused on one hard problem: keeping porting and number-acquisition compliant. It integrates with the XPaaS Numbers module, with third-party number APIs and with portability providers — so the rules hold whoever moves the number.

Porting compliance — port-in and port-out against regulatory obligation.
Acquisition compliance — new-number allocation, eligibility and duty of process.
Multi-provider integration — XPaaS, number APIs and portability providers in one workflow.
Regulatory workflow — deadlines, approvals and obligations encoded, not remembered.
Evidence & audit — every action logged and reconstructable for a regulator.

Audit log

A porting dispute is decided on what you can prove, not what happened. Themis records the case as it runs, so the evidence exists before anyone asks for it.

Append-only — entries are written once, never edited or deleted. A correction is a new entry; the original stays visible.
Every actor — staff, customers, and the third-party providers and APIs acting on a request, each attributed rather than collapsed into "system".
Lifecycle — submission, validation, provider exchanges, deadlines met or missed, approvals, rejections and the reason for each.
State change — what a field held, what it became, who changed it and under what authority.
Replay — replay a single port end to end, at any past point in time, without reading raw logs.
Export — a complete, timestamped pack for one case or a date range, in a form a regulator or auditor can accept.
Retention — hold records for the period your licence requires, with deletion governed by the same rules rather than by hand.

Independent product

Agora

In production The marketplace

Ships with

eSIM storefrontMerchandising consolePublic or your own cloud+ Distributor portal

Integrates with Multiple eSIM vendors · XPaaS eSIM/IoT

Buying eSIM is easy. Selling it is not.

Buying eSIM connectivity is not the hard part. Selling it is. Agora sits above raw connectivity, integrating several eSIM vendors so supply is a sourcing decision rather than a dependency, and adds the commerce that turns supply into revenue. It is distinct from the Metis eSIM/IoT module, which handles low-level ICCID and MSISDN at the network level.

Why multiple layers. Most eSIM revenue in travel and IoT does not come from selling direct. It comes from partners who already own the customer — tour operators, travel agents, device makers, retail chains. Each wants to sell under its own name, at its own price, without seeing your cost or each other's terms. Agora is built for that shape of business.

You, the operator hold the vendor contracts and wholesale cost. Define the master catalogue, set margin floors, and see every sale across every partner.
Distributors buy at the rates you agree, publish their own selection from your catalogue at their own retail prices, under their own branding.
Resellers beneath them sell what their distributor allows, at prices it controls, seeing only their own scope. A distributor can build its own channel without touching your systems.
Subscribers buy from whichever storefront they arrived at, and receive a profile that activates on demand.

Each layer sees its own catalogue, pricing and margin, and nothing above it. Terms cascade downward; visibility does not travel back up.

Supply — integrate several eSIM providers and switch between them by cost, coverage or quality, without changing what customers see.
Issuance — profiles delivered by QR or in-app, activated on demand.
Settlement — track what each partner sold and what it owes, per layer.

How they relate

Three products, three jobs, no overlap.

MetisThe service orchestration platform. UCaaS, CPaaS, Numbers and eSIM/IoT, delivered through self-service surfaces on top of the engines you already run.

ThemisThe compliance product. Governs porting and number acquisition across your own inventory and external number and portability providers.

AgoraThe commerce product. Sources eSIM from multiple vendors and sells it through layers — direct, distributor, and reseller beneath them.

Where the lines fall

Two of the products touch things Metis also handles. The boundary in both cases is the same: Metis runs the asset, the other product governs or sells it.

Numbers vs ThemisMetis Numbers holds the inventory: what you own, what is assigned, what is free. Themis governs a number moving — in or out, against a regulator's clock and evidence requirements. Holding is operations; moving is compliance.

eSIM/IoT vs AgoraMetis eSIM/IoT is network-level: ICCID and MSISDN on your own SIM estate. Agora is commercial: sourcing profiles from eSIM vendors and selling them through a channel. One manages what you already run, the other sells what you buy.

Taken togetherA number can be held in Metis, ported under Themis, and sit behind a plan sold through Agora — without either product reaching into the others.

One architecture

Everyone gets the view built for them.

Across all three products, subscribers, staff and resellers each work in a surface shaped to their role — not a single panel bent to serve three audiences at once.

SubscriberSelf-service surface — subscriber portal, porting request portal or eSIM storefront

OperatorOperations console — service operations, compliance & audit, or merchandising

ResellerDistributor portal — scoped sell & provision, in Agora

DeploymentPublic cloud or bring your own cloud, on all three products

Why Neotelos

What else you could do.

Every alternative here is legitimate, and two of them are genuinely good answers for some operators. The objection is proportionality, not quality.

Incumbent suite vendorComplete, proven, and sold as an estate. A multi-year programme, an eight-figure commitment, and the customer-facing layer arrives last.

Build it in-houseFull control and exact fit. You now run a software team, own the roadmap forever, and every engine integration is yours to maintain.

Point tools, stitched togetherCheap and fast per tool. Becomes the fragmentation problem — systems that never agree, and integration debt that grows faster than the estate.

NeotelosThe customer-facing layer, modernised independently of the systems of record. One product at a time, on the estate you already run.

Deployment & data residency

Your data stays where your licence says it stays.

Telecom data is among the most tightly held categories there is — subscriber identity, numbers, call and message records, location. Where it physically sits is usually decided by your regulator and your licence, not by procurement preference. All three products deploy either way, without a different codebase or a reduced feature set.

Public cloudRun on our infrastructure in the region you choose. Fastest to stand up, and the right answer when residency rules permit it.

Bring your own cloudMetis, Themis and Agora deploy inside your own cloud tenancy or data centre. Subscriber data, call records and audit trails are created and stay inside a boundary you control and already had assessed.

Why bring your own cloud settles the privacy question

Controller — in fact as well as on paper. Personal data is processed inside your own infrastructure, so who holds it has one answer.
No transfer — data does not leave your tenancy, which removes the transfer-mechanism problem rather than documenting a solution to it.
Assessments — encryption, key management, access control, logging and retention follow controls you already run and have had audited.
Erasure — erasure obligations are carried out in infrastructure you hold, rather than requested from a processor and waited on.
Sub-processors — fewer third parties touch personal data, so the register you maintain and disclose stays short.

For operators under GDPR, or under national rules that go further on telecom data, this is usually the difference between a deployment that clears review and one that stalls in it.

τέλος

Take one product, or all three.

Tell us which workflow you're modernising first, and we'll show where Metis, Themis or Agora fits.