Pluto Security

AI workspace security platform for enterprises to manage and protect employee-driven AI adoption.

Cover Block

From the public record

Field	Value
Name	Pluto Security
Tagline	AI workspace security platform for enterprises to manage and protect employee-driven AI adoption.
Headquarters	Tel Aviv, Israel [TechCrunch, October 2026]
Founded	2025 [Calcalist Tech, October 2026]
Stage	Series A [TechCrunch, October 2026]
Business model	SaaS
Industry	Security
Technology	AI / Machine Learning
Geography	Middle East / North Africa
Growth profile	Venture Scale
Founding team	Co-Founders (3+) [Calcalist Tech, October 2026]
Funding label	$10M+
Total disclosed funding	~$42,000,000 [TechCrunch, October 2026]

The Short Version

PUBLIC Pluto Security is building an enterprise AI workspace security platform at a moment when security teams are being forced to govern employee use of AI tools, agents, and internally built automations before standard controls have caught up [TechCrunch, October 2026] [Calcalist Tech, October 2026]. The company emerged from stealth in October 2026 with $42 million in disclosed funding, after beginning commercial sales in April 2026 and reporting more than $2 million in ARR with more than 30 enterprise customers, figures that are early but notable for a company founded in 2025 [TechCrunch, October 2026].

The founding story is straightforward and timely: Pluto was started in Tel Aviv in 2025 by Shahar Bahat, Tal Ofer Regev, and Gil Maman, with public materials also naming Noa N. as a co-founder according to LinkedIn, though that point is less broadly corroborated [Calcalist Tech, October 2026] [LinkedIn]. Its pitch is to give enterprise security teams visibility, contextual risk analysis, and real-time enforcement across AI tools, their supply chains, and employee-created applications and agents, which places the differentiation less on a general model layer and more on governance of fast-moving enterprise AI usage at the endpoint and workflow level [Calcalist Tech, October 2026] [Tokenpost].

The team reads as security-native. TechCrunch identifies Bahat as a former Palo Alto Networks employee, while external coverage links Maman to Microsoft, Palo Alto Networks, Bridgecrew, and Unit 8200, and Regev is identified publicly as co-founder and CPO [TechCrunch, October 2026] [lesechos-comfi.lesechos.fr] [LinkedIn]. That background does not by itself establish durable distribution, but it does fit the product category and helps explain the early customer access.

On capital formation, Pluto has disclosed an $8.5 million seed led by TLV Partners in 2025 and a $34 million Series A led by Jump Capital in October 2026, for roughly $42 million total disclosed funding, with backing from several cybersecurity operators and angels alongside institutional firms [TechCrunch, October 2026] [Crunchbase]. The model is standard enterprise SaaS, and the early traction claims are directionally encouraging: TechCrunch reports customers including Oscar Health, Workato, Sixt, and AlphaSense, while Calcalist reports more than 1 million endpoints secured and more than 40 enterprise customers at launch, figures that should still be treated as reported company claims rather than audited operating data [TechCrunch, October 2026] [Calcalist Tech, October 2026].

Over the next 12 to 18 months, the central questions are whether Pluto can turn stealth-launch momentum into repeatable enterprise expansion, whether the product remains credible as AI tooling changes quickly, and whether customer count translates into durable revenue depth rather than broad but shallow deployment [TechCrunch, October 2026] [iHeart]. If those pieces hold, Pluto has a plausible path into a meaningful control point for enterprise AI adoption; if they do not, the main risk is that strong early narrative and funding outpace proof of long-term platform value.

Single-source, plausible -- Core company, funding, and founder facts are corroborated by TechCrunch, Calcalist Tech, Crunchbase, and LinkedIn, but several traction and product-scope claims remain company-reported or single-source.

Taxonomy Snapshot

Axis	Value
Stage	Series A
Business Model	SaaS
Industry / Vertical	Security
Technology Type	AI / Machine Learning
Geography	Middle East / North Africa
Growth Profile	Venture Scale
Founding Team	Co-Founders (3+)
Funding	$10M+ (total disclosed ~$42,000,000)

The Company in Brief

