Nearly every serious loss at a small firm walks in through the mail, and hardly any of it looks like a swindle. It looks like an invoice from a company paid eleven times before, sent out of their genuine account, inside a thread you both remember. Filtering at the front door cannot catch that. Something has to be sitting in the mailbox.
Ironscales gives protection at mailbox level over API, and to call that a gateway would be plainly wrong. The distinction matters far more than it sounds. A gateway inspects on the way through, then holds no further view. An API connection lives inside the tenant, reads whatever already landed, and remains able to act an hour afterwards, which is generally the moment somebody realises.
It also means nothing about your mail routing shifts. No records to re-point, no cutover evening, no window with mail queueing while a change propagates. Authorise the connection inside the tenant and it begins reading.
The second lever is simulation and training, honest about its own nature: against a message crafted well enough to survive every filter you own, the single control that works is a person who pauses. Testing runs continuously in place of annually, and lessons reach whichever people the results point to.
Bought alone it is training. Bought beside the mailbox lever the two feed one another, because what gets reported inside the tenant shapes the campaign that follows.
Rates are lifted live from billing while this page loads. Whatever you send to the sheet sits waiting while you read on.
Ironscales gives protection at mailbox level over API, and it is expressly not a gateway. Reading mail that already landed is the only place you will catch a message sent from a genuine supplier account that somebody else took over last week.
| Cleared for | Mailboxes inside a Microsoft 365 or a Google Workspace tenant |
|---|---|
| Protects | Mail already delivered and sitting in the mailbox |
| Held until | Somebody in the tenant authorises the API connection |
| Signalled by | Ironscales, at mailbox level and never as a gateway |
| Confirmed by | Reporting per mailbox, plus the banners your staff actually see |
By itself this lever protects nothing whatever. What it alters is behaviour, and behaviour is the only control that answers a message good enough to survive every filter you own. Purchased alone it is training. Purchased beside the mailbox lever it is training aimed at genuine results.
| Cleared for | Anybody holding a mailbox in the tenant you connected |
|---|---|
| Protects | Nothing by itself. What it alters is behaviour |
| Held until | Scope and frequency of testing have both been settled |
| Signalled by | Ironscales campaign and training reporting |
| Confirmed by | Results per person, with lessons handed out from them |
Mail is the route most money leaves by, and even here there are edges. Below are those worth understanding before a purchase.
Heads up: card statements show FORTIFY 24X7 - ServiceShield IT is a Fortify 24x7 brand, and your subscription is billed by Fortify 24x7.