Is Menlo Security Available as an On-Premise Deployment?
No. Menlo Security on premise is not a deployment model the vendor sells. Menlo delivers remote browser isolation, browser DLP and its secure enterprise browser from its own cloud, and you route traffic to it through a proxy rather than installing an appliance in your data centre. Menlo’s product pages describe cloud delivery with no endpoint agent for the core isolation service, and no on-premises appliance appears in the current lineup.
📌 TL;DR Executive Summary
- Core Takeaway: Menlo is SaaS end to end. You set it as the proxy, install an SSL certificate so encrypted traffic can be inspected, and pages render in Menlo Cloud through Adaptive Clientless Rendering.
- Key Risk/Challenge: Isolating in a vendor cloud moves data residency onto the vendor and adds a detour — roughly 40–80ms near a point of presence, 150–400ms when users are far from one.
- Recommended Solution: Get the deployment model, processing locations and DLP scope in writing, then run the two-week proof of concept against your worst-connected office and your most latency-sensitive app.
What Menlo Security Is and Where It Actually Runs
Menlo Security is a privately held cloud security company based in Mountain View, California, founded in 2013. Its original product was remote browser isolation: pages load inside a container in Menlo Cloud, and the device receives a safe representation rather than the live page and its scripts.
The portfolio has widened since. By 2026 it covers remote browser isolation, a secure enterprise browser, browser DLP, file security strengthened by the February 2025 Votiro acquisition, Secure Application Access for zero-trust reach into SaaS and private apps, and MARS — Agent Runtime Security — for AI agents. In March 2026 Menlo bundled these into a Browser Security Platform, built on the argument that the browser is where people and AI agents now do their work.
The company reported passing $140 million in annual recurring revenue for the fiscal year ending January 2026, and Bill Robbins became CEO in February 2026, with co-founder Amir Ben-Efraim moving to executive chairman. Menlo also cites more than 8 million protected human users across over 1,000 enterprises — vendor and press figures rather than audited filings, so read them as directional.
For anyone weighing Menlo Security on premise, one detail matters more than the rest: every product in that list is described as cloud-delivered. Nothing in Menlo’s current documentation describes a self-hosted appliance, a virtual machine image you run yourself or a bring-your-own-cloud variant. Pages claiming otherwise are describing an older architecture, a different vendor, or a reseller’s shorthand.
How Menlo’s Cloud Delivery Works Under the Hood
Proxy-first deployment, not an appliance build
You deploy Menlo by pointing traffic at it. The standard pattern is to configure Menlo as the proxy server for browsers or for the network path, which means no client configuration, no server to build and no software installation on user devices. That is also why the model reaches contractor laptops, BYOD phones and unmanaged kiosks: the redirect happens upstream of the device, so the device needs nothing installed.
Why an SSL certificate has to sit on the proxy
Encrypted sites will not pass through a proxy that cannot read them, so an SSL certificate is installed on the proxy to let Menlo terminate the connection, evaluate the content and re-establish it. It is the same interception model any inspecting proxy uses, but it is the step that generates the most questions from security teams: managed endpoints have to trust your inspection point, and applications that pin their certificates break unless explicitly exempted.
Adaptive Clientless Rendering, explained
Most isolation products stream pixels — the remote browser draws the page, encodes video and ships frames to the client. Menlo’s patented Adaptive Clientless Rendering mirrors page structure instead: it reconstructs the DOM and styling information inside the device’s own browser, which keeps bandwidth low, text selectable and scrolling responsive on ordinary hardware. The security property is the same either way — the live page, its scripts and any exploit payload stay inside the container.
If you want the wider picture before you design a rollout, this browser isolation guide covers how isolation architectures get deployed across a workforce.
The Secure Extension and the enterprise browser
Menlo splits enforcement between local and cloud controls. A Menlo Secure Extension applies policy inside the browser itself, while high-risk browsing activity is automatically routed to Menlo Cloud for rendering and threat elimination. The secure enterprise browser packages that idea so a standard Chromium browser behaves as a managed one, with browser DLP and local controls built in.
How long implementation takes
Partner implementation guides describe a proof-of-concept environment in roughly two weeks and a live deployment in as little as one month. Those timelines assume your certificate work and proxy change are ready. The technology is rarely the long pole; change control is.
Why the On-Premise Question Keeps Coming Up
Buyers rarely ask for Menlo Security on premise because they like racking servers. They ask because three consequences follow from cloud isolation, and each has a real operational answer.
Data residency and sovereignty
When isolation happens in a vendor cloud, page content — including whatever a user types into a form — is processed there. For an EU or UK buyer the questions become concrete: which points of presence handle my traffic, which legal entity contracts with us, where are logs stored and for how long, and which sub-processors sit beneath that. Residency is now a market expectation rather than a checkbox: AWS opened its first European Sovereign Cloud region in Brandenburg, Germany on 15 January 2026, and buyers who read that announcement expect the same granularity from every security vendor they sign.
Latency: the cost of the detour
Every request travels device → Menlo Cloud → destination → back again. Typical cloud-proxy latency runs 40–80ms when the user sits near a point of presence and 150–400ms when they are far from one. For email and document review that is invisible; for latency-sensitive SaaS — a CRM with heavy forms, a trading dashboard, a browser-based video call — it is measurable. The fix is geographic rather than technical: find the PoP nearest your largest user population and test from your worst-connected office, not from head office on gigabit fibre.
What agentless DLP can see, and what it cannot
Menlo Browser DLP inspects what moves through the browser: web form fields, copy-paste into those fields, file upload and download, HTTP POST requests and watermarking. It ships with almost 400 data dictionaries you apply to form fields and extend with your own, and coverage includes generative AI prompts and uploaded files. Menlo Data Security adds AI Adaptive DLP, generally available since April 2026, which inspects files and data in motion — password-protected archives included — and masks PII, PHI and PCI content rather than blocking the action. Menlo reports 92% detection accuracy for that engine in its own testing.
The trade-off is structural, not a product flaw. Browser-side controls see the browser. They do not see a file copied to a USB stick, a screenshot pasted into a desktop chat client, or data typed into a native application. If your DLP programme is built on endpoint agents, agentless coverage is a different product with different edges, not a lighter version of the same one.
Containment as a design idea keeps spreading to new layers, which is why the benefits of browser isolation now get discussed well beyond the browser tab.
Pricing: What Menlo Quotes For and What It Doesn’t
Menlo does not publish a list price. Cost varies by which products you deploy — Protect, Secure and/or Manage — and by user licence count, plus add-ons; basic support is included in every deal. Exact quotes go through sales.
What has changed is the front end of that process. Menlo now runs a self-service estimator that returns a budgetary estimate in minutes without demanding a phone number, a shift from the older quote-only approach. Use Menlo’s pricing page to sanity-check budget bands, not to model a contract — an estimator cannot know your add-ons, your seat ramp or your support terms.
| What you decide | What it changes | What to ask on the call |
|---|---|---|
| Products (Protect / Secure / Manage) | Which capabilities you actually receive | Which tier covers isolation, which covers browser DLP, which covers app access |
| User licence count | The bulk of the contract value | Are contractors, BYOD users and service accounts counted as seats? |
| Add-ons | File security, agent runtime protections, extra support | Which of these are bundled at your tier and which are separate line items |
| Support level | Response times and escalation path | What basic support includes in writing, and what targets sit above it |
Menlo does not advertise a free trial; the usual entry point is a scoped proof of concept, so budget it with named success criteria, an owner and a deadline.
A Practical Checklist Before You Commit
- Confirm the deployment model in writing. If your requirement is written as Menlo Security on premise, ask directly whether any component can run in your own environment. A one-line email answer settles the entire question.
- Map the traffic path first. Decide whether Menlo becomes the proxy for all browsers, for a PAC file segment, or only for high-risk categories. The narrower the first phase, the cleaner the result.
- Do the certificate work before the PoC. Chain changes need change control and a rollback plan. Nothing stalls an isolation rollout like discovering that in week three.
- List every application with certificate pinning. Mobile apps, some finance clients and a long tail of internal tools will fail under inspection unless exempted.
- Test latency from the worst location. Time the three workflows your users complain about most, at peak hours, from the branch office rather than HQ.
- Define DLP scope as dictionaries plus destinations. Decide which of the ~400 dictionaries apply to which form fields, and which destinations are blocked, masked or allowed with a watermark.
- Write the residency answers down. Processing locations, log retention, sub-processors, deletion on exit and the contracting entity — in the security review, not in a slide.
- Decide AI-agent policy early. Menlo extended MARS in August 2026 to browser assistants such as Microsoft Copilot and Gemini in Chrome, and to coding agents such as Claude Code. If staff already use them, that policy belongs in the pilot.
If your rollout also touches hosted browsers rather than only on-device traffic, these cloud browser security best practices cover the configuration side a proxy deployment does not.
If On-Premise Is Non-Negotiable, What Then?
The requirement usually arrives second-hand. That is how most Menlo Security on premise requests start: a policy written years ago says regulated data must not leave the perimeter, and someone turns it into a search for an on-prem version. Split it into parts before you shop. Control over processing location, retention, who can read a log and deletion on exit are four different asks, and most can be satisfied contractually. “Runs in my rack” is the one that cannot.
Financial services, healthcare and legal teams hit this wall hardest, and their policies often date from when cloud inspection meant email filtering. Three routes work. Narrow the requirement to the controls you actually need and verify each one in writing. Keep the layers that must stay local — desktop DLP, endpoint agents, a managed browser at the edge — and use cloud isolation only where policy permits. Or accept that this architecture does not fit your constraint and evaluate something else; that decision costs less in week one than in month four.
Whichever route you take, the pilot plan should name the environments in scope, the three workflows you will time, the pinning apps you will exempt and the person authorised to roll back.
Profile-Level Isolation vs Remote Browser Isolation: Where Send.win Fits
These are two different isolation problems, and teams often conflate them. Menlo isolates the browsing session from the endpoint so a malicious page cannot reach the device and so data cannot leave through a browser. A browser profile manager isolates accounts from each other so the same person can work across several identities without cookies, storage and sessions bleeding together.
For an agency running client accounts, a QA team testing as different users and regions, or a support team reproducing a customer’s view, the second problem is the daily one. Send.win gives each profile its own cookies, storage, sessions, fingerprint settings and proxy — on the Sendwin Browser desktop app for Windows, macOS and Linux, or in the cloud browser running from Helsinki in the EU with nothing to install. Timezone, locale, WebRTC and geolocation follow the proxy exit IP automatically, and residential proxies are included on paid plans alongside bring-your-own HTTP/SOCKS5.
| Question | Menlo Security | Send.win |
|---|---|---|
| Primary job | Keep web threats and data loss away from the endpoint | Keep accounts, sessions and browser identities separate per profile |
| Where it runs | Menlo Cloud, reached through a proxy | Desktop app, or cloud browser in Helsinki, Finland (EU) |
| Who buys it | Security teams protecting a workforce | Agencies, social media managers, QA and support teams managing many accounts |
| Unit of separation | The user and the policy attached to them | The profile: cookies, storage, sessions, fingerprint settings, proxy |
| Network | Cloud proxy for isolation and inspection | Residential proxies on Pro and Team, or your own HTTP/SOCKS5 |
Both can sit in one stack without overlap: Menlo protects the endpoint from what the web delivers, and a profile manager keeps the accounts you are authorised to manage from contaminating one another. If you are weighing a local lab against a hosted one for testing, this comparison of virtual browser vs local setups covers the trade-offs.
🏆 Send.win Verdict
Menlo answers “how do I stop a malicious page from reaching this laptop”. It does not answer “how do I keep eight client accounts from sharing one browser identity”, and no amount of proxy configuration will make it. If your team manages accounts you own or are authorised to manage across stores, brands or regions, Send.win handles that layer: isolated profiles with their own cookies, storage, sessions, fingerprint settings and proxy, shareable with paid teammates so a profile opens already signed in, and synced across devices through the cloud.
See Send.win plans — Pro at $19/mo (150 profiles, 5 GB proxy bandwidth, 6 seats), Team at $49/mo (500 profiles, 20 GB, 16 seats), or start with the free cloud demo, which gives you 10 minutes a day in the cloud browser with nothing to install.
Frequently Asked Questions
Is Menlo Security available as an on-premise deployment?
No. Menlo’s documented model is cloud delivery: traffic is routed to Menlo Cloud through a proxy, and no appliance, VM image or self-hosted option appears in its current product lineup. If an on-premises requirement is non-negotiable for your regulator, raise it in the first conversation rather than after a pilot.
Does Menlo Security require software on the endpoint?
Not for the core isolation service — deployment is proxy configuration, with no client configuration or software installation on user devices. Menlo does offer a Secure Extension that applies policy locally inside the browser and a secure enterprise browser for managed enforcement. Contractors and BYOD devices are covered precisely because the redirect happens upstream of them.
How does Menlo’s cloud model differ from an on-prem appliance?
With an appliance, rendering and inspection happen on hardware you own, inside your perimeter. With Menlo, rendering happens in the vendor’s cloud and only a safe representation reaches the device. That removes capacity planning and patching from your team, and it moves residency, latency and log-retention questions into the contract.
What is Adaptive Clientless Rendering?
ACR is Menlo’s patented rendering method. Instead of streaming pixels as video frames, it mirrors the page’s structure so the device’s own browser reconstructs it. The result uses far less bandwidth, keeps text selectable and still keeps the live page and its scripts inside the isolated container.
How much does Menlo Security cost?
There is no published list price. Cost depends on which products you deploy — Protect, Secure and/or Manage — and on user licence count, plus add-ons, with basic support included in every deal. A self-service estimator returns a budgetary figure in minutes, but firm quotes come from sales.
How long does a Menlo implementation take?
Partner implementation guides describe a proof-of-concept environment in roughly two weeks and a live deployment in as little as one month. In practice the schedule is set by certificate changes and proxy cutover approvals, so start those in parallel with the technical work rather than after it.
Where does Menlo process data for EU customers?
Menlo describes cloud delivery through its own points of presence; the specific locations serving your sites are a contract question, not a marketing-page question. Ask for the PoP locations, the contracting entity, log retention periods and the sub-processor list, and get the answers into your security review in writing.
What is the difference between browser DLP and endpoint DLP?
Browser DLP inspects what moves through the browser: form fields, copy-paste, file uploads and downloads, HTTP POST requests and watermarks, backed by almost 400 data dictionaries and AI-based masking of PII, PHI and PCI content. Endpoint DLP also sees local file movement, USB copies and desktop applications. Agentless browser coverage is broader in reach and narrower in scope.
How Send.win Helps With Menlo Security On Premise
Send.win is a browser profile manager for professionals and teams: every account gets its own isolated browser profile.
- Isolated profiles – separate cookies, storage and sessions per profile
- Fingerprint protection – each profile keeps its own consistent browser fingerprint, so profiles never share one browser identity
- Desktop app + cloud browser – native app for Windows, macOS and Linux, or run profiles in the cloud with no install
- Residential proxies included – on Pro and Team, with timezone and locale matched to the proxy
- Team sharing – share a signed-in profile with a teammate without sharing the password
Try the free cloud demo — no install — or download the desktop app. Paid plans start at $19/month, and your first card purchase is covered by a 7-day money-back guarantee (see pricing).