PUBLIC Pluto Security presents as a newly formed enterprise security company built around a very specific problem: how to give security teams visibility and control as employees adopt AI tools and build their own AI-enabled workflows inside the enterprise [Crunchbase] [pluto.security, retrieved 2024]. Public company materials place the business in Tel Aviv, Israel, and Crunchbase lists the company as founded in 2025, which matters because it frames just how early this platform still is relative to the speed of customer adoption described elsewhere in public coverage [Crunchbase] [pluto.security, retrieved 2024].

The public record on legal structure is thin, so the cleaner read is to stay with what can be tied to first-party and directory sources. Pluto Security describes itself on its website as a platform for CISOs and security teams seeking to secure AI tools, supply chain components, and employee-built applications, while Crunchbase categorizes it as a cybersecurity software company and records disclosed funding activity totaling roughly $42 million across seed and Series A financing [pluto.security, retrieved 2024] [Crunchbase].

The milestone sequence visible from public company and Crunchbase materials is short but coherent. The company was founded in 2025, established a Tel Aviv base, and by the time of its current website presence had already positioned products including its core platform and the Plutonium catalog around AI component assessment and control [Crunchbase] [pluto.security, retrieved 2024]. That chronology does not by itself prove product maturity or market leadership, but it does show a company that was formed directly into the current enterprise AI security cycle rather than adapted into it later [Crunchbase] [pluto.security, retrieved 2024].

Single-source, plausible -- Confirmed primarily by Crunchbase and Pluto Security's website; no state filing or equivalent public legal-entity document was available in the cited source set.

What They Have Built

Mixed sourcing

Pluto Security is positioning around a problem that has moved from policy to tooling: employees are now building with AI inside the enterprise, and security teams need visibility before they can enforce anything. Public materials describe Pluto as an AI workspace security platform for enterprise security teams, focused on monitoring and protecting AI tools, agents, employee-built applications, and related workflows [TechCrunch, October 2026] [Calcalist Tech, October 2026]. On its website, the company frames the product as a way to help CISOs say yes to AI adoption while protecting "tools, supply chain, artifacts, and runtime," language that suggests a control plane spanning both the applications employees use and the components those applications depend on [pluto.security, retrieved 2024].

The reported feature set is relatively specific for a company only recently out of stealth. Calcalist says the platform provides endpoint visibility, contextual risk analysis, and real-time enforcement across AI tools, their supply chains, and employee-created applications, agents, and automations [Calcalist Tech, October 2026]. Additional press coverage says Pluto monitors AI tools, skills, extensions, Model Context Protocol servers, and applications built by employees, and analyzes prompts, commands, running processes, permissions, and prior activity [Tokenpost]. Taken together, that points to a product architecture anchored in endpoint and usage telemetry rather than a narrow policy dashboard, although the underlying model, deployment method, and technical stack are not described in the cited public material.

A second product surface appears to be emerging around ecosystem trust and discovery. Pluto's website and coverage reference Plutonium, a free service for assessing publicly available AI skills, connectors, and add-ons, and Tokenpost also describes an MCP scanner and a catalog of verified components [pluto.security, retrieved 2024] [Tokenpost]. Separately, founder LinkedIn activity says the company launched Market Space, a platform to discover and install secure-by-default skills, MCPs, connectors, and agents, but that claim remains company-adjacent rather than independently reported [LinkedIn]. The practical read is that Pluto may be trying to own both enforcement inside the enterprise and the discovery layer around third-party AI components, which is strategically interesting if customers increasingly treat AI connectors and agent frameworks as part of the attack surface.

Inferred, not confirmed -- Core product positioning is corroborated by TechCrunch, Calcalist Tech, and the company website, but several technical feature details rely on single-source press coverage or company-adjacent claims.

Market Size and Demand

PUBLIC

The market matters now because enterprises are moving from ad hoc employee AI use to organization-wide adoption, and that shift creates a new control problem for security teams that existing endpoint, SaaS, and application-security products do not fully map to [TechCrunch, October 2026] [Calcalist Tech, October 2026] [iHeart].

Public source coverage on Pluto does not include a third-party TAM model, so the safer way to frame the market is through adjacent categories rather than a fabricated sizing claim. The company is being positioned against enterprise spend on AI security, SaaS security posture, endpoint control, and software supply chain security, all of which sit near the workflow Pluto describes, namely visibility and enforcement across AI tools, supply chains, and employee-built applications [Calcalist Tech, October 2026] [cybercompanyprofiles.com] [pluto.security, retrieved 2024]. That does not establish a clean market boundary. It does suggest Pluto is selling into an emerging budget intersection, where buyer urgency may be real before category definitions are settled.

