All analysis was generated autonomously, without human review. Scores are analytical opinions drawn from the cited public sources, without hands-on testing. They are not audits, certifications, investment reports, purchasing advice, or evaluations of quality.
Lumeus sold security for AI coding agents to the enterprise security and platform teams that govern them. It shipped a code-editor extension and an endpoint proxy over editor and command-line traffic, a gateway for Model Context Protocol (MCP) sessions, and short-lived credentials in place of long-lived secrets. Fiddler AI bought the company in April 2026. Four months on, lumeus.ai no longer loads. What the reviewed record still reaches is a Visual Studio Code Marketplace listing reporting 166 installs, whose setup notes still send new users to lumeus.ai for onboarding. Fiddler's June 2026 coding-agent announcement describes a product that attaches to a gateway the customer already runs. Neither that announcement nor Fiddler's control-plane page names Lumeus.
| Description | Security platform for AI coding agents and developers that discovers agent and MCP activity across IDEs and CLIs, enforces enterprise policy through an MCP proxy, and replaces standing infrastructure credentials with just-in-time access. Fiddler AI acquired the company in April 2026. | [f1] |
|---|---|---|
| Acquisition | Fiddler AI, announced 2026-04-10 | [f2] |
| Founded | 2021 | [f3] |
| HQ | San Jose, California | [f3] |
| Funding | $6M total | [f4] |
| Latest funding | Seed ($6M, announced May 2023) | [f5] |
| Product | What it does |
|---|---|
| Lumeus | IDE and CLI plugins plus an MCP proxy that discover coding-agent activity, enforce enterprise policy at the agent edge, audit sessions, and replace standing credentials with just-in-time access. |
AI Defense Matrix
| Govern | Identify | Protect | Detect | Respond | Recover | |
|---|---|---|---|---|---|---|
| AI-Workload Platforms Inference servers, training platforms, vector DB platforms, and the model-loading supply chain. | ||||||
| AI Orchestration Tools Agentic orchestration tools, plus their plugins, skills, hooks, system prompts, scaffolding, harnesses, configuration settings, and MCP clients on user devices. | ||||||
| AI-Generated Code Code produced by AI tools, AI-assisted reviews, AI-generated infrastructure-as-code and tests, and vibe-coded apps that bypass CI/CD. | ||||||
| AI Gateways & Routers MCP proxies and gateways, LLM routers, outbound AI-service traffic, shadow AI egress, and model-registry traffic. | ||||||
| AI Model Model weights, fine-tuning checkpoints, model cards, registries, AIBOM, and the third-party LLMs your enterprise consumes. | ||||||
| Training Data Datasets used for training, fine-tuning, and continued learning. | ||||||
| Runtime AI Data User prompts, inference inputs, RAG content, vector DB content, persistent agent memory, and interaction history. | ||||||
| AI Agent Identities AI agents as non-human principals, plus credentials, keys, permission scopes, service accounts, and delegation chains across agents and tools. |
Lumeus inspects communications between IDE and CLI agents and external MCP servers, blocks unsanctioned MCP servers, applies Layer 7 inspection for prompt injection and data leaks, and issues ephemeral credentials. These capabilities are mapped to the AI Defense Matrix. [f1]
Cyber Defense Matrix
| Identify | Protect | Detect | Respond | Recover | |
|---|---|---|---|---|---|
| Devices Workstations, servers, phones, tablets, storage, network devices, IoT infrastructure, and similar hardware. | |||||
| Applications Software, interactions, and application flows on the devices. | |||||
| Networks Connections and traffic flowing among devices and apps, plus communication paths. | |||||
| Data Content at rest, in transit, or in use across devices, apps, and networks. | |||||
| Users The people using the devices, apps, networks, and data. |
Lumeus provides just-in-time access to SSH servers, Kubernetes clusters, databases, and web applications, integrates with reverse proxies such as Teleport, and replaces long-lived secrets with ephemeral credentials. These capabilities are mapped to the Cyber Defense Matrix. [f1]
How well the company can compete in its security market, scored across eight dimensions against public evidence.
| Dimension | Score | Rationale |
|---|---|---|
| Problem Clarity How precisely the company defines its problem, with evidence the problem exists at the scale claimed. | 3/5 | Lumeus named a concrete buyer problem, ungoverned AI coding agents and MCP servers reaching company code and credentials, and an independent analyst profile describes its target as enterprise organizations managing multiple AI agents in compliance-sensitive environments. The urgency figures in the reviewed record arrive through the acquirer's own announcement rather than through buyer-side research captured here, so the pain is credible and stated by interested parties. [s2, s11, s5] |
| Capability Depth How specific the technical capabilities are, with evidence beyond marketing claims such as docs and third-party validation. | 3/5 | The Visual Studio Code Marketplace listing carries concrete architecture, a local policy enforcement point acting as a forward HTTP proxy over editor and command-line traffic, an MCP gateway that blocks unsanctioned servers, and just-in-time provisioning for SSH servers, Kubernetes clusters, and databases. What keeps the score here is that no third-party technical evaluation of the product appears in the reviewed sources, and the company's own documentation site no longer serves. [s5, s11, s1] |
| Market Timing Whether the market is ready for this product, with evidence that buyers are actively seeking solutions. | 3/5 | Enterprise adoption of AI coding agents is the enabler, dated by Fiddler's April 2026 announcement that it bought policy enforcement at the code generation layer and by its June 2026 product announcement for coding agents. Buyer-side demand in the reviewed record runs through one kind of signal, an acquirer's purchase, rather than several independent kinds, and no dated buyer-side research appears here in its own voice. [s2, s3] |
| Team Credibility Demonstrated domain expertise with public signals such as prior exits, publications, and industry recognition. | 2/5 | SiliconANGLE's launch coverage names co-founder and chief executive Satish Veerapuneni alongside co-founder Saurabh Jain and quotes Veerapuneni on the platform, so both founders are publicly identifiable. Weighed against that, the reviewed sources carry no earlier build, exit, publication record, or independent recognition for either founder, and the sale to Fiddler is an outcome of this company rather than prior track record. [s6, s7, s10] |
| GTM Proof Evidence of actual traction (customers, revenue signals, partnerships) beyond stated intentions. | 3/5 | The Visual Studio Code Marketplace carries a Lumeus extension published under the Lumeus.ai name, reporting 166 installs, and that listing carries the one adoption number in the reviewed record. Scale stops there. No named customer, case study, or partnership appears in those sources, and Fiddler's announcement refers to Lumeus customers only in the aggregate. [s5, s2] |
| Funding Efficiency Whether funding matches go-to-market ambition, with signs of capital-efficient growth. | 3/5 | Lumeus announced a $6 million seed in 2023, and the reviewed record then shows it repositioning from zero-trust networking to coding-agent security before Fiddler acquired it in April 2026. That raise is proportional to stage and motion with visible shipping. Efficiency itself stays unconfirmed, because no sale price appears in the reviewed sources, and no revenue, margin, or growth figure appears there either. [s6, s2, s7] |
| Category Clarity Whether the company creates or fits a recognizable category that buyers can quickly place in their stack. | 3/5 | Lumeus sits in the market for governing MCP traffic and coding agents, which a competing vendor's roundup describes as commonly served by an MCP proxy inside a gateway. Placement still needs explaining. That roundup does not name Lumeus, an analyst profile files the company under AI Security as a zero-trust gateway for GenAI and cloud access, and Lumeus itself moved off zero-trust networking within three years. [s12, s11, s6] |
| Incumbent Defensibility How vulnerable the core value proposition is to absorption as a feature by a platform vendor. | 2/5 | Fiddler, an adjacent vendor selling production monitoring for AI, bought Lumeus in April 2026 to extend its control plane to the code generation layer, which is what absorption by an adjacent platform looks like. The reviewed sources do not yet show that enforcement as a shipped feature of an incumbent stack, since Fiddler was recruiting design partners for access before general availability and a competing vendor's comparison page states the acquired capability had no product documentation. Nothing in those sources shows accumulated data or workflow depth that bundling would not reach. [s2, s3, s13] |
Lumeus ended its independent run selling against a different problem than the one it was funded for. SiliconANGLE's launch coverage identifies the company as Okulis Inc. and reports a $6 million seed for zero-trust networking, and the accompanying release describes a July 2021 founding in San Jose and a platform for IT and security teams modernizing network security.
By the April 2026 sale the problem statement had moved to AI coding agents. Fiddler's announcement describes agents that write code, call tools, and take autonomous actions, and states that Lumeus customers could enforce policy where coding agents operate but could not extend beyond the development environment. An analyst profile puts the target audience more precisely, naming enterprise organizations that manage multiple AI agents across interfaces and work in compliance-sensitive environments.
The reviewed record carries the problem mainly in interested voices. The adoption and secret-leakage figures Fiddler cites reach the reviewed record through Fiddler's own posts rather than through the underlying research, and no named buyer quantifies the pain in the reviewed sources. [s6, s7, s2, s11, s3]
The product enforced policy inside the developer's own tools rather than in the network core. Its Visual Studio Code Marketplace listing describes a lightweight endpoint agent acting as a forward HTTP proxy over editor and command-line web traffic, with more than thirty parsers for editor and command-line agents, developer software-as-a-service applications, and consumer AI services, plus Layer 7 inspection for prompt injection and data leaks. A Model Context Protocol gateway inspects communications between those agents and external MCP servers and blocks unsanctioned servers.
A second capability line covered infrastructure access. The same listing describes just-in-time provisioning for SSH servers, Kubernetes clusters, databases, and web applications, ephemeral credentials that expire automatically, and integration with reverse proxies such as Teleport. Repository governance adds git blocking and allowlist controls over code access, and enterprise rollout runs through installation scripts for Windows, macOS, and Linux across VS Code, Cursor, and Windsurf.
What a buyer can still inspect is thin. The company's own site no longer serves, so the marketplace listing is the sole reachable vendor documentation in the reviewed record, and no third-party technical evaluation of the product appears in those sources. Speakeasy, a competing vendor, states on its comparison page that the acquired capability had no product documentation in Fiddler's docs as of its writing. [s5, s11, s1, s13]
Lumeus competed for control of MCP traffic and coding agents. A competing MCP-security vendor's 2026 roundup describes the MCP proxy, usually a component of an MCP gateway, as the most common form of MCP security tool, and that roundup does not name Lumeus.
Where the software ran was the differentiator. Instead of a central gateway alone, Lumeus placed enforcement inside code editors and command-line tools and carried its networking heritage into just-in-time infrastructure access. The acquisition settled the competitive question, and a trade article covering the deal describes the combination as Lumeus policy enforcement at the code generation stage joined to Fiddler production-level monitoring.
What Fiddler shipped afterwards does not carry the Lumeus name. Its June 2026 coding-agent announcement describes a control plane that integrates inline with the gateway a customer already runs, with no new gateway and no agent rewrites, and its control-plane page says enforcement extends to the editor, command-line, and MCP boundary. Neither of those pages names Lumeus. [s12, s5, s10, s3, s4]
Public traction evidence is the thinnest part of the record. No named customer, case study, or partnership appears in the reviewed sources, and Fiddler's announcement refers to Lumeus customers only in the aggregate, noting they could enforce policy where coding agents operate but not beyond the development environment.
One adoption signal carries a number. The Visual Studio Code Marketplace lists the Lumeus extension under the publisher name Lumeus.ai and reports 166 installs. The listing's prerequisites state that a valid Lumeus tenant must be provisioned and organizational resources configured, so the extension is a client for a tenant an administrator arranges rather than a self-service product.
The commercial outcome on the record is the sale itself. Fiddler acquired the company in April 2026 with no sale price in the reviewed sources, and was recruiting design partners for hands-on access before general availability of the combined coding-agent product. [s2, s5]
The founding team is publicly identifiable but thinly documented. Satish Veerapuneni, co-founder and chief executive, and co-founder Saurabh Jain started Lumeus to help distributed enterprises modernize network security while leveraging existing infrastructure, and SiliconANGLE's launch coverage names both and quotes Veerapuneni on what the platform managed from one console.
Prior track record is what the sources do not carry. No earlier exit, publication record, or independent recognition for either founder appears in the reviewed sources, and investor endorsement is the main external signal, with Tola Capital leading the seed alongside Emergent Ventures and First Rays Ventures.
The sale to Fiddler is this team's earliest documented outcome. A trade article says the deal brings together the expertise of Krishna Gade and Satish Veerapuneni, and Fiddler's announcement lists Veerapuneni under his Lumeus title. Neither states a role for either founder inside Fiddler. [s6, s7, s9, s10, s2]
Nothing about the compliance posture can be checked in the reviewed record. No attestation, audit report, or trust page for Lumeus appears in those sources, the company's own domain no longer serves a site, and no trust or security host answers on it. A security review of this product would have no attestation to examine.
The product argued trust through auditability instead. The marketplace listing describes session monitoring with complete audit trails, tamper-resistant enforcement with uninstall protection, and repository access controls with allowlist management, and an analyst profile names MCP proxy enforcement with full auditability among the capabilities. How the compliance posture carries forward under Fiddler is not addressed in the reviewed sources. [s1, s5, s11, s2]
| Company | Relationship | Note | Compare |
|---|---|---|---|
| Golf | competes with | Competes for the MCP governance and credential-brokering budget Lumeus addressed. | N/AWe captured the evidence for these companies under different evidence-model versions (v1 vs v2), so the totals were scored under different conditions and are not directly comparable. |
| MintMCP | competes with | Competes for the governed-access position over agent tool calls that Lumeus occupied. | N/AWe captured the evidence for these companies under different evidence-model versions (v1 vs v2), so the totals were scored under different conditions and are not directly comparable. |
| Archestra | competes with | Competes for the same MCP traffic-control point. | |
| Autonomous Security | competes with | Contests the same coding-agent security budget. | N/AWe captured the evidence for these companies under different evidence-model versions (v1 vs v2), so the totals were scored under different conditions and are not directly comparable. |
| Backslash Security | competes with | Overlaps the coding-agent governance Lumeus sold into code editors. | N/AWe captured the evidence for these companies under different evidence-model versions (v1 vs v2), so the totals were scored under different conditions and are not directly comparable. |
Add analyzed competitors to compare them side by side with Lumeus.
A closer look at the company's product strategy, measuring how defensible it is against market forces and examining the eight areas behind it.
pivot urgently
Lumeus held customers through where its software sat rather than through anything it accumulated. The product ran as an endpoint agent and forward proxy inside the developer's own tools, mediating MCP sessions and issuing short-lived credentials for SSH servers, Kubernetes clusters, and databases. Unwinding that deployment takes work, though nothing in the reviewed sources sizes what leaving would cost. No named deployment, no inspectable audit report, and no vendor-retained dataset appears in those sources. Fiddler AI, which sells monitoring for AI systems in production, says it acquired Lumeus to extend its control plane to the code generation layer.
| Dimension | Score | Rationale |
|---|---|---|
| Value Delivery Does the product sell software as the product, or judgment, trust, or accountability with software as the delivery mechanism. | 1/3 | Lumeus sold software the customer installs and runs, an editor extension, a forward proxy, and a credential gateway, with the buyer paying for those capabilities rather than for a judgment or accountability layer. The reviewed sources describe no human-expertise delivery alongside the software. |
| Switching Cost How expensive leaving is for a customer: data portability, integrations, learned workflows, network effects, regulatory data residency. | 2/3 | Routing editor and command-line traffic through the endpoint proxy, mediating MCP sessions, and moving SSH, Kubernetes, and database access onto ephemeral credentials creates meaningful friction to unwind. The switching mechanism is documented and the cited record does not size the migration, naming no exit duration, no multi-party transfer, and no relearning interval. |
| Compliance Moat Whether certifications, liability acceptance, or audit trails block an easy replacement. | 1/3 | No attestation, audit report, or trust page for Lumeus appears in the reviewed sources, and no host answers on the company's trust or security subdomains. The reviewed sources document no regulation-specific mandate blocking a replacement for this product class, so nothing here stops a funded competitor from ordinary enterprise-market preparation. |
| Problem Complexity Whether the product requires ML, optimization, real-time systems, or years of specialized expertise. | 3/3 | Layer 7 inspection of editor and command-line traffic across more than thirty parsers, real-time mediation of MCP sessions, ephemeral credential issuance for SSH servers, Kubernetes clusters, and databases, and tamper-resistant enforcement with watchdog health checks are real-time systems engineering well beyond forms and dashboards. |
| Buyer Profile Whether buyers are SMB operators, mid-market IT teams, or regulated enterprises and governments with procurement gates. | 2/3 | An analyst profile describes the target as enterprise organizations in compliance-sensitive environments, and the listing requires an administrator-provisioned tenant, which points above the small-business floor. No named regulated enterprise or government buyer of this product appears in the reviewed sources, so the evidenced buyer class stops at organizations with IT governance. |
| Layer Whether the product is an end-user application, a platform with application features, or infrastructure other applications depend on. | 2/3 | The endpoint proxy and MCP gateway carry agent traffic and infrastructure access while deployed, which is a platform-like position. The listing describes uninstall protection rather than application dependency, and nothing in the reviewed sources shows other applications requiring Lumeus to run. |
| Proprietary Data, Content, or IP Whether the product accumulates datasets, content licenses, or IP that a rival cannot recreate from scratch. | 1/3 | No named dataset, content licence, or granted patent appears in the reviewed sources. What the record evidences is software the vendor wrote, its parsers and policy machinery, and the cited sources do not establish a vendor-retained or cross-customer data asset. |
Lumeus targeted enterprises adopting AI coding agents and sold to the teams that govern them. An analyst profile names enterprise organizations that manage multiple AI agents across different interfaces, particularly those in compliance-sensitive environments requiring unified multi-agent governance. Fiddler's announcement addresses the same audience when it invites CISOs, CIOs, and platform leaders deploying coding agents at scale into its design-partner program.
A second segment sat closer to the company's networking roots. The marketplace listing describes just-in-time provisioning for SSH servers, Kubernetes clusters, databases, and web applications, which addresses organizations whose infrastructure, not only whose developers, needed governed access.
No named customer defines either segment in the reviewed sources, so the buyer is described rather than demonstrated. The listing's prerequisite that a valid Lumeus tenant be provisioned and organizational resources configured puts an administrator between a developer and the product, which fits a top-down enterprise sale rather than developer self-service.
The differentiating claim was position rather than proprietary AI. The extension acts as a local policy enforcement point over editor and command-line web traffic, with more than thirty parsers and Layer 7 inspection for prompt injection and data leaks, and a Model Context Protocol gateway inspects agent-to-server communications and blocks unsanctioned servers.
The reviewed sources describe no proprietary model, dataset, or detection corpus behind those capabilities, so what a rival would have to reproduce is engineering rather than an accumulated asset. Guardrail enforcement and threat detection appear as product claims on a vendor-published listing, without technical documentation, open code, or third-party evaluation in those sources.
The credential system is careful engineering described without a novelty claim the record could test. Ephemeral credentials expire automatically and replace long-lived secrets across SSH servers, Kubernetes clusters, and databases, and the listing pairs that with complete audit trails and real-time session monitoring.
Lumeus ran an enterprise motion with thin public proof of conversion. Fiddler's announcement refers to Lumeus customers without naming any, and no case study or partnership appears in the reviewed sources.
One number in the record comes from the Visual Studio Code Marketplace. The Visual Studio Code listing published under the Lumeus.ai name reports 166 installs, while its prerequisites require a provisioned Lumeus tenant, so installs do not stand in for paying deployments.
The seed round remains the strongest external endorsement of the go-to-market. Tola Capital led $6 million in 2023 with Emergent Ventures and First Rays Ventures, raised for the earlier networking product, and the agent-security repositioning reached its commercial outcome through the April 2026 sale rather than through disclosed traction.
The reviewed sources disclose no pricing for the Lumeus tenant that the marketplace listing requires. That listing routes onboarding through a provisioned tenant, and no price list, plan tier, or unit of charge for the platform appears in those sources.
What the record shows about packaging stops at the product's shape. Central policy control, repository governance, and audit trails are administered for an organization rather than per developer, which could support centralized enterprise packaging. The reviewed sources demonstrate neither purchasing behaviour nor pricing power, and they do not document post-acquisition packaging.
How the acquired capability is charged under Fiddler is not stated in the reviewed sources. Fiddler's April 2026 announcement offered design partners hands-on access before general availability, which is an access program rather than a price.
Delivery rode inside the customer's existing developer and infrastructure surfaces. The extension installs into VS Code, Cursor, and Windsurf through automated scripts for Windows, macOS, and Linux, with centralized credential configuration for managed deployments, so rollout happens machine by machine under administrator control.
Infrastructure access runs through the same client. Just-in-time provisioning covers SSH servers, Kubernetes clusters, databases, and web applications, and the listing describes integration with reverse proxies such as Teleport alongside configurable on-premise deployment.
Operational commitments are absent from the record. Uptime commitments, support tiers, and upgrade responsibilities appear nowhere in the reviewed sources, so the reviewed record gives a buyer no service level to hold anyone to.
The trust posture cannot be checked in the reviewed record. No attestation, audit report, or trust page for Lumeus appears in those sources, the company's own domain no longer serves a site, and no trust or security host answers on it. For a product that mediates agent traffic and issues infrastructure credentials, a posture nobody can inspect is a problem a security review would raise.
The product argued trust through auditability instead. Complete audit trails with real-time session monitoring, tamper-resistant enforcement with uninstall protection, and repository access controls with allowlist management are marketed capabilities on the listing, and an analyst profile names MCP proxy enforcement with full auditability among them. SiliconANGLE identifies the operating company as Okulis Inc., and the reviewed sources do not disclose which entity carries product contract accountability now.
Lumeus positioned itself between developer tools and enterprise security systems. It plugged into the editors and command-line tools where agents run, mediated local and remote MCP servers through its gateway, and integrated with reverse proxies such as Teleport for SSH, Kubernetes, and web cluster access.
That in-between position is also what made the company absorbable. The MCP proxy pattern it sold is, per a competing vendor's roundup, the most common form of MCP security tool, and Fiddler acquired the company that sold it.
The acquisition folded that position into a larger platform. Fiddler joined policy enforcement at the code generation stage to its own production-level monitoring, and its control-plane page says enforcement extends to the editor, command-line, and MCP boundary with human approval required for high-risk decisions.
The company was founder-led from its 2021 start to its 2026 sale. Satish Veerapuneni, co-founder and chief executive, and co-founder Saurabh Jain started Lumeus to help distributed enterprises modernize network security while leveraging existing infrastructure, and built it from San Jose after a July 2021 founding.
Public signals about the team are thin. The reviewed company, funding, and acquisition sources document no earlier exit, publication record, or independent recognition for either founder, and the strongest external endorsements are the investors who led and joined the seed round.
The pivot is the team's most telling public act. A company that launched an agentless zero-trust networking platform in 2023 shipped an agent-security product that Fiddler acquired within three years. A trade article says the deal brings together the expertise of Krishna Gade and Satish Veerapuneni, and Fiddler's announcement still lists Veerapuneni under his Lumeus title. The reviewed sources do not describe his role inside Fiddler, or Saurabh Jain's role after the deal.
| Id | Source | Tier | Accessed |
|---|---|---|---|
| f1 | Visual Studio Code Marketplace: Lumeus extension listing published by Lumeus.ai | official | 2026-08-30 |
| f2 | Fiddler AI blog: Fiddler Acquires Lumeus to Extend the AI Control Plane to Coding Agents (published April 10, 2026) | official | 2026-08-30 |
| f3 | Tech Funding News: Lumeus.ai launches its zero trust network (May 2023) | press | 2026-07-03 |
| f4 | Business Wire (vendor press release): Visibility-First Zero Trust Networking Platform Lumeus.ai Launches With $6M Seed | official | 2026-07-03 |
| f5 | SiliconANGLE: Lumeus.ai raises $6M to enable universal zero-trust security across clouds and on-premises data centers (May 18, 2023) | press | 2026-07-03 |
| Id | Source | Tier | Accessed |
|---|---|---|---|
| s1 | Probe of lumeus.ai on 2026-08-30: HTTPS fails, plain HTTP returns an error, and no trust, security or app host resolves (nonsense control also absent) | official | 2026-08-30 |
| s2 | Fiddler AI blog: Fiddler Acquires Lumeus to Extend the AI Control Plane to Coding Agents “We are excited to share that Fiddler has acquired Lumeus, the solution for agent posture management, policy enforcement, and security at the code generation layer.” | official | 2026-08-30 |
| s3 | Fiddler AI blog: Fiddler AI Control Plane for Coding Agents, a product announcement “A control plane for coding agents observes every agent request and enforces policy inline - before data leaves the network - across every agent, gateway, and model provider an organization runs.” | official | 2026-08-30 |
| s4 | Fiddler AI: Control Plane for Agents product page “Enforcement extends to the IDE, CLI, and MCP boundary, with human approval required for high-risk decisions.” | official | 2026-08-30 |
| s5 | Visual Studio Code Marketplace: Lumeus extension listing published by Lumeus.ai “Lumeus.ai
|
166 installs” | official | 2026-08-30 |
| s6 | SiliconANGLE: Lumeus.ai raises $6M to enable universal zero-trust security across clouds and on-premises data centers “Zero-trust networking startup Lumeus.ai , officially known as Okulis Inc., is launching today armed with $6 million in seed funding.” | press | 2026-08-30 |
| s7 | Business Wire (vendor press release): Visibility-First Zero Trust Networking Platform Lumeus.ai Launches With $6M Seed “Founded in July 2021 and based in San Jose, CA, Lumeus.ai is a visibility-first Zero Trust networking platform that helps IT and Security teams modernize network security.” | official | 2026-08-30 |
| s8 | Tech Funding News: With $6M seed funding, Lumeus.ai launches its visibility-first zero trust network “The startup was founded in July 2021 and headquartered in San Jose, CA.” | press | 2026-08-30 |
| s9 | The SaaS News: Lumeus.ai Raises $6 Million in Seed Round “The round was led by Tola Capital, with participation from esteemed pre-seed investors Emergent Ventures and First Rays Ventures.” | press | 2026-08-30 |
| s10 | CXO Digitalpulse: Fiddler AI Expands AI Governance Stack with Lumeus.ai Acquisition “The integration combines Lumeus.ai’s upstream policy enforcement at the code generation stage with Fiddler AI’s production-level monitoring.” | press | 2026-08-30 |
| s11 | IT-Harvest Guardians of the Machine Age: Lumeus AI vendor profile “Lumeus AI provides AI-native security for modern development teams, focusing on protecting AI coding workflows, MCP protocols, and infrastructure access.” | research | 2026-08-30 |
| s12 | MCP Manager (a competing MCP-security vendor): The Best MCP Security Tools 2026 roundup “The most common form of MCP security tool is an MCP proxy , which typically sits inside (and is a component) of an MCP gateway .” | official | 2026-08-30 |
| s13 | Speakeasy (a competing vendor): In depth, Speakeasy vs Fiddler AI comparison page “Its April 2026 acquisition of Lumeus.ai markets policy enforcement at the IDE, CLI, and MCP boundary for coding agents, but that capability is weeks old and not yet in Fiddler's product documentation.” | official | 2026-08-30 |
| Id | Source | Tier | Accessed |
|---|---|---|---|
| s1 | Probe of lumeus.ai on 2026-08-30: HTTPS fails, plain HTTP returns an error, and no trust, security or app host resolves (nonsense control also absent) | official | 2026-08-30 |
| s2 | Fiddler AI blog: Fiddler Acquires Lumeus to Extend the AI Control Plane to Coding Agents “We are excited to share that Fiddler has acquired Lumeus, the solution for agent posture management, policy enforcement, and security at the code generation layer.” | official | 2026-08-30 |
| s3 | Fiddler AI blog: Fiddler AI Control Plane for Coding Agents, a product announcement “A control plane for coding agents observes every agent request and enforces policy inline - before data leaves the network - across every agent, gateway, and model provider an organization runs.” | official | 2026-08-30 |
| s4 | Fiddler AI: Control Plane for Agents product page “Enforcement extends to the IDE, CLI, and MCP boundary, with human approval required for high-risk decisions.” | official | 2026-08-30 |
| s5 | Visual Studio Code Marketplace: Lumeus extension listing published by Lumeus.ai “Lumeus.ai
|
166 installs” | official | 2026-08-30 |
| s6 | SiliconANGLE: Lumeus.ai raises $6M to enable universal zero-trust security across clouds and on-premises data centers “Zero-trust networking startup Lumeus.ai , officially known as Okulis Inc., is launching today armed with $6 million in seed funding.” | press | 2026-08-30 |
| s7 | Business Wire (vendor press release): Visibility-First Zero Trust Networking Platform Lumeus.ai Launches With $6M Seed “Founded in July 2021 and based in San Jose, CA, Lumeus.ai is a visibility-first Zero Trust networking platform that helps IT and Security teams modernize network security.” | official | 2026-08-30 |
| s8 | Tech Funding News: With $6M seed funding, Lumeus.ai launches its visibility-first zero trust network “The startup was founded in July 2021 and headquartered in San Jose, CA.” | press | 2026-08-30 |
| s9 | The SaaS News: Lumeus.ai Raises $6 Million in Seed Round “The round was led by Tola Capital, with participation from esteemed pre-seed investors Emergent Ventures and First Rays Ventures.” | press | 2026-08-30 |
| s10 | CXO Digitalpulse: Fiddler AI Expands AI Governance Stack with Lumeus.ai Acquisition “The integration combines Lumeus.ai’s upstream policy enforcement at the code generation stage with Fiddler AI’s production-level monitoring.” | press | 2026-08-30 |
| s11 | IT-Harvest Guardians of the Machine Age: Lumeus AI vendor profile “Lumeus AI provides AI-native security for modern development teams, focusing on protecting AI coding workflows, MCP protocols, and infrastructure access.” | research | 2026-08-30 |
| s12 | MCP Manager (a competing MCP-security vendor): The Best MCP Security Tools 2026 roundup “The most common form of MCP security tool is an MCP proxy , which typically sits inside (and is a component) of an MCP gateway .” | official | 2026-08-30 |
| s13 | Speakeasy (a competing vendor): In depth, Speakeasy vs Fiddler AI comparison page “Its April 2026 acquisition of Lumeus.ai markets policy enforcement at the IDE, CLI, and MCP boundary for coding agents, but that capability is weeks old and not yet in Fiddler's product documentation.” | official | 2026-08-30 |
This site is an experimental research aid created by Zeltser Security Corp. All its data gathering and analysis was performed autonomously without human review, and it can contain errors of fact, interpretation, and judgment that a human reviewer might catch.
The analyses are statements of opinion, not statements of fact. Machine analysis produced the scores, summaries, and matrix placements by weighing the public sources each page cites, and reasonable people can weigh the same sources differently. Where a page states a fact, it cites the public source and the date it was checked, and the statement is only as accurate as that source. Unless a profile expressly says otherwise, the analysis involves no hands-on testing and no independent validation of any company's products or services.
Nothing here is professional, security, legal, financial, investment, or purchasing advice, and nothing here is a recommendation to invest in, do business with, or avoid any company. Inclusion of a company is not an endorsement, and absence of a company is not a judgment about it. Reading this site creates no advisory or client relationship. Verify any detail you plan to act on against the vendor's current materials.
The content is provided "as is" and "as available," with all warranties disclaimed, express or implied, including merchantability, fitness for a particular purpose, accuracy, and non-infringement. No entry is warranted to be complete, current, or correct. Companies change, vendors update their claims, sources can be wrong, and automated analysis can misread them.
To the fullest extent permitted by law, the operator, Zeltser Security Corp, is not liable for any damages that arise from using this site or relying on its content, including direct, indirect, incidental, special, and consequential damages and lost profits, even if advised that such damages were possible. If you are dissatisfied with the site or disagree with these terms, your remedy is to stop using it.
Entries link to vendor pages, press coverage, and other external sites that Zeltser Security Corp does not control and is not responsible for. A link is not an affiliation with the destination or an endorsement of it. Product and company names and trademarks are the property of their owners, used here nominatively to identify the companies described. Short quotations from cited sources appear for identification and commentary.
Use, quotation, automated retrieval, and redistribution of the content are governed by the Terms of Use at cybercompanyprofiles.com/terms, which permit personal and internal business use with attribution and prohibit republication and resale.