- Supported
- Partial or conditional
- Not supported
- Not publicly documented
| Capability | Comma Compliance | Archive IntelFull comparison | Archive360Full comparison | Arctera (formerly Veritas)Full comparison | FirmScribeFull comparison | Global RelayFull comparison | HadriusFull comparison | IntradynFull comparison | JatheonFull comparison | LeapXpertFull comparison | Microsoft PurviewFull comparison | MimecastFull comparison | MirrorWebFull comparison | NICE ActimizeFull comparison | OpenTextFull comparison | ProofpointFull comparison | SmarshFull comparison | SnippetSentryFull comparison | SteelEyeFull comparison | Theta LakeFull comparison |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Capture | ||||||||||||||||||||
| WhatsApp capture | Supported: Yes | Partial or conditional: Connector listed; capture architecture not described in public documentation | Partial or conditional: Through partners (LeapXpert, Sausalito Labs) | Supported: WhatsApp Business and personal; all threads or business threads only | Partial or conditional: WhatsApp Business only, via a direct Meta BSP relationship. Personal WhatsApp not captured. | Partial or conditional: Listed; capture method not specified | Partial or conditional: App-level archiving; needs a separate virtual business number for each employee | Supported: Yes | Partial or conditional: Native Mode and Governed Mode; BYOD needs a dedicated app with a separate business number | Not supported: Microsoft still documents a TeleMessage connector, but TeleMessage has not resumed service since its May 2025 breach | Not publicly documented: Not listed in current product documentation | Partial or conditional: Via the Trusted Contacts app; capture method not publicly documented | Partial or conditional: Via Movius MultiLine partnership, on a Movius business number; needs the Movius app on each device | Partial or conditional: Listed; historically via TeleMessage. Current capture architecture not described. | Supported: Via Proofpoint Capture | Not supported: Via TeleMessage, whose services have been suspended since 2025 | Supported: Yes | Partial or conditional: Historically partnered with TeleMessage; current capture methods not fully documented | Partial or conditional: Via partner integrations (LeapXpert, Movius, CellTrust) | |
| Signal capture | Not supported: No | Not publicly documented: Not listed in public documentation | Partial or conditional: Through partners (LeapXpert, Sausalito Labs) | Not supported: Not supported | Not publicly documented: Not documented | Not publicly documented: Not named in any public documentation | Not supported: Not natively supported | Not publicly documented: Not listed among supported channels | Partial or conditional: Via Governed Mode through Teams or the Leap Work app | Not supported: Microsoft still documents a TeleMessage connector, but TeleMessage has not resumed service since its May 2025 breach | Not publicly documented: Not listed in public documentation | Partial or conditional: Stated; capture method not publicly documented | Not publicly documented: Not documented as a supported channel | Partial or conditional: Listed; current capture architecture not described in public documentation | Supported: Via Proofpoint Capture | Not supported: Via TeleMessage, whose services have been suspended since 2025 | Not supported: Not supported | Partial or conditional: Historically partnered with TeleMessage; current capture methods not fully documented | Partial or conditional: Via LeapXpert integration | |
| iMessage capture method | Supported: Point-of-delivery, not iCloud-dependent | Partial or conditional: Proprietary capture method | Not publicly documented: Not listed in public documentation | Partial or conditional: Through partners (LeapXpert, Sausalito Labs) | Partial or conditional: Capture methodology not publicly detailed; all-threads or business-threads-only mode | Partial or conditional: Syncs with the user's Apple ID/iCloud account; depends on Apple sync rather than real-time capture | Not publicly documented: Not named in any public documentation | Partial or conditional: Device agent on corporate-owned devices. On BYOD, iMessage must be disabled and business texting falls back to SMS/MMS. | Supported: Yes | Supported: Custom data center infrastructure; Native Mode (native iMessage app) and Governed Mode (via Teams or Leap Work app) | Partial or conditional: Via third-party connector; previously routed through TeleMessage infrastructure | Not publicly documented: Not listed in public documentation | Partial or conditional: Via the Trusted Contacts app; capture method not publicly documented | Partial or conditional: Via Movius MultiLine, on a Movius-assigned business number. Personal-number iMessage not captured. | Not publicly documented: Not listed in public documentation | Supported: Via Proofpoint Capture | Partial or conditional: iCloud backup-based | Partial or conditional: Device-based; connection-dependent, with no current recovery for missed messages | Partial or conditional: Capture methodology not publicly detailed | Not publicly documented: Not documented in mobile capture materials |
| Channels supported | iMessage, Android SMS, WhatsApp, Gmail, Outlook, Slack, Teams, Zoom, Bloomberg, web, LinkedIn, YouTube, X/Twitter, and Meta | 280+ enterprise data types, including email, Teams, Slack, and Bloomberg; Signal and iMessage not listed | 130+ content sources; mobile messaging channels (WhatsApp, iMessage, Signal, WeChat, Telegram) through partners | iMessage, WhatsApp, WhatsApp Business, and Android SMS | 50+ data types, including email, mobile, social, Bloomberg, and financial messaging | Claims 30+ channels; no list published | Mobile, email, and social, each sold as a separate product with its own license fee | 22 listed, including email, social media, websites, Teams, Slack, Zoom, Bloomberg, iMessage, WhatsApp, and WeChat | WhatsApp, iMessage, WeChat, Signal, Telegram, LINE, SMS, RCS, and voice; integrates with Teams and Slack | Exchange, Teams, SharePoint, OneDrive, Yammer, and Microsoft 365 Copilot; non-Microsoft channels need third-party connectors | Email, Teams, Slack, Zoom, and Google Workspace; encrypted mobile channels not listed | RingCentral, WhatsApp, iMessage, SMS, RCS, WeChat, Teams, Slack, Google Chat, Symphony, social (LinkedIn, X, TikTok, YouTube, Facebook), Microsoft 365, Gmail, and websites | Claims 100+ communication types, including voice, video, chat, Teams, Zoom, Webex, mobile, SMS, WhatsApp (via Movius), WeChat (partner-fed), and turret recording | 50+ sources, including email, Teams, Slack, Bloomberg, LinkedIn, and YouTube; iMessage not listed | 80+ | 80+ channels, including email, mobile, social, voice, and collaboration | iMessage, SMS, WhatsApp, WhatsApp Business, and Android SMS | Email, voice, chat and mobile, financial messaging, and collaboration channels | 100+ integrations across unified communications, voice, video, email, social, and financial messaging | |
| Personal vs. business separation | Supported: Simple toggle: users mark contacts as business or personal, and only business conversations are archived | Supported: Yes: personal conversations stay private; only business communications are captured | Not publicly documented: Not documented for mobile channels | Not publicly documented: Not documented by Arctera; depends on the mobile partner | Partial or conditional: User-tagged: employees manually tag business threads, or all threads are captured | Partial or conditional: Authorization-based: employees authorize Global Relay access to their corporate iCloud account | Not publicly documented: Unstated | Partial or conditional: A separate business number; anything on that number is treated as business | Not publicly documented: Not listed | Partial or conditional: BYOD needs a dedicated app with a separate business phone number | Not supported: Not natively supported for non-Microsoft channels | Not publicly documented: Not documented for mobile channels | Partial or conditional: Via the Trusted Contacts app; employees opt in | Partial or conditional: A separate Movius business number for mobile messaging, or mandated corporate devices with managed apps | Not publicly documented: Not broadly documented for mobile channels | Not publicly documented: Not stated | Partial or conditional: Structural separation via a separate compliant app, MDM containerization, or carrier-level capture | Supported: Logs messages from known contacts only; personal messages excluded | Not supported: On BYOD, capture is tied to the device's number, so personal messages are included. SteelEye recommends consent or dedicated business devices. | Partial or conditional: Dependent on the mobile partner (for example, Movius provides a second business line) |
| Archive | ||||||||||||||||||||
| Architecture and archive | Supported: End-to-end: capture, archive, supervision, policy matching, and exam-ready case management in one platform. Archive included, with the option to push to a third-party archive. | Supported: AI platform with two products: communications archiving (capture and supervision) and marketing review. Archive included. | Supported: Enterprise data and AI governance platform across 280+ data types, strong in legacy archive migration. Capture architecture not described in public documentation. | Supported: Archiving, capture, surveillance, and e-discovery sold as suites; cloud, on-premises, or hybrid. Archive included. | Not supported: Capture-only: routes messages to a third-party archive | Supported: Enterprise platform: capture, archiving, supervision, and review in one managed platform. Archive included. | Supported: Compliance platform covering communications archiving, marketing review, trade surveillance, and employee oversight. Archive included. | Supported: Hardware appliance, virtual appliance, or cloud. Archive included; mobile and social are separate add-on licenses. | Supported: Archiving with capture connectors, search, e-discovery, and keyword alerts; cloud or on-premises | Not supported: Capture and governance layer only: exports to Smarsh, Global Relay, or another third-party archive, so a separate archive is required | Supported: Microsoft 365-native governance platform, strong for Exchange, Teams, SharePoint, and OneDrive. Archive included; non-Microsoft channels need third-party connectors. | Partial or conditional: Modular security platform; compliance archiving is one capability among four product lines. Capture architecture not described in public documentation. | Supported: Capture, archive, and AI supervision across a broad channel set; mobile capture via the Trusted Contacts app (launched March 2025). Archive included. | Partial or conditional: Modular: capture (NTR-X), archive (ARCHIVE-X, launched 2024), and surveillance (SURVEIL-X) are each purchased separately | Partial or conditional: Modular: separate products for archiving, eDiscovery, and records management. Supervision may need additional components. | Partial or conditional: Modular: Proofpoint Capture, Archive, and Supervision are separate products | Partial or conditional: Modular capture, archive, supervision, and review workflows across multiple systems | Not supported: Capture-only: routes messages to a third-party archive; data never at rest in SnippetSentry's system | Supported: End-to-end: capture, archive, communications surveillance, trade surveillance, and regulatory reporting | Partial or conditional: Modular: separate capture, archive, and supervision layers; mobile messaging through partners (LeapXpert, Movius, CellTrust) |
| WORM storage | Supported: Yes: written at point of capture | Not publicly documented: Implied through audit-ready archiving, but not stated as WORM | Supported: Yes | Partial or conditional: Opt-in when ordering, with a fixed 7- or 10-year retention period | Partial or conditional: Dependent on the third-party archive | Supported: Yes | Supported: Yes | Supported: Yes | Supported: Yes | Partial or conditional: Dependent on the third-party archive the customer chooses | Supported: Yes | Supported: Yes | Supported: Yes | Supported: Yes, via ARCHIVE-X | Supported: Yes: immutable, WORM-compliant storage | Supported: Yes | Supported: Yes | Partial or conditional: Dependent on the third-party archive chosen | Supported: Yes | Supported: Yes |
| Supervision | ||||||||||||||||||||
| Policy processing and custom matching | Supported: Yes: built in, with custom policy matching | Partial or conditional: Policy processing: yes. Custom matching uses AI-based filtering; structured policy matching not prominently documented. | Partial or conditional: Classification and retention rules | Supported: Arctera Surveillance: supervision policies, lexicons, and behavioral rules | Not supported: Not supported | Supported: Yes, with custom policy matching | Partial or conditional: AI classification with false-positive reduction; custom policy matching not defined | Partial or conditional: Keyword and lexicon rules | Partial or conditional: Keyword and user-group alerts. Content Policy can delete matching WhatsApp messages from the chat. | Supported: Yes, with custom policy matching | Supported: Yes, with custom policy matching | Supported: Yes: custom detection rules via Mimecast Aware | Supported: Custom policy matching: yes | Partial or conditional: Yes, via SURVEIL-X, a separate purchase | Partial or conditional: Customizable policies; policy processing through separate supervision components, not bundled in all products | Partial or conditional: Custom policy matching: yes. Supervision is an optional add-on, not a default inclusion. | Supported: Yes, via the enterprise platform, with custom policy matching | Not supported: Not supported | Supported: Yes, with custom policy matching | Supported: Custom policy matching: yes |
| AI compliance monitoring | Supported: Real-time policy scanning; human validation before escalation; no client data used for training without consent | Supported: AI-driven supervision | Not publicly documented: Not listed | Supported: Machine learning prioritization and an AI assistant for review | Not supported: Not supported | Supported: Proprietary LLM with chain-of-thought reasoning | Supported: AI classification with false-positive reduction; review queue with AI prioritization | Not publicly documented: Not listed; supervision is keyword and lexicon based | Not publicly documented: Not listed | Partial or conditional: Not documented as a native feature; depends on the third-party archive | Supported: Yes | Not publicly documented: Not listed | Supported: Sentinel engine | Supported: Actimize Intelligence generative-AI features for SURVEIL-X (May 2025); vendor-published metrics, not independently validated | Partial or conditional: OpenText Aviator provides AI assistants, summarization, and search across OpenText products | Supported: AI-assisted pre-review and post-review | Supported: "AI-powered supervision" | Not publicly documented: SentryWatch alerts on channel anomalies; no AI supervision documented | Supported: Compliance CoPilot | Supported: Patented AI and ML risk detection |
| Case management and e-discovery | Partial or conditional: Search and export tool | Partial or conditional: eDiscovery and legal investigations | Partial or conditional: Arctera eDiscovery: legal hold, cases, and redaction | Not supported: None | Partial or conditional: eDiscovery and litigation-oriented, built for legal holds and investigations | Partial or conditional: Review queue with AI prioritization | Partial or conditional: Scheduled searches, review cadence, and flagged-message review with comments and timeline | Partial or conditional: Legal hold, cases, and redaction | Not supported: Not documented; handled by the third-party archive | Partial or conditional: Oriented toward litigation, legal hold, and internal investigations | Partial or conditional: eDiscovery and investigations; not purpose-built for regulatory exam workflows | Not publicly documented: Not prominently documented for regulatory exam prep | Partial or conditional: Oriented around financial-crime investigation and trade reconstruction | Partial or conditional: eDiscovery and legal investigations via OpenText Core for eDiscovery | Partial or conditional: Oriented toward litigation | Partial or conditional: eDiscovery and litigation-oriented, integrating with third-party vendors | Not supported: Not supported | Partial or conditional: eDiscovery, legal hold, and trade reconstruction | Partial or conditional: Oriented toward litigation | |
| Trust | ||||||||||||||||||||
| Transparency | Partial or conditional: Capture code: not published. Pricing: published. | Not supported: Capture code: not published. Pricing: not published. | Not supported: Capture code: not published. Pricing: not published. | Not supported: Capture code: not published. Pricing: not published. | Not supported: Capture code: not published. Pricing: not published. | Not supported: Capture code: not published. Pricing: not published. | Not supported: Capture code: not published. Pricing: not published. | Not supported: Capture code: not published. Pricing: not published. | Not supported: Capture code: not published. Pricing: not published. | Partial or conditional: Capture code: not published. Pricing: published as part of Microsoft 365 licensing. | Not supported: Capture code: not published. Pricing: not published. | Not supported: Capture code: not published. Pricing: not published. | Not supported: Capture code: not published. Pricing: not published. | Not supported: Capture code: not published. Pricing: not published. | Not supported: Capture code: not published. Pricing: not published. | Not supported: Capture code: not published. Pricing: not published. | Partial or conditional: Capture code: not published. Pricing: free tier published, Premium not published. | Not supported: Capture code: not published. Pricing: not published. | Not supported: Capture code: not published. Pricing: not published. | |
| Commercial | ||||||||||||||||||||
| Pricing and free trial | Starts at $99/month, plus $40/user/month for text archiving and $12/user/month for each other connector; priced per seat per connector. No setup, retrieval or export fees; 1TB of storage included. No public free trial. | Not publicly listed; enterprise contract required. No public free trial. | Not published; quote required. Storage pooled at 15 GB per user; per-GB import and export fees. No public free trial. | Not publicly listed; quote required. 7-day free trial. | Not publicly listed; varies by deployment size and data sources; export fees set per order form. No public free trial. | Not disclosed; quote required. No public free trial. | Modular by channel: email per mailbox, appliance by storage (perpetual license plus annual support), mobile and social as add-ons. 30-day free trial. | Priced per user for each channel. Free trial not listed. | Subscription, priced per user and per supported channel. No public free trial. | Bundled with Microsoft 365 E3/E5; Communication Compliance needs E5 or an add-on; third-party connectors cost extra. Free trial via the Microsoft 365 Purview Suite. | Not publicly listed; custom quote required. No public free trial (email-security trials only). | Quote-based, not publicly listed; says no per-GB or hidden fees. No public free trial. | Not publicly listed; enterprise contract required; capture, archive, and surveillance are bought separately. No public free trial. | Not publicly listed; custom enterprise quote required. No public free trial. | Capture, archive, and supervision priced separately; enterprise contract required; not publicly listed. No public free trial (SMB email product only). | Not publicly listed; enterprise contract required; per-connector add-ons common; export fees may apply. No public free trial. | Free tier and Premium tier (Premium pricing not publicly listed). Free tier needs no credit card. | Not publicly listed; enterprise contract required. No public free trial. | Not publicly listed; tier and feature-set based; annual or multi-year. No public free trial. | |
Competitor feature descriptions reflect publicly available documentation and may not capture all capabilities. Information is reviewed periodically.