A unique identity per unit
Not one code per batch: one per container, tied to product, batch and territory. The serial number is obfuscated, so two consecutive labels look nothing alike and nobody can guess the next one.
Product authentication
Every product has a story.
Make sure it's yours.
XYVONA gives every physical unit a unique digital identity, so you can verify authenticity, follow distribution and talk to your buyer at the moment they scan.
Protecting physical products across pharma, beauty, beverages and consumer goods.
How it works
Three steps. One label.
Nothing changes in your production line or your packaging. What changes is what you know about every unit once it leaves your warehouse.
- 01
Order your labels
Tell us how many units you need. We generate the codes, send them to print and deliver the rolls. Every label is born with a unique identity, already registered.
- 02
Apply them to your product
They go on during packaging, with no change to your line. Only when you activate the roll do those units start authenticating: a label stolen from the warehouse verifies nothing.
- 03
See what happens out there
Every buyer scan tells you where your product is, whether it is genuine and when it was first scanned. No app: the QR opens a page in the phone browser.
Protection
Four layers that hold each other up
A single layer can be copied. Together, copying a label is not enough: the counterfeiter would also need our key, and that key never leaves the cryptographic module.
A signature verified on the server
Every code carries a cryptographic signature. A made-up code is rejected without ever touching the database, and copying a real label does not create a new unit: it creates a second scan of the same one, which is exactly what gets detected.
Behavioural detection
Eleven rules watching scan velocity, geographic clustering, device diversity and datacenter networks. A batch showing up in two countries at once raises an alert with its evidence attached.
Real-time intelligence
Heat map, territory diversion alerts, case management and webhooks into your team. The data is yours and exports whenever you want.
What's included
What the platform does
This is not a roadmap: it is what is running, and what you will use from your first batch.
Public verification
The page behind the QR weighs under 30 KB and works on an old phone with one bar of signal. It never tells a buyer "counterfeit": a code that fails returns “we could not verify this”, and the suspicion lands in your inbox with the evidence.
Activation on the floor
By range, by roll or by unit, from the panel. A unit that is not activated never authenticates, and that is the rule that makes a stolen roll worthless.
Batch recall
Flag the batch and the next scan of any of its units shows the safety notice instead of “verified product”. In seconds, with nothing reprinted.
Roll chain of custody
Every roll has a state —ordered, printed, shipped, received, consumed— and can be declared stolen in one move. All of its units stop authenticating immediately.
Hash-chained audit log
Every sensitive operation lands in an append-only log linked by hash. It is what a pharmaceutical auditor asks for to prove the history was not edited afterwards.
Isolation between brands
Each customer sees only their own data, and not because the application filters it: the database enforces it. A programming error cannot cross two brands.
Industries
Where counterfeiting hurts
- Pharmaceutical
- Cosmetics & beauty
- Beverages & spirits
- Nutraceuticals
- Agrochemicals
- Consumer goods
In pharma the buyer portal ships off and cannot be switched on: storing which medicines an identified person scanned is health data, and that responsibility is not something to pass along.
Shall we start with one batch?
The fastest way to evaluate this is with real product: a small batch, our labels, and the panel with your own data in it.