The demand signal in the public record is less about abstract market size and more about timing. TechCrunch reported Pluto began selling in April 2026 and had exceeded $2 million in ARR with more than 30 enterprise customers by its October 2026 financing announcement [TechCrunch, October 2026]. Calcalist Tech separately reported more than 40 enterprise customers and more than 1 million secured endpoints at stealth launch [Calcalist Tech, October 2026]. Those figures are company-reported, and the customer-count variance should be read conservatively, but together they support the narrower point: enterprises appear willing to buy security controls for employee-driven AI before the category has a mature analyst taxonomy.

A second tailwind is architectural drift inside the enterprise. Pluto's public product descriptions focus on AI tools, extensions, Model Context Protocol servers, connectors, automations, and employee-created applications, which is a broader attack surface than classic sanctioned SaaS management or developer-only application security [Calcalist Tech, October 2026] [Tokenpost] [pluto.security, retrieved 2024]. If that framing is accurate, the adjacent markets are not only AI security, but also SaaS security posture management, browser and endpoint control, developer security tooling, and software supply chain review. The practical implication is that Pluto may benefit from budget convergence, but it may also face longer evaluation cycles because buyers will compare it to several partially overlapping control stacks.

Regulation is not the central public-market argument here, but macro governance pressure is present in the background. Pluto's positioning around visibility, permissions, prompts, commands, and runtime enforcement maps to concerns that boards and security leaders already recognize: data leakage, unauthorized agent behavior, third-party connector risk, and policy enforcement over tools employees adopt faster than procurement cycles can react [TechCrunch, October 2026] [Tokenpost]. The stronger near-term driver appears operational rather than statutory. Security teams need a way to say yes to AI usage while keeping auditability and control, which is consistent with Pluto's own framing and with the customer names cited in launch coverage [pluto.security, retrieved 2024] [TechCrunch, October 2026].

Market frame	What public sources support	Evidence quality
Enterprise AI security	Pluto is described as an AI workspace security platform for enterprise security teams managing AI tools, agents, applications, and workflows [TechCrunch, October 2026] [Calcalist Tech, October 2026]	YELLOW
Adjacent endpoint and runtime control	Coverage cites endpoint visibility and real-time enforcement across AI tools and employee-created applications [Calcalist Tech, October 2026]	YELLOW
Adjacent software supply chain security	Public materials reference securing AI supply chains, connectors, add-ons, and MCP components [pluto.security, retrieved 2024] [Tokenpost]	ORANGE
Substitute SaaS and app governance spend	Inference from Pluto's focus on employee-adopted tools and business workspaces, compared with existing SaaS governance workflows [cybercompanyprofiles.com] [pluto.security, retrieved 2024]	ORANGE

The table makes the main point cleanly: the public evidence supports a live enterprise pain point, but not a settled market map. For investors, that usually means category formation risk is real, even when early budget availability appears encouraging.

Inferred, not confirmed -- Section relies on named public reporting for demand signals and product scope, but no independent third-party market sizing or analyst category data was identified in the cited sources.

Who Else Is Fighting for This

MIXED Pluto Security is positioning itself in the narrow but increasingly relevant gap between traditional endpoint control and the newer problem of employee-built AI workflows, but the public record here is still thinner on named rivals than on the company’s own framing of the category [TechCrunch, October 2026] [Calcalist Tech, October 2026].

The public evidence supports three competitive buckets, even without a clean vendor set named in the source pack. The first is incumbent enterprise security tooling, especially endpoint and broader security-control stacks that already sit with the buyer Pluto appears to target, namely security teams responsible for AI, application, and software supply chain risk [TechCrunch, October 2026] [cybercompanyprofiles.com]. Those incumbents have the distribution advantage because they already own budget lines, deployment channels, and policy surfaces inside large enterprises, but the available reporting does not show them as purpose-built for monitoring prompts, Model Context Protocol servers, employee-created agents, or no-code automations at the level Pluto describes [Calcalist Tech, October 2026] [Tokenpost].

