AI Governance & Security Vendor Wiki

4 min read

dope.security

Primary category: network-security-sase. Also listed in dlp.

One-liner — An SSE that inverts the category’s architecture: TLS inspection runs on the endpoint and traffic goes straight to its destination, with no vendor data centre in the path.

What it does — A secure web gateway plus DLP delivered as a lightweight endpoint agent. Every other vendor in network-security-sase works by hairpinning user traffic through the vendor’s own points of presence, decrypting and inspecting there, then forwarding on. dope.security calls that the “stopover” and does the inspection locally instead — branded Fly Direct. The claimed consequences are lower latency (no detour), no vendor-side outage taking the workforce offline, and user traffic never traversing the vendor’s infrastructure. Its AI-relevant piece is Dopamine DLP, applied to prompts and uploads to AI services rather than bolted on as a URL category.

Naming / provenance — Founded 2021 by Kunal Agarwal (previously Forcepoint). The brand is lowercase dope.security; expect “Dope Security” in lists. Founded 2021, Palo Alto CA.

Ownership & viability — independent, VC-backed, ~$24M raised, latest a $16M Series A in March 2023. Three years without a disclosed round while competing against zscaler, netskope, palo-alto-networks and fortinet is the central risk on this page — this is a small company selling into a category dominated by multi-billion-dollar incumbents. Treat as a genuine but early bet.

Positioning & differentiators —

  • The architecture is the product. On-device inspection is a real, checkable difference, not marketing. It changes the answer to “does our web and AI-prompt traffic leave our control to be decrypted by a third party?” from yes to no — which is a materially different conversation with a compliance officer than the one zscaler or netskope require.
  • No vendor-side outage domain. SSE outages take entire workforces offline; there is no shared cloud plane here to fail.
  • Managed-device only, by construction. The flip side: no agent, no coverage. Unmanaged devices, BYOD, contractors and non-endpoint traffic are outside the model in a way they are not for a cloud proxy.
  • Endpoint cost. Inspection consumes local CPU; the vendor’s counter is the sub-100MB footprint claim, which is a vendor claim and unverified.

Who should choose them / anti-fit — Fits a fully managed-device fleet at a firm that objects on principle or on regulation to a third party decrypting its traffic — a defensible position for a manager handling MNPI. Anti-fit: a firm with meaningful BYOD or contractor access, one needing branch/appliance coverage for non-endpoint traffic, or one whose procurement will not approve a Series-A vendor for a Day-1 control.

Known weaknesses / gotchas — Vendor size versus the incumbents is the dominant concern. Every performance and architecture claim above traces to the vendor’s own marketing, which is unusually assertive (its blog publishes its own competitive “buyer’s guides”) — treat those posts as marketing, not evidence. No independent analyst placement found.

Deployment & data handling — Endpoint agent. Traffic does not leave the tenancy for inspection — that is the entire architectural claim, and it is the one thing worth verifying directly in a trial. What telemetry or metadata is sent to dope’s cloud control plane is unverified and is the right follow-up question.

Integrations & partnerships — IdP and management-tool integrations claimed; specific list unverified.

Compliance & FS traction — Unverified. Cited references (a Fortune 100 deployment of 18,000+ devices, Outreach Health) are vendor-published and not financial services. Certifications not confirmed.

Commercial — Not public. Per-seat subscription; positioned as cheaper than legacy cloud proxies.

Open questions

  • Any funding since the 2023 Series A — the key viability question.
  • What metadata reaches dope’s control plane, given the “traffic never leaves” claim.
  • Independent verification of the performance and footprint claims.
  • Coverage story for unmanaged devices, BYOD and non-endpoint traffic.
  • Certifications held; any financial-services customers.

Sources

History

  • [2026-08-26] Page created via wiki-create + researched same day. Found by diffing the live SurveyMonkey instrument against the wiki — a human had added it to the SSE and DLP questions.

Graph View

Backlinks