For governments, companies and defence: private by design, post-quantum today
Obleevo moves files, messages, voice and screens straight from one browser to another, end-to-end encrypted with a post-quantum layer, and keeps nothing on any server. Organisations that would rather have no stored data and no account database to protect can use it today for lawful work, and we can build the rest with you.
All of this works now, in the version anyone can open at obleevo.com. None of it is a promise.
Nothing stored, anywhere
Files, messages, voice and screens go straight from one browser to another. The server only introduces browsers, keeps rooms in memory and has no database: there is no stored content to steal or sell.
Post-quantum encryption, now
Every pair of browsers runs a hybrid X25519 + ML-KEM-768 (FIPS 203) key exchange on top of WebRTC’s own encryption, so traffic recorded today cannot be opened later by a quantum computer. Keys move forward at least every minute and are renewed every 30 minutes.
Checked on every release
Before each release, the cryptographic code passes all 1,052 official NIST (ACVP) and Wycheproof test vectors, in Node and in Chrome; a hostile-server test suite confirms that a compromised server reads nothing.
In step with Canada’s post-quantum direction
The Canadian Centre for Cyber Security has set out a roadmap for Government of Canada systems to move to post-quantum cryptography, built on the NIST standards, ML-KEM among them. Obleevo already uses ML-KEM. That is the same direction, not a certification: the Cyber Centre has not evaluated Obleevo.
No accounts to provision or leak
No sign-up, no email, no password database. Nothing to set up for staff, nothing to remove when they leave, and no list of accounts to steal.
Works without the internet
No-server mode connects two devices on the same Wi-Fi or a phone hotspot by scanning two QR codes: once Obleevo is open on both, neither the internet nor any server is involved, not even for the introduction.
Made and hosted in Canada
Developed by The House of Brendrof in Canada. The server runs on OVHcloud in Beauharnois, Quebec. When a direct link is impossible, an encrypted relay carries traffic it cannot read: Cloudflare’s first, our own in Beauharnois as backup.
Releases you can verify
Every file of each release is published with its SHA-256 fingerprint, timestamped in the Bitcoin blockchain and checkable from any browser at /verify.html: a quietly changed version would show.
Eight languages, accessibility checked
French and English, plus Spanish, German, Portuguese, Italian, Romanian and Japanese. Automated accessibility tests (axe-core) run on every change, in light and dark themes, at phone and computer widths; testing with people who use assistive technology is still to come.
What it changes for you
Government
Departments, agencies, municipalities and public bodies.
Exchange files with citizens, suppliers and other departments without either side creating an account or uploading anything to a third-party cloud.
No copy on our side: no stored copy for us to secure, retain or purge. Your own record-keeping duties stay yours.
French and English as equals, plus six more languages.
A post-quantum key exchange already in place, in the direction of the Government of Canada’s migration — with no certification claimed.
Law firms, finance, health, engineering, media: anyone handling files that must not leak.
Send files of up to 1 TB (in Chrome and Edge on a computer) straight to a client or colleague: no size plan, no waiting for an upload, no link that outlives the transfer.
Signed delivery receipts: both browsers sign the name, size and SHA-256 of what was delivered, checkable by anyone.
No accounts to manage and no vendor holding your data: our server has nothing of yours to lose.
Calls of up to 20 people with screen sharing, chat and notes, in the same encrypted room.
Defence services, public safety and their suppliers — for unclassified work, and for defence or security services only under a written agreement with us.
No-server mode for the field: two devices, one local Wi-Fi or hotspot, two QR codes — text and files pass with no internet, no server and nobody in the middle.
Resistance to “harvest now, decrypt later”: recorded traffic is protected by ML-KEM-768 as well as X25519.
Eight safety words, or a QR scan in person, prove nobody sits between two devices; a connection that cannot complete the post-quantum exchange is refused, never downgraded.
Burn erases a room from every browser in it; Escape pressed three times is a panic exit.
None of this is in Obleevo today. It is on our roadmap for organisations and gets built with a partner who needs it — ask us.
Self-hosted edition
Obleevo on your own servers and network, introduction server and relay included, with no dependency on ours.
Administration policies
Rules set by your organisation: room size, who may host, file types, relay-only connections.
Organisation identity and device keys
Devices enrolled with keys your organisation issues, so a colleague is recognised without any account on our side.
Classification banners
Markings shown on every room, file and screen, set by your policy.
Watermarked screen sharing
Each viewer’s name drawn across a shared screen, as Obleevo already does for view-once pictures.
Chain of custody
Signed records of who sent and received what, built on the signed delivery receipts Obleevo already makes.
Native apps
Desktop and mobile apps for managed fleets, alongside the browser version.
Where it stops today
Obleevo is not certified, accredited or evaluated for classified networks or classified information, by Canada or anyone else, and must not be used for them today. It runs in an ordinary web browser, on ordinary devices.
The free public service may not be used for the operations of intelligence or secret services, for military operations, or for covert or offensive surveillance of people, unless The House of Brendrof has signed a separate written agreement: for those services, what this page offers starts with that agreement. No agreement covers anything the law forbids. See section 6 of the Terms.
Its cryptography runs in the browser, in JavaScript and WebCrypto: it passes the official test vectors, but it is not a CMVP-validated module, which some purchasing rules require.
Both people must be online at the same time, and there is no webcam video, no delayed sending and no archiving: it is not storage or records management. When a direct link is impossible, an encrypted relay is used; it sees addresses and volume, never content.
If one of your requirements rules it out, we would rather say so in the first email than during the pilot. The public version stays free to use.
How working together goes
01
A first conversation
You tell us what you need to move, between whom and under which rules. We tell you plainly what works today and what does not.
02
A pilot
A limited trial with your team, on your use case, with the version available today or a build made for the pilot.
03
An agreement
Scope, support, hosting and any roadmap work put in writing, once the pilot has shown it is worth it.
Work with us
Tell us who you are, what you need to exchange, with whom and under which rules. Pick the subject that fits: your email app opens with it filled in.