Kenmei
Kenmei is a Spanish software platform for mobile network operators. It unifies multi-vendor network data into a single telco data layer, then applies AI agents that detect anomalies, diagnose root causes and recommend actions automatically.
What is Kenmei?
Kenmei is a network intelligence and automation platform for mobile operators, published by Kenmei Technologies SL, a company registered in Paterna, near Valencia, Spain. Its stated purpose is to turn the raw data a mobile network already generates into decisions and actions, rather than into more dashboards.
The offering is presented as four connected building blocks. The Telco Fabric is a telecom-specific data layer: it ingests OSS records, call traces, user equipment data, alarms and configurations in streaming or batch mode, decodes proprietary telco formats into open ones such as Parquet, enriches them with time and geography, and exposes a common data model. Kenmei claims processing up to five times faster than a generic ETL thanks to a C++ core and a Spark engine, and more than three times the return on ingestion because the same data feeds several use cases.
On top of it sits the Agentic Network Platform, a set of goal-oriented AI agents coordinated by an orchestrator. One agent analyses performance deviations, another troubleshoots root causes, others address planning, capacity or user experience. The company is explicit that the agents act within limits the operator sets and are meant to multiply an engineering team rather than replace it.
Three packaged AI Products build on the same fabric: Anomalies, for detecting degradations before customers notice; Geolocation, which turns real user activity across roads, cities and railways into coverage insight and reduces reliance on drive testing; and Interference, which detects, classifies and locates radio interference. A Professional Services team completes the range, covering deployment, diagnostics, planning, integration and training.
Compatibility is claimed across all major vendors and radio technologies from 2G to 5G, with deployment either in the operator's own cloud or on-premise. Kenmei has joined the Ericsson Intelligent Automation Platform ecosystem as an rApp provider and announced a collaboration with Microsoft built on Azure, Fabric and Foundry. Telefónica, MASOrange, Ooredoo, Zain and Etisalat are named as customers, and case studies cover Moldtelecom, MASOrange and Telefónica. The product is sold entirely through a sales conversation: no price, plan or trial is published.
What it does
- Unify OSS, trace, alarm, configuration and crowd-sourced data from every vendor into one queryable layer
- Detect network anomalies and surface the degradations that affect customers first
- Diagnose root causes automatically instead of correlating dashboards by hand
- Recommend and trigger next actions within boundaries the operator defines
- Produce large-scale geolocated coverage and quality insight from real user activity
- Detect, classify and locate radio interference
- Decode 3GPP signalling to shorten trace-file troubleshooting
When to use Kenmei / When not to
A quick filter to help you decide if Kenmei is the right fit.
When to use Kenmei
- Mobile network operators and communication service providers running multi-vendor estates from 2G to 5G
- Network operations centre teams who spend hours correlating KPIs across separate vendor tools
- Radio planning and optimisation engineers who need coverage and quality insight without drive testing
- Network data and platform engineers tasked with consolidating OSS, trace and crowd-sourced data
- Operators already invested in the Ericsson or Microsoft ecosystems who want automation that plugs into them
When not to use Kenmei
- Individuals and small businesses: there is no self-service sign-up, no published price and no trial
- Teams outside mobile telecoms, since the algorithms are stated to be built specifically for RAN, Core and Transport
- Buyers who need to compare costs before talking to a vendor, as no pricing is published anywhere
- Developers looking for a public API to build on, because no API documentation is published or reachable
- Organisations that require a published security certification such as ISO 27001 or SOC 2 before procurement
How to use Kenmei
A typical end-to-end flow, from setup to results.
- Identify which building block matches the problem: the Telco Fabric for fragmented data, AI Agents for automated diagnosis, or one of the packaged AI Products
- Read the relevant solution page, since each block is documented separately and no single overview page exists
- Submit the contact form, the only entry point on the site, giving name, company, work email, job title and the problem to solve
- Discuss scope with the sales and engineering team, as pricing and packaging are agreed case by case
- Agree a deployment target: the operator's own cloud, or on-premise inside the operator's perimeter
- Connect the data sources the Telco Fabric will ingest, such as OSS, traces, user equipment data, alarms and configurations
- Let the fabric decode, enrich and correlate that data into the common model
- Enable the AI agents or packaged products relevant to the chosen use cases
- Define the boundaries within which agents are allowed to act before they recommend or trigger anything
- Engage Professional Services if internal capacity is short, as Kenmei positions them explicitly to accelerate deployment
Pros & Cons
Pros
- A shared data layer that several use cases reuse, which Kenmei quantifies as more than three times the return on ingestion
- Algorithms stated to be developed in-house for RAN, Core and Transport rather than adapted from generic AI
- Deployment inside the customer's own cloud or on-premise, so operator data stays within its perimeter
- Named Tier-1 references including Telefónica, MASOrange, Ooredoo, Zain and Etisalat, with three published case studies
- Integration into the Ericsson Intelligent Automation Platform ecosystem and a stated Microsoft collaboration
- A clear architectural story in which data unification, intelligence and action are separate, documented layers
- Long-standing telecom specialisation, with the company registered since 2018 and more than eighty staff announced in 2024
Cons
- No pricing whatsoever is published: there is no pricing page, no plan and no indicative range
- No free trial, no free plan and no self-service sign-up; every path leads to a sales conversation
- No public API documentation, and no developer or documentation subdomain responds
- No security certification is claimed or published, which enterprise procurement usually requires
- The privacy policy covers only the website, so nothing contractual is published about operator network data
- Subprocessors are described by category only, never named
- The site is available in English only, despite a customer base across Europe, the Middle East and Asia
Pricing & Plans
Kenmei publishes no pricing information of any kind. There is no pricing page on the site, no plan is described with a figure, and no amount appears anywhere in the collected pages. No free plan and no free trial are announced. Commercial terms are agreed through a sales conversation, which the site invites via a single contact form.
- the multi-vendor telco data layer
- sold without a published price
- the AI agents layer
- sold without a published price
- Anomalies
- Geolocation and Interference
- sold without a published price
- deployment
- diagnostics
- planning
- integration and training
- sold without a published price
Data, GDPR & hosting
A consolidated view of how Kenmei handles your data.
GDPR overview
GDPR implementation is documented for the website. The privacy policy, last updated on 16 May 2025, is built explicitly on Regulation (EU) 2016/679 and lists the full set of data subject rights: information, access, rectification, erasure, withdrawal of consent, objection, portability, restriction and cookie control. Rights are exercised by writing to the Paterna office or emailing the company with the subject line "GDPR Valencia", and the Spanish supervisory authority (AEPD) is named with its address and telephone. The policy states that no international transfers outside the European Union take place. No data protection officer is designated and no Article 27 representative is named, which is consistent with an EU-established company. On the product side, the Telco Fabric page describes the data layer as fully GDPR-ready; the site never uses the words "GDPR compliant".
Who owns the data?
The published privacy policy names KENMEI TECHNOLOGIES SL as data controller, but it covers only the website and the company's social media presence. It says nothing about ownership of the network data an operator would process on the platform. For the product itself, the only public statement is architectural: Kenmei says deployments run in the customer's own cloud or on-premise and that data never leaves the customer's perimeter, with personally identifiable information anonymised or obfuscated and access restricted through role-based controls, IAM and VPN. Ownership of operator data is therefore left to the individual contract, which is not published.
Reuse rights
For the website, the policy limits processing to answering enquiries, delivering downloaded content and sending commercial communications, on the basis of consent, pre-contractual measures or legitimate interest. It states that no international transfers outside the European Union are carried out. Nothing published grants or restricts an end user's right to reuse data produced by the platform, and no terms of service covering the product are available. The legal notice governs use of the website only, and reserves all intellectual and industrial property in the site's content to the company. Anyone needing to know what they may do with platform outputs has to obtain the commercial contract.
Data retention & training
Hosting summary
Kenmei names no hosting country and no hosting region for its platform. The published model is that the customer chooses: deployments run in the operator's own cloud or on-premise, and the company states that data never leaves the customer's perimeter. Security measures described for the Telco Fabric include encryption at rest and in transit, anonymisation or obfuscation of personally identifiable information, and fine-grained access control through role-based permissions, IAM and VPN. A separate statement exists but has a narrower scope. The website privacy policy, which covers the site and the company's social media presence rather than the platform, states that no international transfers of personal data outside the European Union are carried out. It identifies recipients only by category - a newsletter and email marketing provider, hosting providers and an IT and web design consultancy - and names none of them. The March 2026 Microsoft collaboration states that Kenmei's solutions are built on Azure, Fabric and Foundry, but gives no region. Anyone needing a jurisdiction guarantee will have to obtain it contractually.
Things to keep in mind
Risks and trade-offs to weigh before adopting Kenmei.
- No published price, plan or trial: the total cost of ownership cannot be estimated before entering a sales process
- The privacy policy covers only the website, so no published document states how operator network data is handled, retained or protected
- No security certification is claimed or published; the site describes a management system but names no certificate, body or validity date
- Automated agents that recommend and trigger network actions can erode an engineering team's own diagnostic skill if their reasoning is not reviewed
- Subprocessors are named only by category, which makes an independent supply chain assessment impossible from public information
- A 2024 press release describes the platform under a former name, so older third-party sources may not describe today's product
- The site publishes an unedited template block on its case studies page, a reminder to verify claims directly rather than assume every page is final
Setup & Integrations
Technical difficulty
High, and unavoidably so. Setting Kenmei up means connecting operator-scale data sources - OSS records, call traces, user equipment data, alarms and configurations - into a fabric deployed either in the operator's own cloud or on-premise. That is an infrastructure project, not a sign-up. Kenmei sells Professional Services explicitly to accelerate deployment and close the skills gap, which is itself an indication of the effort involved. The lightest documented path is for operators already running Ericsson infrastructure, where Kenmei ships as an rApp and states that no extra integration is needed.
Integrations
Supported languages
Behind Kenmei
Fundraising
Social
Resources
All the official URLs gathered for verification and reference.
Frequently asked questions
Who is Kenmei built for?
What does the Telco Fabric actually do?
What do the AI agents do?
Which packaged products are available?
Where is the data hosted?
How much does Kenmei cost?
Does Kenmei offer a public API?
Does Kenmei hold security certifications?
What integrations does Kenmei announce?
Who publishes Kenmei?
Should you pick Kenmei?
Kenmei is a focused, credible enterprise product rather than a tool anyone can pick up. Its argument is coherent: mobile operators already hold the data they need, but it is trapped in vendor silos, so Kenmei unifies it once in a telco-specific fabric and then lets AI agents act on it. The separation between the data layer, the intelligence layer and the agents is clearly explained, and the packaged products for anomalies, geolocation and interference show what that architecture is meant to deliver in practice.
The supporting evidence is unusually concrete for a company of this size. Named Tier-1 customers, three published case studies, membership of the Ericsson automation ecosystem, a stated Microsoft collaboration and a documented funding history all point to a real deployment base. The Spanish commercial register confirms an entity registered since April 2018, with investors that include an operator and a public regional fund.
What a reader should weigh is how little is published about the commercial and contractual side. There is no price, no plan, no trial and no self-service path of any kind. No API documentation exists. No security certification is claimed, which is notable for a vendor selling into carrier infrastructure, and the privacy policy explicitly covers only the website, so nothing published binds the company on how operator network data is handled. Subprocessors are described by category rather than named.
None of that makes the product weak; it makes it opaque from the outside. Kenmei is worth a conversation for an operator with fragmented network data and a genuine automation mandate, and that conversation is where all the questions this site leaves open will have to be answered.
- Choosing a selection results in a full page refresh.
- Opens in a new window.