The second bucket is AI-native security challengers. Latio appears in the record not as a direct operational benchmark but as a market-map publisher that identified Pluto as an endpoint AI security leader, which at minimum places Pluto inside an emerging peer set of vendors focused on AI-specific exposure rather than legacy endpoint telemetry alone [latio.com] [Pluto Security blog]. The third bucket is adjacent substitutes, including internal security engineering efforts and policy-led governance programs that enterprises may use instead of buying a dedicated platform. That substitute set matters because Pluto began selling only in April 2026, according to TechCrunch, which suggests it is still competing not just against vendors but against the common enterprise instinct to extend existing tools first [TechCrunch, October 2026].

Pluto’s clearest edge today is product alignment with a problem that is arriving faster than formal procurement cycles. Multiple sources describe the platform as providing endpoint visibility, contextual risk analysis, and real-time enforcement across AI tools, supply-chain components, and employee-created applications or agents, which is more specific than a generic "AI security" label and likely resonates with CISOs trying to monitor unsanctioned builder activity across coding assistants, connectors, and automations [Calcalist Tech, October 2026] [TechCrunch, October 2026] [Tokenpost]. The early commercial signal is notable if taken conservatively: TechCrunch reported more than 30 enterprise customers and more than $2 million in ARR by October 2026, while Calcalist reported more than 40 enterprise customers and more than 1 million secured endpoints at stealth launch [TechCrunch, October 2026] [Calcalist Tech, October 2026]. That edge is promising but perishable. If the differentiation rests on speed of category formation and telemetry across fast-changing AI tools, then larger security vendors with existing enterprise distribution could narrow the gap quickly once demand settles into a standard feature checklist.

The exposure is less about an identified direct rival and more about channels Pluto does not yet appear to own in public reporting. There is no disclosed evidence here of a major reseller network, a bundled distribution partner, or a platform dependency that would make Pluto hard to displace once a broader endpoint or cloud security suite adds similar controls [TechCrunch, October 2026] [Calcalist Tech, October 2026]. Even Plutonium, the company’s free service for assessing public AI components and MCP-related assets, reads as a useful top-of-funnel and ecosystem signal, but the public sources do not yet establish that it creates a proprietary data moat or an embedded developer distribution loop strong enough to keep rivals out [pluto.security, retrieved 2024] [Tokenpost]. The strongest named external actor in the source set is not a competitor but the incumbent ecosystem around Palo Alto Networks talent and security buyers, which cuts both ways: it helps founder credibility, but it also highlights how easily a scaled incumbent could contest the same account base if the feature set proves tractable [TechCrunch, October 2026].

The most plausible 18-month scenario is a land-grab in which the winners are the vendors that translate AI-workspace security from a novel control plane into an operational standard tied to existing security workflows. Pluto is a credible winner if enterprise demand keeps moving from shadow AI discovery toward active enforcement on employee-built agents, connectors, and automations, because that is where its public product description is most concrete today [Calcalist Tech, October 2026] [TechCrunch, October 2026]. The loser if that shift does not happen is likely the broader class of AI-security specialists represented in market maps such as Latio’s, Pluto included, because the budget could remain with incumbents and internal teams if buyers decide this problem can be handled as an extension of existing endpoint, governance, or application security tooling rather than a standalone platform [latio.com] [Pluto Security blog].

Single-source, plausible -- Competitive framing is supported by TechCrunch, Calcalist Tech, Pluto’s website, Tokenpost, and Latio-related references, but the source set does not name verified direct competitors beyond market-map context, so parts of the landscape analysis remain inference-based from public product positioning.

Opportunity

Upside case

PUBLIC The prize here is not a point solution for AI policy enforcement, but a chance to become the control layer enterprises use to see, assess, and govern the fast-growing sprawl of employee-built AI tools, agents, and automations, a market opening that has appeared quickly enough for an early entrant to matter [TechCrunch, October 2026] [Calcalist Tech, October 2026].

The headline opportunity is straightforward. If Pluto Security can turn its early foothold in endpoint visibility, contextual risk analysis, and real-time enforcement into a durable system of record for enterprise AI usage, it could plausibly become default infrastructure for AI workspace security across large organizations [Calcalist Tech, October 2026]. That outcome is reachable, not merely aspirational, because the company appears to have found early commercial pull unusually quickly: TechCrunch reported Pluto began selling in April 2026, had already exceeded $2 million in ARR, and had more than 30 enterprise customers by its October 2026 emergence from stealth [TechCrunch, October 2026]. The same launch window also produced reported customer references including Oscar Health, Workato, Sixt, and AlphaSense, which matters less as logo theater than as evidence that the product is being tested in live enterprise environments rather than design-partner limbo [TechCrunch, October 2026] [daily.dev].

