Every recording carries verifiable proof of origin — an inaudible mark baked into the audio itself. It survives copying, compression and re-uploading, so the evidence travels with the file wherever it goes.
The mark is embedded in the audio itself — not in metadata that can be stripped away. Wherever the recording goes, and whatever is done to it, the signed proof goes too.
Through every step, verification still resolves to the original signed master. An identifier held only in metadata — like an ISRC — would have been lost at the first re-upload.
Three things Genotone does to a recording — in one clean pass, inside the tools you already use. Nothing about how you work has to change.
{{ s.body }}
Anyone holding the file can check it and get exactly one of these. Genotone tells you what it can prove — and says so plainly when it cannot.
A missing mark is never proof of synthetic origin. Plenty of legitimate recordings carry no mark, simply because they were never registered.
An identifier carried only in metadata can be separated from the audio. A signed, fingerprinted record cannot be quietly rewritten.
Verification happens in three layers — and only one of them asks you to trust a party at all. The result rests on evidence that can be independently re-run.
{{ t.body }}
The short version. Genotone is the neutral registrar and the identity checker — not the sole judge. Because the record format, the signature method and the verification process are open, a broadcaster's own compliance team, a collecting society, or a court-appointed expert can build their own checker and confirm the answer without asking permission.
The verifier is open, so anyone can re-run a check from the command line — against the public registry, with no Genotone account. Here is the whole interaction:
Genotone owns the audio soft-binding layer — the inaudible mark, the recovery engine and the registry. It does not replace the signing infrastructure it rests on; it extends an open standard governed by the Linux Foundation.
The building blocks of the Genotone platform. Names and scope are indicative and on the roadmap toward pilot service.
{{ p.body }}
Verification runs inside your own applications and ingest pipelines — open methods, no lock-in. The right to check is free and independently implementable.
You never pay a toll to check whether a mark and its claim are valid. Any charge sits on registration, scaled to who you are. These figures show the intended shape, being tested with early partners.
Institutional licences cover managed APIs, bulk processing, service levels and support — not the underlying right to check a claim, because that right is open to everyone.
{{ pl.body }}
A working internal prototype already performs the complete chain — registration, marking, fingerprinting, signing and the four verification responses — tested against real catalogue including awkward edge cases.
Subject to the current funding round, the public registry and partner integrations will be built through a focused seven-month programme. This is not a service you can sign up to this afternoon — and that distinction is deliberate.
Genotone asks to be checked, not simply believed.
Join the mailing list for progress on the registry, pilots and open specification — or get in touch about a walkthrough, pilot or verification demonstration.
Request a technical walkthrough, a pilot discussion, or a verification demonstration. We would rather be checked than believed.
Just hit send in your mail app to confirm your message and we'll be in touch shortly.
Genotone is at an early stage. Registration and verification are designed and prototyped; the public registry follows a focused build programme, subject to funding.