Platforms

Pipelock vs Backslash Security

A self-hosted agent firewall next to a commercial platform for governing agents, MCP servers, and skills on developer endpoints.

At a glance

Pipelock source Backslash Security
Job Agent firewall. Mediates HTTP, WebSocket, and MCP traffic routed through it, scans it for secret leaks, prompt injection, SSRF, and tool poisoning, and can emit signed action receipts for mediated decisions when a signing key is configured. Agentic AI endpoint security platform. Rates MCP servers, skills, and plugins, governs which ones developers may install, and inspects MCP traffic on the endpoint through its own MCP proxy.
Enforcement point Network path, outside the agent process Developer endpoints and the AI clients installed on them
Source Open source, Apache-2.0 core; Enterprise under ELv2 Platform source availability not documented in public materials
Pricing shape Free core; paid Pro and Enterprise tiers Contact sales; the MCP Server Security Hub and Skills Security Scanner are public and free
Runs as Single Go binary, self-hosted; container and Helm Vendor platform with integrations into named AI coding agents and clients
Pick Backslash Security

You want to vet and govern which MCP servers, skills, and plugins developers install across many AI clients, with a vendor and support contract behind it.

Pick Pipelock

You need to inspect traffic those agents route through Pipelock at runtime, self-host the control, read the rules, and keep signed records where receipt signing is configured.

Run both

Backslash governs what gets installed and watches MCP traffic on the endpoint. Pipelock inspects the HTTP, WebSocket, and MCP traffic agents route through it on the network path.

Want the runtime boundary, not just another checklist?

The short version

Pipelock is an open-source agent firewall. It runs as a single Go binary on the agent’s routed network path and scans HTTP, WebSocket, and MCP traffic for credential leaks, prompt injection, SSRF, and tool poisoning. With a signing key configured, it can emit signed action receipts for mediated decisions. The verifier checks them offline.

Backslash Security sells what its site calls an agentic AI endpoint security platform. It rates MCP servers, skills, and plugins on security posture and supply-chain risk, lets security teams allowlist, blocklist, or require approval before installation, and surfaces unmanaged agent use on developer machines. Its MCP security page says an endpoint MCP proxy inspects traffic between agents and MCP servers and blocks malicious instructions, risky tool calls, and policy violations. The public pieces are the MCP Server Security Hub and a Skills Security Scanner. The enterprise platform covers a long list of AI coding agents and clients.

Pipelock is a binary you run in your own environment and inspect at runtime. Backslash is a platform you buy to govern AI tools on developer endpoints.

Feature comparison

FeaturePipelockBackslash Security
ArchitectureSelf-hosted single binary on the network pathVendor platform with endpoint and client integrations
Primary jobRuntime inspection of mediated HTTP, WebSocket, and MCP trafficGovernance of servers, skills, and plugins on endpoints, plus an endpoint MCP proxy
Credential scanning (DLP)65 built-in patterns, encoding-aware, on mediated trafficLists data exfiltration as an MCP threat; credential scanning details not documented in public materials
Prompt injection detectionDeterministic patterns with multi-pass normalization on scanned responses and tool descriptionsSays its MCP proxy blocks malicious instructions; method not documented in public materials
Tool poisoningMediated description scanning and rug-pull drift detectionRates servers and skills before installation; MCP proxy inspects agent-to-server traffic
SSRF protectionMediated private-IP, metadata, and DNS rebinding checksNot described in public materials
Client coverageAny client whose traffic is routed through the proxyNamed list of AI coding agents and desktop clients
Public catalogNoMCP Server Security Hub and Skills Security Scanner, free
Signed receiptsAvailable with a signing key; Ed25519, verifiable offlineNot described in public materials
Source availabilityApache-2.0 core; Enterprise under ELv2Platform source availability not documented in public materials
PricingFree core; paid Pro and Enterprise tiersContact sales

When to pick Pipelock

You need inspection beyond MCP. Backslash documents an endpoint proxy for MCP traffic. Pipelock also scans the HTTP and WebSocket traffic agents route through it, so a secret sent to an arbitrary web endpoint or an injected web page response is in scope, not only MCP calls.

You want to self-host and audit the rules. Every DLP regex, injection pattern, and normalization pass is in the public repository. You can fork it, audit it, or run it air-gapped.

You want evidence. With a signing key and allow-path receipt enforcement configured, Pipelock refuses to forward an allowed mediated request whose signed receipt cannot be emitted. The verifier checks signed receipts offline against your key.

When to pick Backslash

Your problem is governance across many developer endpoints. If the question is “which MCP servers, skills, and plugins are our developers installing, and which should be allowed”, Backslash is built around that question and integrates with the clients developers already use.

You want a public rating catalog. The MCP Server Security Hub and Skills Security Scanner give teams a free place to check a server or skill before installing it. Pipelock has no catalog.

Procurement needs a vendor. Commercial support, SLAs, and a named company behind the product matter to some buyers. Pipelock’s free core is a different answer to a different question.

Different moments in the lifecycle

Backslash acts at the endpoint: rate it, allow it, block it, send it for approval, inspect its MCP traffic, and keep an audit trail of what the harness did. Pipelock acts on the routed network path: read what the installed thing sends and receives, block configured unsafe findings, and emit signed receipts when a signing key is configured. A team that wants both endpoint governance and network-path inspection can run both because the controls operate at different points.

Further reading

Sources checked

Third-party descriptions on this page come from the public materials below, read on the dates shown. Features and pricing change; check the current documentation before you decide.

  • Backslash Security homepage checked 2026-09-01 · lists coverage for Claude Code, Claude Desktop, Cursor, GitHub Copilot, Devin Desktop (Windsurf), Gemini CLI, Google Antigravity, OpenAI Codex, Kiro, and OpenClaw
  • Backslash MCP security page checked 2026-11-14 · describes an endpoint MCP proxy that inspects agent-to-server traffic and blocks malicious instructions, risky tool calls, and policy violations

Third-party product names and marks belong to their owners. PipeLab is not affiliated with, sponsored by, or endorsed by the makers of any product compared on this page. Descriptions of other products come from their own public materials on the dates listed above and reflect PipeLab's reading of them. If something here is wrong or out of date, tell us and it will be corrected.

Frequently asked questions

What's the difference between Pipelock and Backslash Security?
Pipelock is an open-source agent firewall that runs as a single Go binary on the agent’s routed network path and scans HTTP, WebSocket, and MCP traffic for credential leaks, injection, SSRF, and tool poisoning. Backslash Security is a commercial platform that rates and governs the MCP servers, skills, and plugins installed on developer endpoints, and runs an endpoint MCP proxy that inspects traffic between agents and MCP servers. Pipelock self-hosts. Backslash is a vendor platform.
Does Backslash Security scan HTTP traffic?
Backslash says its endpoint MCP proxy inspects communication between agents and MCP servers and blocks malicious instructions and risky tool calls. A forward proxy that inspects general HTTP, CONNECT, or WebSocket payloads is not described in the public materials read for this page. Pipelock is that proxy and scans the traffic itself for agents routed through it.
Is Backslash Security open source?
Its platform source availability is not documented in the public materials read for this page. Pipelock’s core is open source under Apache-2.0, so you can read every DLP pattern and normalization pass in the public repository.

Want the runtime boundary, not just another checklist?

See all comparisons →