The path to scale depends on how Pluto converts an urgent detection problem into broader control, workflow, and procurement gravity. Its own positioning is broad enough to support that expansion: the company describes protection across AI tools, supply chain components, artifacts, and runtime, while public coverage describes monitoring of employee-created applications, agents, automations, and Model Context Protocol servers [pluto.security, retrieved 2024] [Calcalist Tech, October 2026] [Tokenpost]. In practice, that gives Pluto several shots on goal. It can start with visibility, move into enforcement, and then potentially become the approved distribution layer for safer AI components through Plutonium and its catalog of verified components, if those surfaces gain adoption inside customer workflows [pluto.security, retrieved 2024] [Tokenpost].

Scenario	What happens	Catalyst	Why it's plausible
Land-and-expand into enterprise AI governance	Pluto starts as an endpoint and workspace visibility tool, then expands into policy enforcement across tools, agents, and employee-built apps inside large enterprises	Enterprise security teams need a single control plane as AI usage shifts from shadow adoption to sanctioned deployment [iHeart]	Pluto already sells to enterprise security teams and reported more than 30 customers within months of beginning sales, with named accounts including Oscar Health and Workato [TechCrunch, October 2026]
Become the trusted supply chain layer for AI components	Plutonium, the MCP scanner, and verified-component catalog become the approved screening and discovery layer for skills, connectors, add-ons, and agents before they are used inside enterprises	The rise of reusable AI components increases the need for pre-deployment assessment and curation [Tokenpost]	Pluto already operates a free assessment and catalog product, which gives it a public-facing entry point beyond direct sales [pluto.security, retrieved 2024] [Tokenpost]
Standardize security around citizen-built AI	Pluto becomes the default security product for no-code builders, coding copilots, and agentic app creation inside enterprises, especially where employees can deploy tools faster than central IT can review them	Employee-built AI moves from ad hoc experimentation to a budgeted enterprise workflow, increasing demand for continuous oversight [TechCrunch, October 2026] [Calcalist Tech, October 2026]	The company's product scope is already framed around employee-created applications, automations, and AI tools, which aligns with that adoption pattern [Calcalist Tech, October 2026]

What compounding looks like is less a consumer-style network effect and more a security data and workflow flywheel. Each deployment should increase Pluto's visibility into which AI tools, extensions, connectors, prompts, commands, and permissions actually appear inside enterprise environments, and that in turn can improve risk analysis, policy coverage, and the usefulness of any verified catalog or scanner the company maintains [Tokenpost] [Calcalist Tech, October 2026]. If Plutonium becomes a habitual destination for evaluating AI components, Pluto could benefit twice: first as a lead-generation surface, second as a feedback loop that strengthens product intelligence around the long tail of workplace AI usage [pluto.security, retrieved 2024]. The early signs are still company-shaped rather than independently audited, but the reported combination of more than 1 million secured endpoints and more than 40 enterprise customers suggests enough installed surface area for that data loop to begin, if those numbers hold up over time [Calcalist Tech, October 2026].

The size of the win is best framed conditionally, because no public market or M&A benchmark in the supplied source set provides a clean valuation anchor for this exact category. Even so, the disclosed inputs support an ambitious scenario. Pluto raised $42 million in total by October 2026, including a $34 million Series A led by Jump Capital, after reportedly surpassing $2 million in ARR within roughly six months of starting sales in April 2026 [TechCrunch, October 2026]. If the company were to convert that start into a broad enterprise control platform for AI workspaces, the outcome could support a multibillion-dollar enterprise value (scenario, not a forecast), not because the current figures justify that valuation today, but because security platforms that become default systems of record for a new enterprise risk layer tend to expand far beyond their initial compliance or monitoring wedge. Here, the optimistic case rests on Pluto owning a new control point before enterprise AI usage patterns harden around incumbent tooling [TechCrunch, October 2026] [Calcalist Tech, October 2026].

Single-source, plausible -- This section relies primarily on TechCrunch and Calcalist Tech, with additional product detail from Pluto's website and Tokenpost. Several traction and product-scope claims remain company-reported or lightly corroborated.

Sources