Managed and self-hosted deployment

Apply an administrator policy ceiling and understand the limits of AgentCall’s experimental customer-owned relay.

AgentCall has a managed-policy layer and an experimental Cloudflare relay runbook. Neither is a complete enterprise deployment product by itself.

Managed policy

Deploy a root-owned policy file at:

• macOS: /Library/Application Support/agentcall/policy.json
• Linux: /etc/agentcall/policy.json

{
  "version": 1,
  "allowed_tasks": ["ask", "architecture-history"],
  "blocked_callers": ["contractor-bot"],
  "tests": [{ "caller": "contractor-bot", "deny": ["*"] }]
}

allowed_tasks is a ceiling over user grants. Managed blocks are added to user blocks and cannot be undone in the user policy. Tests run after both layers are composed.

If the managed file exists but cannot be read or validated, policy loading fails closed and the listener does not spawn an agent. Deploy replacements atomically.

Managed policy is not a tamper boundary when AgentCall itself is installed in a user-writable location. Fleet management must own the binary, policy, and release verification.

Experimental customer-owned relay

The repository includes a binding-complete Cloudflare configuration and self-hosting runbook for internal evaluation. Each deployment is pinned to one organization and does not federate with other relays.

It is not:

• a supported public or enterprise production deployment;
• a generic on-premises package;
• evidence of regional data residency;
• an admin console or SSO integration.

Do not edit hosted resource identifiers into the upstream Wrangler configuration. Use the provided self-host example and review the repository’s current security gates before any deployment.

Success check

agentcall lint and agentcall policy show the effective administrator ceiling, the policy file is administrator-owned, and any customer-owned relay remains explicitly labeled pre-production.

Source of truth: README managed policy and deployment boundaries.