Big conversations.
A smaller circle.
A private place for the people moving your institution forward. Meet with end-to-end encrypted calls and control over who gets in.
An end-to-end encrypted connection.
Your invitation.
Your way in.
Have a meeting link? Check your camera and microphone, then get ready to join your people.
Built around
your ground rules.
A good meeting starts with knowing who’s in the room — and who’s in control of it.
Your conversation stays in the circle.
New calls use a browser-generated key. Protected audio, video, screen sharing and live chat are decrypted on participant devices. The media server receives encrypted call content.
Share the complete protected invitation privately. The keys stay with your people.
An invitation opens the door. You decide who enters.
Choose institution members, use a private guest list, and admit invited guests through a host-controlled waiting room. Everyone checks their camera and microphone before joining.
A deliberate guest list. A clear moment of admission. A room under your control.
Your institution, through and through.
Your name, your domain, your administrators. A dedicated environment keeps each institution’s database, files, media services and credentials separate.
Each institution is deployed independently, with its own branding and access policies.
Your own address.
Privacy deserves
a straight answer.
Clear boundaries are part of the promise. Here’s what protected meetings mean in practice.
What stays between participants?
Protected audio, video, screen sharing and ephemeral live chat use end-to-end encryption. Compare the meeting verification code with people you trust. Share the complete protected invitation privately; a lost key cannot be recovered by an administrator.
Can a protected meeting be recorded?
Protected meetings disable server recording and stored call chat. Participants can still record their own devices. Meetings that support server recording use transport encryption instead; existing meetings retain their original encryption mode.
What can the service still access?
Accounts, attendance and connection metadata remain visible to the service. Workspace messages and files use server-side encryption and can be decrypted by authorized infrastructure operators. Administrators have no ambient access to private workspace conversations.
How are institutions kept separate?
Each institution runs in a dedicated deployment with its own database, storage, media services and secrets. Its administrators manage its people and policies. Onboarding prepares a deployment plan; a separate server and domain setup are required to bring it online.
Make room for
what matters.
Your people. Your institution.
A place to move things forward.