Pluto Security Raises $34M Series A for AI Workspace Security

The authority to create software is spreading through the office faster than responsibility for its consequences can be reassigned. Pluto Security sells security teams a way to follow that work, including the moment an employee-built workflow reaches for access it should have to request.

The cybersecurity company emerged from stealth on October 13, 2026, with $42M in cumulative funding, including a latest financing of approximately $34M led by Jump Capital. The latest round is reported as Series A. Co-founders Shahar Bahat, CEO, Tal Ofer Regev, CPO, and Gil Maman, CTO, are building AI workspace security across Israel and the US, with new capital intended for product development, research and US expansion.

The distinction between a useful automation and an authorized action sits at the center of Pluto's opportunity. Employees can create applications and agents through AI tools, while a CISO still has to account for the company data, credentials and systems those creations reach. A financing round helps pay for the product; the purchasing decision will turn on whether that product can make those responsibilities manageable in daily work.

What Pluto Security's financing actually includes

Pluto's official launch post describes $42M in total funding. The approximately $34M latest round is part of that cumulative disclosure, an important distinction for anyone comparing financing announcements. The Jerusalem Post's contemporaneous account identifies Jump Capital as the lead, with Skinos Ventures and AlphaDrive Ventures participating, and names TLV Partners as the earlier seed lead, alongside Ansa Capital.

CTech's October 13 reporting also separates the latest financing from the total and identifies the same founding team. The public figures are rounded disclosures; readers should resist turning them into an exact reconstructed capitalization history. A valuation and complete allocation of investor checks were not established in the reviewed sources.

Founded in 2025, Pluto is taking on an enterprise security purchase with a young company's resources and an expanding set of responsibilities. Product development and security research have to advance together: controls need current knowledge about what workers and agents are connecting, installing and creating. The stated US expansion adds the commercial work of getting that capability adopted by organizations with their own approval processes and existing security infrastructure.

The security decision moves inside the workflow

Pluto describes its product around discovery, contextual risk assessment and enforcement across AI tools, their components and the software employees generate. Its current website separates tools and agent sprawl, runtime actions, AI supply chains and generated artifacts. That scope follows a chain of activity rather than stopping at the name of the application an employee opened.

The company's payment-API example makes the distinction unusually easy to understand. A finance worker can use an AI coding tool to create a script, with approval required before that work accesses a payment API. This is a product illustration, not evidence about a particular customer's deployment. Its commercial relevance is the level at which the security team gets to make the decision: a permission inside the work, close to the action that could move money.

Pluto also describes controls for unsafe agent actions and untrusted components, including Model Context Protocol servers. MCP gives AI applications a way to connect with tools and data; those connections introduce access decisions of their own. The features are vendor-described capabilities, so an enterprise evaluating Pluto still needs to inspect how enforcement behaves in its environment, how exceptions get handled and how employees recover when legitimate work is interrupted.

Research becomes part of the customer relationship

Pluto's company story frames its product as a way for people to keep building while security teams retain control. That creates a demanding assignment for the founders. A security leader needs to understand the risk, explain the intervention and keep the people doing the work willing to cooperate with it.

The company is also investing in public vulnerability research, practitioner resources and Plutonium, its AI supply-chain security hub. These resources offer a route into the subject before an enterprise has chosen a commercial product. For a practitioner, a place to inspect a component can be useful on its own. For Pluto, maintaining that resource keeps the company involved in the questions security teams encounter as AI tools change.

The public launch gives some measure of the scale Pluto says it has reached. Bahat's October 13 post reports more than 1.5M secured endpoints and multi-million-dollar annual recurring revenue. Those figures are company-reported, and the number of endpoints alone says little about the quality of a particular intervention. Enterprise buyers need the connection between coverage and useful decisions: which risks were found, what policy applied and how an employee got the work completed.

Where the new capital meets the buyer

DevCuration's reporting on Ultra Security's AI runtime security seed round and Opsin's enterprise AI agent security financing provides adjacent records for readers following capital into this area. Pluto's market opportunity rests partly on a change in who makes software. A business employee who automates an awkward task is making an operating decision, even when the interface feels more like a conversation than a development environment. Security teams inherit the need to understand what that conversation produced and which systems now trust it.

Pluto's intended investment in product and research addresses different parts of that assignment. Research informs what needs attention; the product has to turn that knowledge into controls a customer can operate. US expansion then carries the proposition into purchasing discussions where a broad promise of safer AI has to become a workable deployment, with boundaries a security team can explain to the rest of the company.

The US sales effort will carry that assignment into rooms where the CISO, the people using AI and the people running the company's systems have different questions about the same deployment. Bahat, Regev and Maman are funding the product and research needed to answer them together, while the customer's employees continue finding new things to build.