Communication
Communication responsibilities and links to its capabilities, documentation, and pricing.
Communication
Provides the Capabilities through which parties exchange information and coordinate private, public, remote, and in-person interactions under the applicable permissions.
Inbox
The Communication Capability that presents a governed, attention-oriented view of communication items and platform updates from their authoritative sources while preserving each source's visibility, privacy, action, lifecycle, and provenance rules. Source readers and actions remain authoritative; Inbox stores no second archive and grants no new action authority.
The Capability responsible for email communication through controlled addresses, with defined address-lifecycle, message-handling, disclosure, and sending boundaries.
MailGap containment
The containment guarantee applied to service correspondence: message content stays inside CAIRL rather than being forwarded to the person's real inbox; display is plaintext; attachments are quarantined by default; sending is reply-only from inbound scope under send-token enforcement; and there is no general outbound composition. These obligations form one feature contract and do not grant public-alias sending permission.
- Documentation: How MailGap works
- Guide: Manage your aliases
- Tutorial: Read and reply in MailGap
- Pricing: Personal plans and inclusions
Gateway origin containment
The containment guarantee applied to a person's connection when they reach a participating platform: the platform observes a CAIRL egress node rather than the person's own connection; the routed set is derived from the CAIRL service registry and cannot be widened by configuration; every other destination connects directly with no CAIRL involvement; a routed destination fails closed rather than falling back to a direct connection; and neither plane stores or can query a record joining a person to a destination, because the control plane holds identity and never sees a destination while the egress nodes see destinations and learn only whether a presented credential is valid. It is one Capability rather than a grouping because those obligations are a single coherent containment responsibility carried by one enforceable contract, which holds or is breached as a whole.
Explore Gateway origin containment
- Documentation: How GateWay routes traffic
- Guide: Browser and computer scope
- Tutorial: Handle your proxy credentials
- Pricing: Plans and usage
Pricing
This area groups capabilities; pricing and inclusions depend on the service and how it is used. Follow the applicable service documentation and current pricing pages.