Loading page…
A security platform for employee-built AI tools that reached $2M ARR soon after launch.
40+ enterprise customers · 1M+ endpoints protected
The wedge is security for software employees already create with AI: protect the browser extensions and internal tools that traditional procurement never reviewed.
Fewer bars = easier, cheaper, or faster for an AI-assisted solo builder. Editorial judgments based on the case details.
Pluto Security is an Israeli security startup focused on the shadow software employees create themselves: AI-built tools, browser extensions, and vibe-coded applications. The company emerged from stealth on October 13, 2026, and disclosed $42 million in financing across an approximately $34 million Series A led by Jump Capital and an approximately $8.5 million seed round led by TLV Partners. Armis founders also invested. Pluto began selling in April 2026 and says annual recurring revenue has already passed $2 million. It reports more than 40 enterprise customers, including Oscar Health, Workato, Sixt, and AlphaSense, and says its platform protects over one million endpoints. That combination points to an unusually urgent enterprise problem: software creation has spread beyond central IT, while security review still assumes a managed development process. The product gives security teams visibility and control over tools created outside that process. The numbers are company claims repeated in a news briefing, not audited financials or independently verified customer metrics.
For an enterprise security product aimed at AI-built apps and browser extensions, the first customers usually come from a narrow, high-trust wedge rather than broad awareness.
The quick-reference card — acquisition channels, replication playbook, risks & traps, and our verdict — is members-only.
Join the Unicorn Club — $5/moCancel anytime, in one clickPaste into Claude Code / Codex and get a working version of this product end-to-end.
Two production-grade prompts per idea — a full build spec and an SEO growth plan — plus 10 tailored build specs a week. Members only.
Join the Unicorn Club — $5/moCancel anytime, in one clickEvery claim traces back to a listed source — open any of them and check the number yourself.
Data credibility: Creator-Reported. The October 16, 2026 news briefing reports Pluto Security's $2M+ ARR, 40+ customers, and 1M+ endpoints, along with its funding and named customers. These are company-reported figures relayed by a news channel; no financial statements, customer confirmations, or independent endpoint measurements were presented.
The first dollar in this category usually arrives as a paid enterprise pilot that converts into an annual platform contract.
Security products compound when every deployment improves both detection and buyer confidence. For Pluto’s market, broader endpoint coverage can surface more employee-built applications, which gives security teams a stronger inventory and helps them prioritize the riskiest data paths.
A security startup can spend months in a quiet stretch while buyers complete risk reviews, procurement, and legal checks. For Pluto’s enterprise market, that silence is not a reliable signal of product failure: security teams may agree with the problem but lack a budget owner or a route through vendor onboarding.
Pluto Security sells a platform for protecting software created directly by employees, including AI tools, browser extensions, and vibe-coded applications. Its central job is to extend security visibility to software that bypasses the usual engineering and procurement pathways. In a mature implementation, that means finding these applications, understanding their permissions and data access, assessing risk, and giving security teams controls for monitoring or remediation. The company’s reported figure of more than one million protected endpoints points to a deployment surface that spans employee devices, while its customer list includes organizations across healthcare, workflow software, travel, and financial research. That breadth suggests a cross-industry control rather than a single vertical application. The value is not simply blocking AI use: employees are already building tools to solve real workflow problems. A useful product helps teams distinguish safe, valuable experimentation from applications that expose credentials, customer data, or regulated information. The platform therefore sits between endpoint management, application security, and AI governance, with adoption depending on how well it fits existing security operations.
The reported $2 million-plus ARR implies recurring enterprise subscriptions rather than transactional security audits. A likely commercial structure combines a platform fee with deployment scale, such as endpoints, applications, or organizational coverage, although the briefing does not give Pluto’s exact pricing. The 40-plus customer figure provides a rough denominator but not a reliable average contract value: customer sizes and contract stages may differ substantially. For a new company in this category, annual agreements make sense because discovery and remediation are continuous as employees create new software. Tiering can connect price to the depth of controls: inventory and visibility at the entry level, policy enforcement and integrations in higher tiers, and enterprise support or data retention as add-ons. Sales qualification should identify a security owner, a business unit willing to pilot, and an existing control gap before implementation begins. A strong renewal case comes from ongoing coverage and measurable reduction in unknown applications, not from a one-time inventory report. Keep the value metric understandable to finance and security buyers alike.
A platform monitoring employee-built software has meaningful engineering and operating costs. It needs reliable endpoint or browser visibility, application analysis, identity and policy integrations, and a secure multi-tenant control plane. Detection quality matters because false positives create expensive analyst work and erode trust. The infrastructure bill can rise with telemetry volume and retention, so a founder should design sampling, compression, and tiered storage before broad deployments. Enterprise sales also add costs that a simple self-serve SaaS avoids: security questionnaires, implementation assistance, compliance evidence, and integration maintenance. Pluto’s substantial disclosed financing—$42 million across the seed and Series A—provides room to build this infrastructure and support enterprise expansion, but it is not evidence of profitability. A smaller entrant could focus on a single ecosystem, such as browser extensions in a defined regulated industry, and use managed deployment services during early pilots. Gross margin improves as onboarding becomes repeatable and detection runs efficiently, while customer success remains important for large accounts. Treat security certification and incident response as core operating expenses.
Copy the timing and problem framing: employees are building useful software with AI, and security teams need a way to govern it without shutting down experimentation. Start with one observable surface and one buyer, then prove a measurable reduction in blind spots. Pluto’s early enterprise adoption shows that the concern can support paid contracts, while its $42 million funding indicates the category also attracts substantial capital and ambitious competitors. A bootstrapped version should not attempt to recreate a broad endpoint security platform immediately. Choose a constrained workflow, such as discovery and risk review for employee-built browser extensions, and integrate with the controls the target customer already owns. Sell a paid assessment that naturally becomes ongoing monitoring, but make the recurring benefit clear from the first deployment. Build credibility with transparent detection methodology and careful handling of customer code and telemetry. Avoid claiming comprehensive AI security before the product can demonstrate it. The transferable lesson is to convert a fast-changing technology behavior into a concrete governance task with an accountable budget owner.
The largest risk is that the category expands faster than customer budgets and policy clarity. Security teams may acknowledge employee-built AI software while choosing to manage it through existing endpoint, browser, or identity products instead of buying a new platform. Detection that is noisy, incomplete, or easy to bypass would undermine trust quickly. The product also handles sensitive endpoint and application telemetry, making its own security posture and data governance critical to enterprise adoption. Large security vendors can bundle adjacent controls, compressing the room for a standalone startup; meanwhile, AI development methods and the applications they produce change at a rapid pace. Enterprise sales cycles may outlast startup runway, especially when procurement requires audits and integrations. Pluto’s named customers and reported ARR show commercial traction, but the evidence comes from company-reported claims in a news summary and does not establish retention, margins, or renewal rates. A founder entering this market should validate repeat usage, measurable risk reduction, and willingness to pay before investing in broad platform coverage.
The four founder playbooks — first customers, first dollar, the flywheel, the silent stretch — are in the Unicorn Club, on this idea and on all 1,403 others. The story, the numbers, the sources and every later section stay open to everyone.
Join the Unicorn Club — $5/moCancel anytime, in one click