Pluto Security funds monitoring of non-developer AI tools
The filing says finance departments are the biggest source of detected risk, and the round funds monitoring of non-developer tools.
| Pluto Security | |
|---|---|
| funding | $42 million |
| Series A | $34 million |
| seed | $8.5 million |
| ARR | $2 million |
| enterprise customers | more than 30 |
| vibe-coded risk share | about 60% |
| tool appearance time | two hours |
| sales start | April |
The round totals $42 million. Jump Capital led the $34 million Series A, and TLV Partners led the $8.5 million seed.
Bahat says a newly announced AI tool can appear inside a company within two hours.
About 60% of detected risks sit in vibe-coded tools made by non-developers.
Finance departments are the biggest source, followed by marketing and legal, with developers fourth.
The company says it began selling in April and has crossed $2 million in annual recurring revenue with more than 30 enterprise customers.
The filing leaves out product name, detection latency, block rate, and incident count. It also leaves out exact customer count, exact ARR, named Fortune 500 customer, and any measured reduction in exposed AI tools.
The buyer is constrained by internal AI sprawl, not by perimeter gaps. The round funds visibility into non-developer tools, but the filing does not prove that exposure is reduced.
The filing supports monitoring, not a measured reduction.
After answers.microsoft.com. We did not report this. The pictures, if any, are theirs.
