Teams that bolted Zoom onto a governed stack.
A consumer video app next to compliant email and files adds a second vendor, a second data boundary, and a compliance gap no one owns. MEETINGS runs inside the boundary you already document.
Product 05 · IRONKEEP MEETINGS
MEETINGS is the audio and video layer of the IRONKEEP suite: calls, screen shares, and meeting chat inside one authorization boundary, with meeting actions logged for assessor review.
Private beta · Q2 2026
Receive product updates and the CMMC Level 2 readiness checklist.
What's inside
Audio, video, and screen share for regulated teams.
Join from calendar or chat
Start or join a call from a calendar event in IRONKEEP MAIL or a channel or DM in IRONKEEP CHAT. No second app to deploy and no second vendor to assess.
Audio, video, and screen share
Full meeting controls with host, presenter, and attendee roles, plus waiting room, raise hand, reactions, spotlight, and in-meeting chat.
External guests, no accounts
Guests join scheduled calendar meetings by invitation only, with domain allowlists and expiring links.
Pre-join device check
Check camera, microphone, and speakers before joining, with background blur.
Encrypted cloud recording
Recordings write to encrypted, tenant-scoped storage inside the authorization boundary.
Meeting chat under DLP
In-meeting chat is screened by your sensitive data rules before messages send.
Meeting actions audited
Start, join, leave, recording, and host controls each write a sanitized event to an immutable trail, with no tokens, emails, or display names in the logs.
Legal hold and retention
Recordings under hold are protected from deletion. Everything else follows automated retention and disposition.
Tenant isolation
Every meeting record is tenant-scoped and denied cross-tenant at the database and API layers.
Room for the whole program
Up to 250 participants per meeting.
How a call stays in scope
Schedule or start.
Schedule the meeting on your calendar in IRONKEEP MAIL, or start a call from a channel in IRONKEEP CHAT.
Screen who joins.
Pre-join device checks, waiting rooms, and expiring guest links control who is in the room before the call connects.
Meet and prove.
The call runs inside the authorization boundary, meeting actions land in the audit trail, and retention and legal hold cover any recordings you make.
Who it's for
Teams that bolted Zoom onto a governed stack.
A consumer video app next to compliant email and files adds a second vendor, a second data boundary, and a compliance gap no one owns. MEETINGS runs inside the boundary you already document.
Teams whose meetings touch CUI.
Screen shares, meeting chat, and recordings can carry controlled data. MEETINGS keeps them inside the same encryption boundary and audit trail as the rest of the suite, with meeting chat under the same DLP path.
Teams that meet with primes and subs.
External guests join scheduled meetings by invitation without creating accounts. Domain allowlists and expiring links keep access scoped to the meeting itself.
See also
FAQ
No. MEETINGS ships as part of the suite alongside IRONKEEP MAIL, IRONKEEP DRIVE, IRONKEEP DOCS, and IRONKEEP CHAT, under the same identity, encryption boundary, and audit trail.
Yes, for scheduled calendar meetings. Guests join by invitation only, with no account required. Admins can enforce domain allowlists, and invite links expire after a window you choose. Calls started from IRONKEEP CHAT are limited to people in your tenant.
Recordings stay inside the authorization boundary in encrypted, tenant-scoped storage. Recordings under legal hold are protected from deletion, and everything else follows automated retention and disposition.
No. MEETINGS covers audio, video, and screen share, with no PSTN dial-in and no transcription. Recording is cloud-only, and diagnostics are bucketed, carry no personal identifiers, and never leave your boundary.
United States only, on FedRAMP Moderate authorized cloud infrastructure, administered by US citizens. Tenant-scoped encryption keys and tenant isolation keep other tenants and IRONKEEP staff from reading tenant content.
Not yet. FedRAMP Moderate authorization work is in progress under the FedRAMP 20x program. IRONKEEP is not currently FedRAMP authorized, does not hold an Authorization to Operate, and is not listed on the FedRAMP Marketplace.
Private beta
Join the beta list and receive the CMMC Level 2 readiness checklist.
No sales call required.