Request access

Product 04 · IRONCHAT

Team chat built for CUI work.

IRONCHAT is the conversation layer of the IRONKEEP suite: channels, threads, and direct messages next to your mail, files, and docs, covered by the same retention and audit controls.

Private beta · Q2 2026

Keep conversations in scope.

Receive product updates and the CMMC Level 2 readiness checklist.

Request access →
  • Beta updates
  • Readiness checklist
  • No sales call required

What's inside

IRONCHAT

Team chat that stays inside the compliance boundary.

Channels and DMs

Keep project conversations, private channels, and direct messages in scope.

Threads and mentions

Discuss decisions clearly with threads, mentions, edits, and unread state.

Secure attachments

Share files in chat without sending work outside the suite.

More IRONCHAT features

Searchable conversations

Find the channels, threads, and messages you are allowed to see.

Notifications that fit work

Use mentions, unread state, and digests to keep conversations moving.

Inside one suite

No separate chat vendor, identity setup, or assessor workflow to manage.

Retention and audit trail

Chat is covered by the same retention settings, audit logging, and legal hold controls as the rest of IRONKEEP.

Who it's for

Built for teams that keep conversations in scope.

Teams whose project chatter leaks into consumer apps.

Program details end up in personal messaging apps when the approved path is slower. IRONCHAT keeps quick questions inside the boundary.

Teams splitting decisions across email and chat.

Decisions scattered between inboxes and chat threads are hard to evidence. Threads, mentions, and retention keep the record in one place.

Teams consolidating tool sprawl.

A separate chat vendor means separate identity, separate logging, and separate assessor questions. IRONCHAT ships inside the suite.

Implementation path

From scattered threads to one record.

  1. 01

    Set up channels.

    Create channels for programs and teams, plus private channels and direct messages where needed.

  2. 02

    Chat where the work is.

    Share attachments, mention teammates, and thread decisions next to mail, files, and docs.

  3. 03

    Retain and prove.

    Retention settings, audit logging, and legal hold apply to chat. Pull evidence when your assessor asks.

FAQ

Common IRONCHAT questions.

Does IRONCHAT replace my CMMC assessment?

No. Your organization still owns its CMMC assessment. IRONCHAT is designed to provide compliant team chat, control mapping, and evidence to support that assessment.

Where is my data stored?

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.

Can IRONKEEP staff read my messages?

No. Zero operator access to tenant content is enforced by explicit deny rules on decrypt operations. IRONKEEP staff cannot read decrypted tenant content, run tenant decrypt operations, create product users, or generate tenant search tokens.

Is chat covered by retention and legal hold?

Yes. Retention settings, audit logging, and legal hold apply to chat, with scoped exports for compliance or legal review.

Can I share files in chat?

Yes. Share attachments in channels and direct messages without sending work outside the suite.

See also

Comparisons and guides.

vs Microsoft GCC High Teams after a tenant rebuild, or chat inside a dedicated boundary without one. vs Google Workspace The add-ons and configuration CUI requires on Workspace, and what IRONCHAT includes by default. What is CUI? Controlled Unclassified Information, explained for small contractors. ITAR controlled technical data Technical data shared in messages is still export controlled. CMMC Level 2 access control policies The access control family, mapped to day-to-day collaboration. DFARS 72-hour incident reporting What the clock demands when an incident touches covered systems.