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.
Paubox delivers TLS to the inbox. We hold the message and send a code. If PHI must not sit in Gmail in the clear, you want a portal and a code.
| Paubox | Secure Message | |
|---|---|---|
| Delivery | TLS to the inbox | Hold the message and send a code |
| Where the body sits | In the recipient inbox after TLS lands — Gmail, or whoever they use | On your gateway until they open the portal |
| Who hosts it | Their service | You. Self-hosted gateway. |
| Recipient | Reads in the inbox they already use | Opens a link, enters a one-time code. No account. |
Paubox runs on their vendor cloud path and delivers TLS to the recipient inbox. Secure Message is MX on your host: the gateway holds the message and the one-time-code portal runs where you operate it.
| Plan / note | Paubox | Secure Message (Hub GET 2026-10-01) |
|---|---|---|
| Public list | Public price not verified (paubox.com/pricing, 2026-10-01) | Community free (1 domain · 1 administrator) |
| Professional | — | $690 / year |
| Enterprise | — | $1,490 / year |
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.
Check SPF, DKIM, and DMARC with the free email auth checker.
See how it works or pricing.