Skip to content
Rush Commerce
AI & Automation3 min read

Neo raises $100M to govern AI agents inside your SaaS

Neo exited stealth with $100M to inventory and control AI agents embedded in software you already bought. The shadow AI problem isn't the agents you deployed.

Ask most operators how many AI agents are running in their business and you'll get a number based on what they deployed on purpose. That number is wrong. The AI agents worth worrying about are the ones your vendors shipped into products you already pay for — your browser, your CRM, your help desk, your IDE — each one arriving with permissions nobody scoped. A Boston startup just raised $100 million on that exact gap.

What actually happened

On July 20, Neo came out of stealth with $100 million across seed and Series A financing from Andreessen Horowitz and Bessemer Venture Partners, with Craft Ventures and Merlin Ventures joining. The founding team is not first-timers: CEO Nick Warner was president and COO at SentinelOne through its IPO, CPO Shlomi Salem led detection engineering there, and CTO Eran Shirazi co-founded EasySend.

The product is a control layer, not another chatbot firewall. Per SecurityWeek, Neo keeps a live catalog of the AI agents, models, extensions, and MCP servers active in an environment, flags over-broad permissions and bad configurations, attributes each action back to a specific user or app, and enforces policy at the level of individual tool calls and API requests — including pausing an operation for review. Warner's framing of the problem is the honest part: agentic capability is being embedded into browsers, developer tools, SaaS platforms, and ordinary business apps, with permission to act on its own. Neo's announcement cites Gartner projecting that agentic features go from 5% of enterprise applications in 2025 to 40% by the end of 2026.

Why it matters for your business

You will not opt into most of this. Your vendors will ship it, enabled, in a Tuesday release note. A 12-person company running Google Workspace, a CRM, a support inbox, and two dev tools now has agentic software touching customer records without a single procurement decision behind it. That's the shadow AI problem, and it's structurally different from the agents you built and scoped yourself.

You don't need a $100M platform to get ahead of it. Do the boring version. Write down every SaaS product you pay for and check what AI features shipped in the last two quarters and what data they read. Turn off the ones with no owner. For the ones you keep, check the OAuth scopes and the connected-app list in each admin console — that's where an "assistant" quietly gets write access to your entire Drive. Then decide, on purpose, which systems an agent may write to and which are read-only forever. The governance question isn't whether AI agents are in your business. They are. It's whether you can name them.

Key takeaways

  • Neo exited stealth July 20 with $100M from a16z and Bessemer, founded by former SentinelOne and EasySend leaders
  • The product inventories AI agents, models, extensions, and MCP servers, flags excessive permissions, and enforces policy per tool call
  • The real exposure is agentic features your vendors enable inside software you already bought — not the agents you deployed deliberately
  • Audit your SaaS stack's new AI features, review OAuth scopes and connected apps, and decide which systems agents may write to

Not sure what's already touching your data? We audit the AI features hiding in the software you pay for, scope permissions to what the job actually needs, and wire in logging you can audit. See how we build governed automation or book a stack review.

Sources: Neo via GlobeNewswire, SecurityWeek.

  • #ai-agents
  • #shadow-ai
  • #ai-governance
  • #neo
  • #saas
TR

Tommy Rush — Founder, Rush Commerce

Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More

Get The Rush Report weekly — one email, zero fluff.