The enterprise browser wars produced two camps: vendors like Island asking companies to replace the browser entirely, and vendors betting the browser employees already use just needs a security layer. LayerX built the strongest version of the second bet: an agentless enterprise extension that turns any browser into a governed workspace - GenAI data leakage prevention, SaaS DLP, shadow app discovery, malicious extension protection, and identity controls, all without a browser migration. Founded in Tel Aviv in 2022 by Or Eshed and David Weisbrot, LayerX raised about $45 million and won customers like Dun & Bradstreet, KnowBe4, and MediaTek before the bet paid off decisively: in May 2026 Akamai announced its intent to acquire LayerX for roughly $205 million, folding the product into its zero-trust portfolio as Akamai Workforce Protector. Evaluators today are therefore buying two things at once - a well-reviewed browser security extension, and a roadmap now owned by Akamai mid-transition.
LayerX is a browser security platform delivered as an enterprise extension for the browsers an organization already runs - Chrome, Edge, and other majors - rather than as a replacement browser. From inside the browser it watches and governs last-mile user activity: what employees type and paste into generative AI tools, what files move into personal cloud apps, which unsanctioned SaaS and AI services are in use, which extensions carry risk, and where credentials are being reused or exposed. Its GenAI DLP capability is the marquee feature, inspecting prompts, pastes, and uploads to tools like ChatGPT, Gemini, and Claude in real time and blocking or warning before sensitive data leaves. Policies can warn, block, or silently log, and because enforcement lives in an extension, deployment rides existing browser management rather than software migration. Following the Akamai acquisition, the technology is being packaged as Akamai Workforce Protector, extending the same controls toward AI agents and desktop applications.
LayerX was founded in 2022 in Tel Aviv by CEO Or Eshed and CTO David Weisbrot, who built web attack and defense systems during their military service - Eshed is known for leading the 2017 exposure of one of the largest browser-hijacking campaigns in Chrome's history. The company raised a $26 million Series A in May 2024 led by Glilot Capital's early-growth fund with Dell Technologies Capital participating, extended the round by $11 million in April 2025 with Jump Capital, and reached roughly $45 million in total funding. The exit came fast: in May 2026, Akamai announced its intent to acquire LayerX for approximately $205 million, with closing expected in Q3 2026 - positioning the extension-based approach as the AI-usage-control centerpiece of Akamai's workforce security strategy and validating the thesis that enterprises want browser security without a browser swap.
LayerX built its brand as the anti-enterprise-browser - explicitly challenging Island and Prisma Access Browser with the argument that forcing a workforce onto a new browser is deployment friction enterprises don't need. Its category framing evolved with the market: from browser security platform, to secure enterprise browser extension, to - under Akamai - AI usage control and workforce interaction security. Reviews back the approach: a 4.9-star rating on G2 (a small but strongly positive review base) and favorable Gartner Peer Insights coverage, where the page now carries the Akamai Workforce Protector name. Its lanes: against full enterprise browsers it wins on deployment speed and user acceptance while conceding depth of control; against network-based SSE and CASB it wins on last-mile visibility inside encrypted sessions; against fellow extension players like Seraphic and SquareX it competed on GenAI-governance depth - a race now reshaped by all three landing inside larger platforms.
LayerX's published case studies consistently report the same pair of outcomes: visibility that didn't exist before, gained without user disruption. Dun & Bradstreet used the platform to prevent file-less data loss and govern risky extensions and shadow identities; KnowBe4 enabled its teams to use GenAI and SaaS tools freely while securing data inside the browser; MediaTek closed GenAI-leakage and malicious-extension blind spots while preserving engineer flexibility; Similarweb consolidated browser security into a single pane of user-activity visibility. Reviewers echo the pattern - clear insight into browser activity, straightforward deployment, and controls that enforce without hindering productivity. The $205 million Akamai price tag - roughly 4.5x total capital raised - is itself the market's verdict on how much that last-mile visibility is worth.
Real-time inspection of prompts, pastes, and file uploads to ChatGPT, Gemini, Claude, and other AI tools - blocking or warning before sensitive data leaves the organization.
Prevents sensitive files and data from moving into personal cloud drives, private email, and unsanctioned websites - governing the destination, not just the network path.
Maps every application and AI service employees actually use, surfacing unsanctioned tools and the identities used to access them.
Audits and blocks risky browser extensions that can steal passwords, cookies, and session data - a blind spot for most endpoint tools.
Flags password reuse, shadow identities, and phishing pages with real-time page-behavior analysis.
Rides the browsers already deployed - Chrome, Edge, and others - via managed extension rollout, with no browser replacement or endpoint agent.
Organizations enable ChatGPT-class tools for employees while inspecting and blocking sensitive data in prompts and uploads - the use case that drove the Akamai acquisition.
Security teams add last-mile data protection over SaaS and web apps without deploying endpoint agents or replacing browsers.
CISOs map unsanctioned SaaS, AI tools, and risky extensions across the workforce - often the first complete inventory they've had.
Real-time page analysis and password-reuse detection cut off credential theft where it happens.
The extension extends governance to contractor and BYOD browsers that full device management can't reach.
LayerX's integration surface reflects its extension architecture: it deploys through the browser management and device management tooling organizations already run (Google Workspace and Microsoft group policies, MDM/UEM extension force-install), feeds alerts and activity data to SIEM platforms, and ties identity signals to the enterprise IdP. Because it observes inside the rendered session, it complements rather than replaces network-layer SSE/CASB stacks - a positioning LayerX leaned into against proxy-based competitors. Gartner reviewers note one caveat: the API is limited, with few options for automating administrative workflows, so teams with heavy SOAR pipelines should validate their specific integrations. The Akamai acquisition points the roadmap toward deeper integration with Akamai's zero-trust portfolio - and evaluators should ask directly how standalone integrations will be supported through the transition.
Deployment is LayerX's headline advantage: pushing a managed extension through existing browser management reaches a workforce in hours, with no browser migration, no endpoint agent, and - per customer accounts - no perceptible change to how employees work until a policy fires. Case studies from KnowBe4 and MediaTek both emphasize rollout without user friction. The admin experience draws more mixed notes: Gartner Peer Insights reviewers praise the flexibility of the policy engine but observe that the same flexibility makes policy setup complex, and that policies cannot be prioritized against each other, forcing workarounds when rules overlap. Plan a tuning phase for DLP classifications - the standard arc of warn-mode first, then enforcement - and confirm which browsers and versions the extension fully supports in your estate, since enforcement depends on the extension actually being present in every browser employees use.
The security awareness company moved beyond traditional DLP by securing data inside the browser, giving teams full GenAI and SaaS access without losing control.
The chip designer eliminated GenAI-leakage and malicious-extension blind spots while preserving the flexibility its engineers expect.
The digital intelligence company consolidated browser security onto LayerX, gaining complete visibility into user activity, risks, and vulnerabilities.
LayerX does not publish pricing. Subscriptions are quoted per protected user or browser, with tiers differentiated by features and support - the standard shape for the category, and materially lighter than full enterprise-browser procurement since there is no migration project attached. Reviews describe the platform as accessible to mid-size security teams, not just global enterprises. The open question is what Akamai does with packaging: acquired products commonly get repriced into platform bundles, and Workforce Protector is being positioned inside Akamai's broader zero-trust portfolio. Buyers evaluating now should ask for pricing commitments that survive the transition, and model the comparison against both enterprise browsers (Island, Prisma) and fellow extension-based platforms rather than against network DLP alone.
LayerX's compliance story centers on governing the risks auditors increasingly ask about first: unsanctioned AI use, data moving into personal SaaS, and credential hygiene. Its discovery and DLP evidence gives compliance teams an inventory of AI and SaaS usage plus enforcement records for data-handling policies - documentation that generic proxy logs struggle to produce because they can't see inside the rendered session. The governance obligations run the other direction too: browser-activity monitoring is employee monitoring, and organizations owe notification, proportionality analysis, and counsel review of what is captured for which populations - especially where the extension reaches BYOD browsers carrying personal browsing. LayerX policies can scope observation to work contexts; drawing those lines remains the customer's job. Organizations with strict data-residency or vendor-risk requirements should also reassess the vendor entity itself as the product moves under Akamai's ownership and infrastructure.
The extension architecture that makes LayerX easy to deploy also draws its ceiling: it governs only browsers where the extension is present and running, so enforcement depends on blocking unmanaged browsers, and it cannot reach native desktop apps, email clients, or file systems the way endpoint DLP does - gaps Akamai's desktop-app roadmap acknowledges. Depth of control trails full enterprise browsers: Island-class session isolation, built-in RDP, and VDI replacement are simply out of scope. Administrators report real friction in reviews: policy configuration is complex, policies cannot be prioritized, and the limited API constrains automation. The review footprint, while glowing, is small - dozens of reviews, not hundreds. And the acquisition cuts both ways: Akamai's resources derisk the vendor, but transitions of this kind routinely bring repackaging, repricing, roadmap reshuffling, and the departure of founding talent - buyers should get roadmap and support commitments in writing.
The category-defining enterprise browser - far deeper control via full browser replacement, at six-figure procurement and real migration weight.
Palo Alto's enterprise browser, the natural fit for organizations already on the Prisma SASE stack.
Google's managed-Chrome tier adds DLP and access controls natively to Chrome - the incumbent play, no third-party extension required.
Microsoft's enterprise browser posture bundled with M365 - compelling economics inside the Microsoft estate.
Browser security that instruments any browser (and Electron apps) at the JavaScript level - a different any-browser architecture.
Extension-based browser detection and response focused on attack detection - now part of Zscaler.
| Category | LayerX: Browser Security Extension | PixieBrix: Browser-Native Guardrails & Workflow Control |
|---|---|---|
| Deployment | Managed extension pushed to existing browsers - hours to deploy, no migration. | Same model: PixieBrix deploys instantly as an extension in the Chrome or Edge employees already use. |
| Protection Model | Monitors browser events at the security layer: prompts to AI tools, uploads, downloads, extensions, credentials. | Governs the workflow layer inside the page - the specific copies, pastes, form entries, and data views of each business process. |
| Insider Threat Response | Blocks or warns on risky data movement to AI and SaaS destinations, with alerts to the security team. | Prevents risky actions at the point of work: blocking sensitive clipboard copies, redacting PII on screen, and requiring justification before high-risk changes. |
| Employee Experience | Invisible until a policy fires - security-centric, with warn or block interventions. | Transparent guardrails coach users in real time - and the same platform automates their repetitive work, making governance feel like help. |
| Analytics | Browser-activity visibility: SaaS/AI usage, extension risk, credential hygiene, DLP events. | PixieBrix Insights tracks workflow execution, guardrail interventions, and automation usage across governed apps. |
| Integrations | Browser/device management for rollout, SIEM export, IdP signals - with a limited API per reviewers. | Integrates with any web app directly in the browser - no APIs needed - and pushes events to tools like Slack, Jira, and Zendesk. |
| Ease of Maintenance | Flexible policy engine, though reviewers cite setup complexity and no policy prioritization. | Ops teams maintain guardrails and automations through a no-code editor, updating and deploying to every user instantly. |
| Governance and Security | Browser-activity monitoring that needs scoping, notice, and counsel review - plus vendor-transition diligence under Akamai. | Minimizes collected data by design: enforcement happens locally in the browser, and no monitoring archives accumulate. |
| Total Cost of Ownership | Quote-based per-user subscription - lighter than enterprise browsers, with packaging now in Akamai's hands. | Low-cost, fast-to-deploy browser layer whose payback spans prevented incidents and automated work alike. |
LayerX and PixieBrix share a conviction: the browser is where work happens, and an extension is how you govern it without disruption. But they watch different layers. LayerX polices browser events - the prompt to ChatGPT, the upload to a personal drive, the risky extension install. PixieBrix governs the workflow inside the page: the agent who shouldn't see the full card number on screen, the paste of the wrong customer's record, the account change that deserves a documented justification. PII is redacted before it renders, risky clipboard copies are blocked with a coaching explanation, high-risk actions require justification with a built-in audit trail - and the same platform automates the repetitive steps that produce careless mistakes in the first place. The two run side by side in the same browser without conflict: LayerX (or its Akamai successor) as the security team's monitoring and DLP layer, PixieBrix as the ops team's guardrail and automation layer. Or start with PixieBrix alone: for teams whose exposure lives inside CRM, support, and back-office workflows, in-page guardrails are the layer that pays back first. PixieBrix installs in minutes as an extension, managed with a no-code editor.
