AegisAI Perspectives · 156
Check a new AI email security vendor on five points before you pick one: funding and team, API access, data handling, a trial on your own mail, support.
See it on your own Google Workspace or Microsoft 365 tenant. No MX change.
Or get the Q3 2026 State of the AI Attack report (free, instant download)
Not ready for a demo? Check your domain.

Look at any vendor that answers five checks in writing: funding and team, connection, data handling, proof on your own mail, support13. Treat a young AI email security vendor as a supplier with access to every mailbox: the UK NCSC sets 12 principles for control and oversight of suppliers. AegisAI reports on its inbound email security page (source: its Q3 2026 Phishing Trends Report) that 3 in 10 confirmed phishing emails cleared native Gmail and Microsoft filters in Q3 202611.
If you run IT for a small business or a company of 20 to 500 people on Google Workspace or Microsoft 365, with a small IT or security team and no SOC, run the five checks below on all AI email security startups you shortlist, ours included. The connection and verdict checks in depth are in how to judge AI-native email security vendors.
Key takeaways
- Google lists gmail.readonly, "View your email messages and settings", as a restricted scope1.
- In Microsoft Graph, only Privileged Role Administrator and Global Administrator can consent to application permissions7.
- Mail.Read as an application permission reads email in all mailboxes without a signed-in user8.
- TechCrunch reports AegisAI was founded by former Google security executives Cy Khormaee and Ryan Luo14.
- "Starts read-only." is the line to look for on a vendor's product page19.
| Question | Answer | Source |
|---|---|---|
| Which new AI email security startups should I look at in 2026? | Any vendor that answers five checks in writing: funding and team, connection, data handling, proof on your own mail, support. This page names no other vendor. The check table below shows one vendor's answers as a reference9. | NCSC; product page |
| What access does an API-based tool ask for? | On Google Workspace, Gmail API scopes such as gmail.readonly, which Google marks restricted. On Microsoft 365, Graph permissions such as Mail.Read across all mailboxes. | Google for Developers; Microsoft Learn |
| Who in my tenant approves it? | In Google Workspace, an admin with the Service Settings privilege, under API controls4. In Microsoft 365, a Privileged Role Administrator or Global Administrator. | Google Workspace Admin Help; Microsoft Learn |
| How do I check a young vendor's funding and team? | Open a named press report and the vendor's own site, and match the names and amounts15. | TechCrunch; careers page |
| How do I prove it before I sign? | Connect it read only on your own tenant first, and grant removal later20. | Inbound email security page |
Short on time? Watch the explainer, or book a demo.
A young vendor's funding and founders are public facts you can check before the first call. Ask for one named press report, then open it yourself.
For AegisAI, TechCrunch reports a 36 million dollar Series A led by Battery Ventures. The careers page states: "Battery Ventures led the $36M Series A in July 2026, with Accel and Foundation Capital." SecurityWeek reports the company was founded in 2025, and that the round brings total funding to 49 million dollars16. The same careers page says: "The founding team that built Safe Browsing, reCAPTCHA and Web Risk at Google is hiring."25
Two sources that agree on the round and the lead investor are enough. A mismatch is a question for the first call. Write the lead investor and the round in your notes before any demo.
An API-based, AI-native tool connects through your mail platform, not your mail routing. SecurityWeek reports AegisAI connects to Microsoft 365 and Google Workspace through an API17. Its product page puts it this way: "Out of band. It reads mail through the Microsoft 365 or Google Workspace API after delivery. No MX change, no gateway."18
The access level is the check. On Gmail, three OAuth scopes matter.
On Microsoft 365, application permissions work without a signed-in user, and Microsoft calls them highly privileged6. Mail.Read reads email in all mailboxes. Mail.ReadWrite can create, read, update and delete email in all mailboxes, and does not include sending10. Ask the vendor for the exact scope or permission list, in writing, for each mode it runs in.
The approver is a role in your tenant, not the vendor. In Google Workspace, app access sits under API controls in the Security section, and needs the Service Settings administrator privilege. An app set to Specific Google data can request only the scopes you specify5. A Limited app can only access unrestricted services.
In Microsoft 365, only an admin can consent to application permissions, and only Privileged Role Administrator and Global Administrator can do it. Microsoft calls tenant-wide admin consent a sensitive operation, and tells admins to review the requested permissions first12. AegisAI connects "with an OAuth grant your admin controls and can revoke"21. Name the person who will approve and revoke before the trial starts.
Ask two questions in writing. What is stored, and for how long? Is customer email used to train models? A vendor that cannot answer both on paper fails this check.
Our own answers are on the live site. The data retention and encryption post states: "Messages are read through the API, analyzed in memory and discarded."23 "Threat history is available in the console for 90 days by default." And: "Customer email content is not used to train models operated by third-party AI labs"22. Put each vendor's two answers side by side in your notes.
Run a read only trial on your own tenant, which shows what the tool finds in your mail. A demo only shows mail the vendor chose. The full trial plan is in how to structure a read only email security proof of concept.
Ask for the read only scope or permission list for the trial.
Have your Workspace admin or Microsoft 365 approver review it before consent.
Connect the tool with read access only, and keep removal off.
Run it on live mail for the whole trial period.
Count what it flagged after delivery that your current filters let through.
Open each flagged message in the trial tool's report, and mark it real or false in your own sheet.
Grant write access only after the count, and note who can revoke it.
Book the trial dates and the review meeting before you connect anything.
Support after you sign is what the vendor puts in writing, so get the support terms on paper first. Ask who answers a ticket, in what hours, and how fast for a missed attack or a wrongly removed message. Ask what happens to your mail if the service is down. A vendor that will not write these down fails this check.
Fill one column per vendor. The AegisAI column shows what its live site and named press state today, and where the site is silent, it says so.
| Check | Ask the vendor | Where to verify | AegisAI's answer |
|---|---|---|---|
| Funding | Who led the last round, and when? | A named press report | Battery Ventures led a 36 million dollar Series A, July 2026 |
| Team | Who founded it, and what did they build before? | Its own site and press | Founders Cy Khormaee and Ryan Luo, former Google security executives; founded in 2025 |
| Connection | API or mail routing? | Product page | API after delivery, no MX change |
| Access at start | Which scopes or permissions in trial mode? | Gmail scopes page, Graph permissions | "Starts read-only." |
| Removal | What extra access does removal need? | Product page | Write access your admin grants and can revoke |
| Approval | Who in my tenant must consent? | Admin console, Entra | Set in your tenant: Service Settings admin on Google, Privileged Role or Global Administrator on Microsoft |
| Training | Is customer email used to train models? | Trust or data page | Not used to train models operated by third-party AI labs |
| Retention | What is stored, and for how long? | Data handling page | Analyzed in memory and discarded; threat history 90 days by default |
| Support | Who answers, and how fast? | A written support commitment | The inbound email security page does not state a support time; ask in writing |
Send the Ask column to every vendor before the first call.
Our page on how to judge AI-native email security vendors says: "AegisAI investigates every email for what it is trying to do, and removes the ones that fail from every mailbox they reached." It reads mail through the Microsoft 365 or Google Workspace API after delivery. Removal needs write access your admin grants and can revoke. Customer email content is not used to train models operated by third-party AI labs.
Track three numbers, each from a place you can open.
To get the second number on your own mail, ask for a read only test on your tenant. Compare the three figures on day 30 before you grant write access.
Look at AI email security startups that answer five checks in writing, from funding and team to support. Run the same checks on AegisAI.
Open a named press report and the vendor's own site, and match the round and the lead investor. A mismatch is a question for the first call.
Yes, for counting what a tool finds. gmail.readonly lets an app view messages and settings. Mail.Read reads email in all mailboxes without a signed-in user. Removal needs write access later.
Only a Privileged Role Administrator or a Global Administrator can consent to application permissions. Microsoft tells admins to review the requested permissions first.
No, for an out of band tool. The AegisAI product page says: "It reads mail through the Microsoft 365 or Google Workspace API after delivery. No MX change, no gateway." Answers about the product itself are in what the product does.