Most of what genuinely goes wrong at a small company arrives politely, in writing, apparently from somebody the reader already trusts. A changed account number on a real invoice. A sign in prompt that looks exactly correct. This route stations a second reader inside the tenant and gives your people practice at catching the first one.
Ironscales does its reading inside the mailbox itself, using the API your tenant already exposes. Stated plainly, because the market muddles this endlessly: no gateway appears anywhere in this arrangement. Your routing records never move, no appliance joins the rack, and no fresh hop gets invented that could fall over and take the mail with it. The connection runs directly into whichever tenant you keep, Microsoft or Google.
That shape buys one thing no gateway can offer. A gateway gets a single look, at the moment of transit, and once it has waved something onward its opinion is spent. Working from inside, a reader may revisit an earlier decision, decide that one was wrong, and withdraw the offending message from wherever it settled.
The second item is practice. Exercises run against a calendar you approved, and whoever is taken in receives a brief lesson rather than a note to their manager. The object is a workforce that flags odd mail quickly, and humiliation produces the exact opposite of that.
It is quoted per seat because a person is what you are training. Plenty of firms protect every mailbox and drill only the departments touching money or client records. That is a reasonable way to spend a budget and we will not talk you out of it.
Each figure here is pulled out of the billing service as this page opens. Load a line now and it waits in the bag until you have finished reading.
Ironscales does its reading inside the mailbox itself, using the API your tenant already exposes. Being explicit, since the market muddles this: no gateway forms any part of it. The connection runs straight into Microsoft 365 or Google Workspace and examines what has arrived, which is how a bad message gets taken back out afterwards. Routing records never move and nothing new joins the path mail travels.
| Carried on | Ironscales, connected to Microsoft 365 or Google Workspace by API |
|---|---|
| Covers | Mailboxes in the connected tenant, after delivery |
| Held in transit | Quarantined and withdrawn messages held in the Ironscales console |
| Postmarked by | Continuous, with our desk handling escalations |
| Signed for | One mailbox, one line, one monthly rate |
The drill on its own, for teams that already run mailbox protection elsewhere or want to train more people than they protect. Exercises are released on a calendar, and anyone taken in gets a brief lesson instead of a telling off.
| Carried on | Ironscales training and simulation platform |
|---|---|
| Covers | Named users you enrol, whether or not their mailbox is on the other line |
| Held in transit | Campaign results and training records held in the Ironscales console |
| Postmarked by | The campaign calendar you agree at rollout |
| Signed for | One user, one line, one monthly rate |
Mail protection is the control most often oversold. This is the true shape of what it touches.
Heads up: card statements show FORTIFY 24X7 - Stars and Stripes IT is a Fortify 24x7 brand, and your subscription is billed by Fortify 24x7.