What Ironscales gives you is mailbox-level API protection. It joins your Microsoft or Google tenant from the inside and examines what has already been delivered, internal mail included. The word gateway does not describe it, and borrowing that word would misstate the vantage point and the field of view together.
An opinion gets formed during delivery, and then a gateway goes quiet. Mail travelling any other road never meets it at all: forwarded between colleagues, sent from an account now under somebody else's control, or landed during the window before a rule existed. Joining over API seats the control within the tenant, where delivered mail remains readable and every copy of it remains reachable.
Reach is also what makes cleanup quick. When one message turns out badly, withdrawing it from all the mailboxes it landed in is a single instruction rather than a negotiation with whoever administers the mail platform.
A simulation is an experiment with a result. You learn how your own staff handle a persuasive message, and coursework then goes to the people the result identifies instead of to the whole company once a year in November. The combined line carries both halves.
Sometimes the gap really is only human, which is why the training line carries its own price. Buying defense twice over helps nobody, so the pieces are priced apart rather than rounded up into a bundle.
Every figure below is taken from billing as this page loads. Whatever goes onto the tray remains there while you read on.
Ironscales attaches by API to whichever tenant you run, then examines whatever has already landed in the mailbox, internal messages included. Mailbox-level API protection sits at a different vantage point than any gateway, and that word will not be borrowed here, since position governs what a control can possibly see.
| Runs on | Whichever mail tenant you run, joined by API |
|---|---|
| Reacts to | Messages already delivered, internal senders included |
| Shelved for | Tenants where one persuasive message would be enough |
| Cleared by | Bad messages withdrawn from every mailbox at once |
| Assayed by | Counted per mailbox, each month |
Send the test, record the result, teach the people the result points at. Take this line alone when the mail itself is already defended and what remains uncontrolled is habit.
| Runs on | Your existing tenant, people enrolled by address |
|---|---|
| Reacts to | What each person does with a planted message |
| Shelved for | Offices whose mail is guarded but whose habits are not |
| Cleared by | Results read through with you, not parked in a console |
| Assayed by | Counted per user, each month |
Mail is where smaller companies actually lose money, so precision about the reach of these two lines earns its paragraph.
Heads up: card statements show FORTIFY 24X7 - H2 Tech Systems is a Fortify 24x7 brand, and your subscription is billed by Fortify 24x7.