Mailbox and phishing defense

Email security

Email security products from public homepages. This set has no thread that names a switch away from a specific email product.

Public pages, not a ranking

Alphabetical inside each group. Positioning is a paraphrase of the linked page, checked 2026-10-15, unless the cell says a claim was not extracted. Dollar amounts appear only in the price column, with a source.
VendorGroupWhat the public page supportsPrice signal
IronscalesPublic product pageHomepage describes AI email security for phishing and business email compromise, and says MSPs get a multi-tenant console. Homepage checked 2026-10-15. No dollar amount on that page.Omitted. No dollar amount on the page we checked.
ProofpointPublic product pageHomepage describes human- and AI-centric security for collaboration and data, including email threat protection. Homepage checked 2026-10-15. No MSP price on that page.Omitted. No dollar amount on the page we checked.
TodylPublic product pageHomepage describes an email security product that pairs detection with analysts and quarantines messages across mailboxes. Todyl is also on the EDR/MDR board. Homepage checked 2026-10-15. No dollar amount on that page.Omitted. No dollar amount on the page we checked.

Switch triggers

The general triggers this desk watches are a price change, a sour account-management relationship, and distributor or marketplace fees. Those are themes from public MSP discussions. A theme is attached to a named product only when a linked thread title supports it.

No thread in the 15 October 2026 research set names an email-security product as the thing being replaced. Rows are public product pages, alphabetical, with no rank.

Migration checklist stub

A starting list, not a vendor runbook. Confirm each step against your contract and the vendor’s own documentation.

  • Export the client list, site list, and the count of agents or collectors you actually bill.
  • Read the current agreement for notice, auto-renewal, and what you can export when you leave.
  • Write down the alerts, scripts, and integrations that have to exist on day one.
  • Pilot on one non-critical client before a fleet cutover.
  • Leave the old agent or collector in place until the new one is reporting.
  • Note whether you buy direct or through a distributor, and who owns that login.
  • Decide whether mail flow (MX) has to change, or whether the tool sits beside the current gateway.
  • List Microsoft 365 or Google Workspace tenants in the pilot.

Back to the full board