Meet-Encrypt

The Brief

Some conversations can't leak. A board deciding on an acquisition, lawyers discussing a case, M&A advisors on a deal — the meeting itself is confidential, and the tools most teams reach for weren't built for that. Mainstream video calls run through someone else's cloud, rooms stay open long after the meeting ends, and "who could have joined" is rarely a question anyone can answer with certainty. Meet-Encrypt started from a simple premise: a meeting should be as private, and as precisely bounded in time, as the room it replaces.

• Confidential conversations running on platforms where the provider — not you — controls the data
• Meeting rooms that stay joinable indefinitely, long before and long after the actual meeting
• No account-free way for outside guests to join without friction or a lingering data trail
• Trust, precision, time and privacy treated as features to bolt on — not as the foundation

A Vault Timed to Open

The idea at the center of Meet-Encrypt is time. A room isn't simply on or off — it's sealed until its scheduled start and sealed again the moment it ends. Access is governed by a cryptographically signed time window: a JWT whose not-before and expiry define exactly when the door opens and closes. Outside that window there is no room to join. Inside it, the meeting unlocks. The mental model is a bank vault on a timer — it opens at the appointed moment and re-seals itself, no manual locking required.

That single decision shapes everything else. Guests join through a signed, time-bound link — no account, no sign-up, no lingering credentials — while organizers sit behind a login. Privacy runs end-to-end through the platform's own custom encryption, engineered for it rather than pulled off a shelf, so the meeting content stays between participants and no provider can read it. And because the whole platform is self-hosted, the data never leaves infrastructure you control.

What We Built

A security-first meeting platform designed for browsers first and confidential use throughout — every capability below follows from the same principle: the meeting should be readable only to the people in it, joinable only when it should be, and hosted only where the client controls it:

The Result

A working, self-hosted meeting platform built for contexts where privacy and timing are non-negotiable:

• Time-bound rooms: meetings that unlock at their signed start and re-seal at the end, so a room is only ever joinable when it should be
• Private by default: custom end-to-end encryption on a self-hosted stack you fully control — no provider ever in a position to read the room
• Frictionless for guests: outside participants join via a signed link with no account, while organizers stay behind login — installable as a PWA with push reminders, no native app
• Notes that never leave: Abby, the built-in AI note-taker, turns each meeting into a summary, action items and decisions, routes them to the right project and emails them when the call ends — all inside the encrypted, self-hosted environment, so nothing ships to a third party

It runs single-tenant today, deliberately architected so it can grow into a productised, multi-tenant SaaS later — organizations are already modelled through Better-Auth. The platform you see is built for one confidential context now, and to become a product for many.

Why This Matters

For lawyers, board members and M&A advisors, a video call isn't a commodity — it's a room where trust, precision, time and privacy all have to hold at once. Most tools optimise for reach; Meet-Encrypt optimises for the opposite. It even brings its own AI note-taker, Abby, so the summary, action items and decisions are captured automatically — yet, unlike cloud note-takers that ship your audio to a third party, Abby runs inside the encrypted, self-hosted environment and the notes never leave your control. A meeting that only exists inside its signed window, that no provider can read, that leaves no data on someone else's servers, and that a guest can still join in one click — that's what security-first looks like when it's built in from the first line, not bolted on at the end.