Operate the boundary.
Managed deployment, upgrades, health, backups, tenant isolation, and supported private connectivity for compatible traffic paths.
Open source first.
Operations when
you need them.
TrapDefense 0.47 publishes the Runtime Gateway and Agent Access Broker together under MIT. There is no separate Enterprise code edition. You can self-host the complete current product; future commercial value can come from running, integrating, and supporting it.
THE SAME PRODUCT BOUNDARY
RUNTIME GATEWAY + CONTENT POLICY + AGENT ACCESS BROKER + AUDIT
The enforcement path stays inspectable and self-hostable. A future service would operate the same product contract rather than unlock hidden authorization features.
POSSIBLE COMMERCIAL SERVICESSell the hard operational work,
Sell the hard operational work,
not a code gate.
These are direction statements. They are not launched offerings, published SLAs, or promises of current availability.
Scale operations.
Central policy rollout, multi-node HA, capacity management, immutable external audit, and evidence retention integrations.
Fit the customer stack.
Identity mapping, MCP/API routing, destination credentials, policy design, acceptance testing, rollout support, and incident response.
The open-source 0.47 baseline.
- Envoy-based Runtime Gateway for explicit bounded HTTP JSON and stateless remote MCP routes.
- Native OpenAI, Anthropic, Gemini, and OpenRouter profiles for text/function calls and fully buffered SSE, with synthetic Python SDK verification.
- Request and response action, PII, and secret controls with inline and mirror behavior.
- Local expiring agent credentials or external JWT validation, with explicit autonomous or delegated authorization.
- Agent Registry, delegation, resource/action policy, request-bound one-time human approval, and local audit.
- Control and data planes as separate services: Ed25519-signed policy snapshots, last-verified-policy enforcement during console outages, and an append-only evidence spool.
- Operations console, six UI languages, bounded gateway admission, optional 2 or 4 same-host inspector processes, and Docker Compose packaging.
Access Broker is Experimental. Customer IdP policy, production routing, target authentication, bypass prevention, HA, capacity, and operational ownership still require deployment acceptance.
No hosted service is available today.
There is currently no managed signup, subscription, production SLA, or multi-tenant control plane. Use the open-source self-hosted package and contact us only if the explicit integration contract fits your environment.
Review the deployment contract ↗START WITH DEPLOYMENT FITBring one
Bring one
real action path.
A useful first engagement defines one client, one destination, a small tool/action set, identity claims, failure policy, and measurable acceptance tests.
hellocosmos@gmail.com ↗GOOD FIRST SCOPE
One protected workflow
Configurable client endpoint · bounded HTTP/MCP JSON · local agent credential, external issuer or connection key · separate target credential · explicit allow/deny/approval cases · bypass control · sanitized evidence.
Discuss deployment fit ↗