OPEN_SOURCE_PATH
Review the current GitHub presence, inspect the policy model, and follow the runtime flow shown throughout this page.
View GitHub
SYSTEM.ALERT: OVER-PERMISSION DETECTED
Stop giving AI agents
god-mode access.
Boundport evaluates every agent action routed through its proxy before it reaches the target system - then allows it, blocks it, or pauses it for approval.
terminal.log
> INIT BOUNDPORT_PROXY
[OK] Core loaded.
[OK] Policy engine synced.
> INTERCEPT: tool_call_req
{
"agent": "agent_finance_01",
"tool": "finance.execute_wire_transfer",
"params": {"amount": 50000}
}
> VALIDATING AGAINST POLICY...
[ERR] VIOLATION_DETECTED: amount_limit_exceeded
[ACT] BLOCK_AND_ALERT
> req_status: DENIED
QUICK_START
docker run -p 8080:8080 railstack/boundport-proxy
Boundport controls what reaches your systems.
Governance starts before execution. Boundport gives teams a consistent review path for inspection, approvals, and audit decisions without handing agents unrestricted runtime access.
01 // INSPECT_REQUEST
Inspect & evaluate
Check the tool call, parameters and context before execution.
02 // REQUIRE_APPROVAL
Pause risky actions
Hold actions outside policy until someone approves them.
03 // RECORD_DECISION
Audit the outcome
Log the request, matched rule and final decision.
Keep enforcement close to your systems.
Run the Boundport proxy locally or inside your own environment. Add centralized policy management, approvals and audit with Boundport Enterprise.
CUSTOMER ENVIRONMENT
AGENT RUNTIME
BOUNDPORT DATA PLANE
(PROXY)
TOOLS / APIS
<-- POLICY DISTRIBUTION --
-- APPROVAL DECISIONS -->
-- REDACTED DECISION EVENTS -->
BOUNDPORT ENTERPRISE
CONTROL PLANE
Control the actions that carry real consequences.
Protocols define what agents may do, what requires approval, and what never reaches production systems. The examples below show how Boundport treats policy as executable guardrails instead of passive documentation.
FINANCIAL OPERATIONS
Require secondary approval for transactions above a specific threshold.
action: require_approval
condition: tool == "stripe.create_refund" && params.amount > 500
PRODUCTION SYSTEMS
Block destructive operations in production environments completely.
action: block
condition: tool == "aws.rds.delete_db_instance" && env == "prod"
SENSITIVE DATA
Redact PII from tool call arguments before they reach external APIs.
action: redact
fields: ["params.ssn", "params.credit_card"]
EXTERNAL ACTIONS
Limit the domains an agent can email or interact with.
action: block
condition: tool == "email.send" && !params.to.endswith("@company.com")
DEPLOYMENT MODEL
Choose the control surface that matches your rollout.
The open-source proxy keeps enforcement local. Boundport Enterprise adds shared policy operations, approval workflows, and centralized audit for teams that need stronger coordination.
On small screens: swipe horizontally to inspect the full comparison.
| CAPABILITY | OPEN-SOURCE PROXY | BOUNDPORT ENTERPRISE |
|---|---|---|
| Deployment | Self-hosted / Local | Managed Control Plane + Self-Hosted Data Plane |
| Policy management | Local YAML | Centralized UI & API |
| Runtime enforcement | Included | Included |
| Approvals | API Webhooks | Slack Integration & Approval Inbox |
| Audit | Local Logs | Immutable Logs & SIEM Export |
| Support | Community | SLA & Dedicated Engineering |
Compare the open-source proxy and Boundport Enterprise across deployment, policy management, approvals, audit, and support.
Build with a clear control boundary from day one.
Boundport gives teams a practical way to introduce agent automation without handing production systems unrestricted access. Put policy enforcement in front of sensitive tools, require approval where consequences are high, and keep an audit trail of every decision.
WHAT YOU GET
Runtime request inspection
Policy-based allow, block, or approval
Deployment close to your systems
Audit-ready decision history
GET_STARTED
Start the evaluation.
Use the open-source path to explore the enforcement model, or book a walkthrough focused on approvals, policy management, and audit workflows.
ENTERPRISE_PATH
Review the architecture and governance model, then book a Boundport walkthrough directly in the embedded scheduler.
Put a policy boundary between agents and production.
Run the open-source proxy locally, or deploy Boundport across your organization with centralized policy, approvals and audit.