Zero-knowledge proofs
on ordinary phones
Prove a statement about the facts kept sealed in your phone's security hardware, and whoever asks learns one thing: that the statement is true. Two answers you give to two different services cannot be connected to each other.
Credentials: prove what your ID document says about you, such as being of age, while the document, your name and your birth date stay secure on your phone.
Products
We develop zero-knowledge solutions for our clients. Our current products:
Proving engine
General-purpose R1CS proving on consumer smartphones, with a classical and a hash-based post-quantum backend. Proving runs in 20–40 MB of memory.
Verifier
Verification services for relying parties over HTTP and TCP, with a credential registry. Verification takes a few milliseconds and requires no storage on the relying party's side.
Transport
Proof delivery over size-constrained channels: HTTP headers, NFC, QR.
Wallet
Reads and verifies an eID document's chip on the device (ICAO 9303), stores the credential under the phone's secure hardware, and presents yes/no proofs. The same wallet model works for driving licences, prescriptions, diplomas, tickets and memberships.
Everything works with the credentials governments already issue. There is no trusted setup ceremony and no new cryptographic assumption anywhere in the stack.
How it works
Enroll once
The document is read and verified once, including its chip. The credential is then stored encrypted under the phone's secure hardware and never leaves the device.
Prove in seconds
When a service asks a question, the phone computes a proof for that question alone. The service receives the answer and nothing else.
Verify anywhere
The service verifies the proof on its own servers in a few milliseconds. No call to us is involved, and there is nothing the service needs to keep afterwards.
The credential is protected by the phone's secure element rather than by the operating system, so it stays protected even on a rooted or otherwise compromised phone.
Why it's different
No stored data
Credentials exist only on users' phones. A service that never receives personal data cannot leak it - and neither can we.
Built for real phones
Zero-knowledge provers normally assume server hardware. Ours was built for the memory limits phones actually enforce, which is why it runs on a six-year-old mid-range Android and not only on flagships.
Algorithm agility
Proofs carry a cipher-suite tag, so the cryptography can be upgraded without breaking existing verifiers. A post-quantum mode is implemented.
Security testing
We write exploits against our own engine before anyone else can. Each one that worked was fixed and then kept in the test suite as a permanent regression check.
Who it's for
Relying parties
Age and credential checks that hold up both under the regulator who requires them and under the one who audits your data handling.
Wallet builders & issuers
An embeddable engine that adds unlinkable, selective presentation to credentials you already issue.
Regulators & auditors
The construction is open, the assumptions are standard, and the performance numbers are measured. The security model is written down so it can be evaluated.
Status
The engine runs today on real hardware. A priority patent application was filed in August 2026. Tetri Systems is a Swedish company and is independently funded.
We are starting pilots with relying parties, wallets and issuers.
Contact
Tetri Systems AB · Sweden
Technical conversations under NDA welcome.