Early access Now inviting design partners

Private conversations,
 built into your app.

Mirage adds chat and video calls to your product that only the people talking can read. Every message is locked on one device and opened on the other. In between it passes through a server you run, and that server can't open it either.

Become a design partner Try the lock yourself

For clinics, law firms, remote operations, and anyone building a product where a leaked conversation is a disaster.

A message travels, locked, from a clinic app to a patient app A doctor writes "Your results look great!". The message is sealed in a locked envelope, passes through the clinic's own server, which only sees scrambled characters, and is unlocked on the patient's screen. CLINIC APP Your results look great! PATIENT APP Your results look great! WHAT YOUR SERVER SEES 9f 3a c1 7e 0b d4 e2 58 … YOUR SERVER
The problem

Most apps send your conversations through someone else's computers.

Chat and video usually come from a big cloud provider. It works, but every consultation, every contract discussion and every confidential call now passes through a company you don't control, in a country you didn't choose.

The usual way SOMEONE ELSE'S CLOUD

They carry it, and they can read it.

Your users' private words sit on a provider's servers, readable by the provider and by anyone who breaks in or asks with a court order.

With Mirage YOUR OWN SERVER

You carry it, and nobody can read it.

Conversations travel as sealed envelopes through a small server in your own infrastructure. It delivers them, but it has no key to open them.

Try it

Type a secret. See what the server sees.

This box runs real encryption in your browser. What you type is locked, sent through an imaginary server, and unlocked on the other side. Nothing leaves this page.

You write, and it's locked

Meet me at 3pm, room 12

The server only sees this

a4 1f 9c 0e 7b 33 d2 88 5a c0 e1 49 2f b7 06 de 91 7c 3e aa 50 14 cb 62 f8 0d 97 4b e3 21 b8 5c 76 09 ad 13 fe 42 88 c5
No key, no idea.

They open it and read

Meet me at 3pm, room 12

Type the same words twice and the scrambled version still comes out different, because every message gets a fresh lock. The demo uses AES-256-GCM through your browser's own crypto; Mirage uses the same family of locks, with keys that never leave the device.

How it works

Four simple ideas, doing all the heavy lifting.

Every device makes its own key

The key is created on the device and never sent to any server. No server-side passwords to leak, no phone numbers to collect.

Each message gets a brand-new lock

Locks change with every message. Even if one were ever picked, yesterday's messages stay sealed.

Your server carries sealed boxes

It helps devices find each other and holds messages for people who are offline, without any way to look inside.

Only the recipient can open it

The matching key lives on their device alone. The words, voice and video appear there and nowhere else.

Who it's for

Built for conversations that can't afford to leak.

Clinics and therapy apps

Video visits and patient chat where medical details never touch a third-party cloud, and your server can sit in the country your health-data rules require.

Lawyers, advisors and notaries

Client conversations stay privileged: case details, contracts and identity checks are seen only by the people in the room.

Remote sites and operations

An engineer on a rig, a mine or a wind farm talks to an expert on shore over a link your company owns from end to end.

Companies building secure communication

Add encrypted chat and calls to your own product under your own brand, without spending years writing and maintaining the cryptography yourself.

Getting started

It snaps into what you already have.

No new app for your users to install, and no new vendor holding their data. Your team adds one library and runs one small server.

YOUR APP Mirage Engine ONE LIBRARY YOUR SERVER, YOUR CLOUD
1. Add the libraryA native library for Windows, macOS and Linux. No browser tricks and no third-party accounts.
2. Start your serverOne small container in your own data centre or cloud, in the country you choose.
3. Connect your peopleYour app decides who talks to whom. Mirage makes sure nobody else can listen.

Engineers: the protocol, threat model and integration details are on the technical page.

In numbers

Small promises we can actually keep.

0messages your server can read. It only ever holds sealed envelopes.
3desktop platforms today: Windows, macOS and Linux.
1small container to run your own server.
2,800+automated tests checking the engine, the server and the app.
Honest status

What works today, and what's coming.

We'd rather tell you now than have you find out in a pilot.

Ready now

  • Private one-to-one messages
  • One-to-one voice and video calls
  • Messages wait for people who are offlineHeld on your server for up to a day, still sealed.
  • Your own server in one container
  • Windows, macOS and LinuxA working desktop messenger is built on it, in closed alpha.

Coming next

  • Group chatsBuilt on MLS, the new internet standard for group encryption.
  • Group callsSmall groups are in testing; larger rooms come after.
  • iPhone and Android
  • Admin controlsWho may join your server, and removing access when someone leaves.
  • Independent security auditNot done yet. We will publish the result when it is.

Mirage is in early access. Features and timelines may change, and design partners help decide what comes first.

Be one of the first to build with it.

We're opening Mirage Engine to a small group of design partners. Bring a real product and a real problem, and we'll build the first integration together.

  • Early access, before anyone else
  • A direct line to the people who build it
  • A real say in what we build next
  • Hands-on help with your first integration
Apply as a design partner

Or just say hello: hello@miragetalk.com