When the network is gone, the meeting still happens.
Lucid Meeting Hub records and understands a meeting from the machines already in it, no bot, no cloud tenant, no server, using models small enough to run on the laptop you were actually issued. It keeps working when the link degrades, when the enclave has no route out, and when the server your organisation runs goes down.
01 Why this, why now
Four sentences we have each heard, and none of them is a missing chat feature.
“I can't run Teams on the FOB.”
No route to the tenant, and a link that will not carry a modern client even when there is one. A platform that assumes a fat pipe to somebody else's cloud has no answer, and “use it degraded” is not an answer when the degraded mode still needs the cloud.
“I have Teams, but I'm not allowed to join a Zoom meeting.”
Blocked by policy, not by technology. The client is right there and the answer is still no, so the work moves to email, a personal device, or a shadow tenant, and the record of it is lost to everyone.
“How do I work with you if your org is on Teams and mine is on Slack?”
Two organisations that both bought good tools cannot talk, because the tools are destinations rather than protocols. Coalition and joint work hits this on day one.
“The decision was made on a call nobody can find.”
The transcript nobody searches, the recording nobody watches, and a staff that re-litigates a settled question a week later. The record exists and it is useless.
02 Try it yourself
Take a code. Join a meeting from your own phone or laptop.
Nothing installs, nothing needs admin rights, and nothing is written to your machine. It is the honest test of the guest story: if you can join a meeting from a locked-down device you do not control, so can the person you are trying to reach.
Ask for a code
The host generates a single-use code in the desktop app and reads it out. It carries no identity and expires with the meeting.
Open the join page
Any browser, any device, the one in your pocket is fine. No app store, no download, no install prompt.
Sound check
Pick your microphone and watch your own level. Your audio stays in your browser until you unmute in the room.
Be in the meeting
Roster, live transcript, consent state, mute and leave. When you leave, the browser has kept nothing.
Prototype, stated plainly. In this build your microphone is genuinely live in the browser, the level you see is you, and the far side is simulated, because the rendezvous service that would carry media between a host and a guest browser is designed and not yet built. A guest also has no vault: keeping a copy of the record on a borrowed machine waits on the portable vault. We are showing you the shape of the thing, with the missing parts named.
The desktop app
Capture, transcription, decisions, search, vault and serverless sync, the thing in Film 1, running offline on a CPU-only machine. This is what a host runs.
The web guest client
Install-free join for the person who cannot install: media only, single-use code, no identity, no record, announced like any other participant.
The portable vault
Until a vault can travel safely to a borrowed machine, a guest leaves with nothing. We would rather say that than quietly copy a record onto a device we know nothing about.
03 Two films
One is the product running. One is the argument for what comes next.
Film 1 is a screen recording of the application on an offline machine, filled with invented meetings. Film 2 is proposed capability and is watermarked as such for its whole runtime, including the part where the organisation's own server dies and the conversation does not.
Short cuts
04 In the fight
What the military version has to do that a commercial one never does.
Same codebase, different deployment shape. These are the requirements that only exist on this side of the house, and they are the reason the architecture looks the way it does rather than being a cloud product with a government logo on it.
Denied and DDIL as a mode
LAN-only operation with no internet, a signed record that can travel on removable media, and a session that forms directly between peers because there is nothing to call home to.
Degrade honestly on a bad link
Video is shed to protect audio, the quality in force is named on screen, and a call that cannot carry video is still a working call rather than a frozen one.
Enclave deployment, zero egress
One signed binary inside your accreditation boundary carrying rendezvous, relay, group media, directory and audit, with no path out of the enclave at all.
FIPS and the crypto suite
Today's key agreement has no validation path, so an enclave build needs a deliberate suite change and a validated module. Named here rather than papered over on a slide.
CAC/PIV and org-issued device certs
Identity is a device keypair; the card and your CA are how a device gets enrolled and revoked. We want to hear what your enrolment reality actually looks like.
Runs on the hardware you have
A plain CPU is the floor and it is supported, not tolerated. Where the machine has a discrete card, integrated graphics or an NPU, which most laptops fielded now do, it is used, and transcription moves from slower-than-real-time to faster than the meeting.
Coalition and cross-organisation
A partner on a different platform joins one conversation without either side migrating, and every message keeps the platform and author it came from.
The acceptance test for native calling is literally “the same call works with the relay stopped.”
Your organisation can run a Lucid node for the control it buys, directory, revocation, retention, legal hold, audit on your own metal. What it can never buy is permission to talk: when the node is unreachable, the peers that can see each other keep going, and the record reconciles when it returns.
No shared fate with the infrastructure05 In garrison, and in industry
The same product earns its place on a normal Tuesday.
A capability that only pays off in a denied environment gets bought once and never used. This one is load-bearing in garrison, at a program office, and inside the defence industrial base, which is also how it gets enough usage to be trustworthy when it matters.
No bot in anyone's call
Record the meeting you are already in, Teams, Zoom, Meet, in person, without a third party joining, without tenant permission, and without your audio leaving the machine.
Decisions that survive the week
Decisions, owners and dates extracted from the transcript and searchable months later, instead of a recording nobody opens.
Works on the laptop you were issued
CPU-only, offline-capable, no account. The configuration most staff actually have is the supported one, and where the machine has a GPU, integrated graphics or an NPU, it uses it and everything gets faster.
The full commercial case, contractor CUI handling, client confidentiality, cost control against per-seat AI pricing, is on the main site's segment comparison.
06 What we actually want from this show
Not a purchase order. A constraint we have not accounted for.
Tell us the blocker
The policy, the network, the accreditation gate or the device restriction that stops you collaborating today. That is worth more to us than a feature request.
Take the build
Insider testers get the current Windows build and a direct line to the two of us. We want it used somewhere awkward.
Argue with the roadmap
Everything marked proposed is still moveable. If we have sequenced it wrong for how you operate, say so while it is still cheap to change.
Come and break it.
Join a meeting from your own phone, watch the server die mid-film, and tell us which of your constraints we have not accounted for.