Data anonymisation platform · four independent modules
Kubli is a four-module platform that anonymises archives, flows and logs for regulated industries, and measures re-identification risk on every result.
Where it's used
Banking
Insurance
Healthcare
Marketplaces
Public sector
Telecom
Utilities
The product at work
Kubli Echo produces a usable copy of your archives and measures its re-identification risk with the three attacks the EDPB names: singling out an individual, linking them to another dataset, inferring an attribute. Above the threshold, the file is not released.
An ordinary row from a customer database. On the left as it sits in your systems, on the right as it appears in the released file.
Product, spend and outcome stay intact: they are the reason anyone wants that file. The customer id changes, but it changes the same way in every table, so the queries you already wrote keep working.
EchoIn 2024 the European regulator made clear that two datasets looking alike prove nothing about anonymity: you have to show that nobody can be traced. Echo shows it, and the answer is a number.
CompassEurope's new rules on artificial intelligence treat automated decisions about people as high risk. In practice that means you will have to show how the system works, not merely that it works.
Usable archives, measured risk
Anonymise your archives without making them useless.
Discover EchoAnomalies caught as they happen
Catches anomalies while the flow is running.
Discover PulseDocumented automated decisions
Documents the decisions as the system makes them.
Discover CompassUsable logs, anomalies surfaced
Makes your logs usable and surfaces only the anomaly.
Discover SentinelHow it reaches you
Kubli adds to your existing software instead of replacing it. Switch on the modules you need and the others do not run. You can start with one.
Point it at your sources
Tell it where the data lives. Nothing is moved or copied elsewhere: the agent goes to the data.
Switch on one module
Only the one you need. The other three do not run, take up no resources, and are not on your invoice.
Verify it on your own case
Before production the measurements are taken against your real data. If the result does not hold, you find out at that point.
It sits alongside your existing systems. No migration, no rewriting, no changing supplier for what already works.
One executable, nothing to install, no graphics card. It reads sources in blocks, so memory does not grow along with the volume of data.
The heavy work happens to the side, not inside your calls. Where an immediate answer is needed, like a movement to approve, the decision arrives on the spot without adding time for the customer.
The four modules are independent. If your problem is archives, start with Echo. If it is anomalies in your flows, start with Pulse.
On our infrastructure or inside your own network, your choice on Team and Enterprise. In the second case the rows never cross the perimeter: counts and agent status do.
Alongside the outcome comes the document reporting how it was obtained and what that measurement does not cover.
Technical specifications, architecture and an integration estimate for your case sit in the confidential documentation, which you can request below.
Two routes
If you have a problem to solve, start with a demo on your own case. If you are assessing us, as a fund or a procurement team, start with the confidential documentation.
Kubli issues no certifications and holds none. It hands over the measurements taken and the documents to stand behind them when someone asks.
Thirty minutes. You tell us which data is blocked and what you would do with it, and we show you the result on an example close to yours. If the case is not a fit we say so on the call.