Ask Secure Message a question. Answers come from this site's docs only. I will cite a page. I will not invent a product claim.
A self-hosted secure email gateway sits in front of the mail you already run. You host it. You hold the keys. Community starts with inbound filtering. Matching outbound mail is held for a one-time-code portal on Professional. It is email — not TigerConnect, not Zix cloud, not Purview.
Secure Message is email. Recipients do not install a client, join a chat, or create an account. They open a link and enter a one-time code sent to the mailbox they already have. It is not TigerConnect and it is not a paging or clinical-chat app.
A hosted encryption service keeps the keys and the message path on someone else’s infrastructure. We encrypt on the host you run. The Zix split is on the vs Zix page. Microsoft’s cloud path is on the OME replacement page.
Point MX at the gateway and relay outbound through it as a smart host. Mailboxes stay where they are. On Professional, matching outbound mail is held and opened in a one-time-code portal. Encryption keys live on the host you run.
Enterprise adds Autopilot, eDiscovery, and DLP. The inbound classifier is one Enterprise signal and stays off until you turn it on. Message content is not sent to a vendor model unless you opt into a hosted provider.
Rubix PDF Sign fills, signs and flattens PDFs on the workstation. No cloud account, no telemetry. It is a free download, and meant to pair with the gateway: sign locally, then send through Secure Message.
Healthcare buyers who need the HIPAA framing should start on the HIPAA email gateway page. See how it works or pricing.