Every meeting,
searchable.
Even we can't read it.

Conclave is your team's confidential memory — captured, searchable, and reasoned over, built so the operator stays blind to your data.

scroll ↓ to reveal
01The system · three planes, one boundary

Three cooperating products behind a single trust boundary.

MEETINGCAPTUREwho spoke whenONE BOUNDARY{ start, end, spk }CONCLAVEcontent · intelligenceTDXVFTEwho is it · consented+ identity
01

Conclave

Intelligence + control plane

The TEE where content lives — transcripts, insights, knowledge base, audio.

02

Capture

Meeting capture + diarization

Joins online meetings or streams a room mic. Identity-free by design.

03

VFTE

Voice identity + consent

Voiceprints, recognized only scoped and consented. A voice you own.

02The moat

Access is not
privacy.

Logins decide who gets in; only encryption and a TEE decide what the vendor can read. Confidentiality is end-to-end or it's a lie — so Conclave owns capture and enforces consent at the microphone.

  • LLM only at ingest
    the read path is pure SQL — no model call, no egress
  • Sealed keys
    TEE-sealed via dstack; they exist only inside the enclave
  • TDX attestation
    every service proves which code is running
  • Ed25519 receipts
    deletions are signed and offline-verifiable
operator can readoperator-blindsingle meetingteam memoryOtter · FirefliesGranolaGlean · NotionRewind · memConclave

team memory that's operator-blind