TM Forum ODA and Open APIs
MEF.DEV exposes TM Forum Open APIs, follows ODA principles and has an entry in the TM Forum ODA Component Directory.
Show this site for
Region: Global. Your role choice is kept for this visit only.
TM Forum ODA · Open API · A2A · A2A-T · MCP
TM Forum ODA · Open API · legacy BSS
A2A-T · Trusted Gateway · TM Forum IG1453
Partner products · B2B2X · settlement
RFI · licence · EU company · ISO 9001:2015
TM Forum ODA · TMF Open API · platform.mef.dev
Partnership · plugins · BPMN low-code
Change one domain at a time instead of a multi-year replacement: channels, partner products and AI agents connect through one governed layer, so revenue projects stop waiting for core migrations. Proven at Kyivstar (VEON) and in TM Forum Catalysts.
Put stable TM Forum contracts in front of legacy systems so channel and partner changes stop rippling through the back end, and replace each domain behind the same API when you decide. Measure it in lead time, not in migration slides.
Every agent-to-agent call is authorised for its specific purpose and recorded, so you add agents from different vendors without handing out permanent access. Proven in TM Forum Catalysts 2025 and 2026.
Onboard third-party products, bundle them with connectivity and settle revenue on one repeatable process — no core BSS change for every new partner. At Kyivstar (VEON), a partner's satellite data service went from configuration to its first customers in three weeks.
Check an EU company, published BSL 1.1 licence terms, a TM Forum Catalyst record and a named production reference — Kyivstar (VEON) — what an RFI asks for, in one place.
Check the component model, deployment, authorization and the TMF Open API layer against exact anchors on platform.mef.dev — start with the architect's reading path.
Deliver the piece of an operator solution you do not have on a stack running in production at an operator — or launch your own products on it with our commercial support.
What we solve
Agents from different vendors start acting in operations, but no one can show which agent did what, on whose authority — and permanent access becomes the default.
Read more →One tariff and one billing cycle for every device make IoT customers overpay or churn, and slices and 5G traffic need their own rating next to legacy.
Read more →Every new channel, product or partner means another change in billing and CRM built decades ago; projects wait for the core, and a full replacement is a multi-year risk.
Read more →The BPMN model is compiled into a versioned application, not interpreted as a script: a process change ships as a new version of compiled code.
Read more →Each partner deal needs its own integration and commercial setup; launches take quarters, and revenue sharing is reconciled by hand.
Read more →Proof
Kyivstar (VEON): legacy BSS swap for OTT and fixed services
OSS/BSS modernization behind TM Forum Open APIs →
TM Forum Catalyst
Trusted multi-vendor AI agents →
How we work
The project runs in short releases: analysis, integration, migration, training and cutover repeat in each, so requirement changes during the project go into the next release instead of stopping delivery. Every workstream has an owner on the operator side and on ours.
A2A-T · Secure Passport · evidence
The same for every reader
MEF.DEV exposes TM Forum Open APIs, follows ODA principles and has an entry in the TM Forum ODA Component Directory.
Business Source License 1.1: free for internal production use; Enterprise Modules by licence key; each version converts to Apache 2.0 after four years.
EU company; deployment in your infrastructure, sign-in through standard SSO; development, delivery and support under an ISO 9001:2015 quality system.
WideCoup Convergent BSS and MEF.DEV are developed, delivered and supported under an ISO 9001:2015 quality management system; MEF.DEV passed an independent security audit and penetration test.
Certificates and audit →Next for you