Common questions

The things a company asks before it hands agents to everyone.

“Be greedy about AI” sounds reckless. Is it?

It would be, without the second half. The risk of more agents is more copies of your credentials, so Hogpass removes that link entirely: agents never hold keys. Each one is issued a scoped, expiring pass at the gateway for the one call it is making. Ten agents and one agent carry exactly the same credential exposure, which is none.

What is Hogpass?

Every employee in your company gets their own AI agent, securely. Each runs in a completely isolated VM, and every request it makes to a real service goes through the Hogpass gateway, which attaches a scoped credential per request. Keys never leave the vault.

How is this different from just installing OpenClaw?

OpenClaw gives one person an agent with unrestricted access to their machine and accounts. Hogpass keeps that capability but raises the bar: each employee's agent runs in its own isolated VM, reaches services only through the gateway with scoped credentials, and every action is policy-checked and logged. No per-person overhead, no unrestricted access.

How do employees talk to their agent?

From the web, from the terminal with one command, or directly in Slack. Connect Hogpass to your workspace and each employee chats with their own agent wherever they already work, with the same identity, permissions and audit trail everywhere.

How does Hogpass keep API keys away from agents?

Credentials live in an encrypted vault (local KMS or Hogpass Cloud) and are attached per-request at the gateway boundary. The agent and the model never see a key: not in environment variables, not in prompts, not in logs.

Does it work with my agent framework?

Yes. Hogpass is framework-agnostic: OpenClaw, NanoClaw, IronClaw, Dify, n8n, OpenHands, or any custom pipeline that makes HTTP calls. No code changes. Agents route through the gateway with one command.

Is Hogpass an MCP gateway?

No, it covers more than MCP. An MCP gateway only governs MCP tool calls. Hogpass enforces at the network layer, so it secures every route an agent can take: MCP tool calls, CLI commands, curl from a shell, or HTTP requests from code the agent writes. Same vault, same policies, same audit log for all of them.

What can I enforce?

Block specific endpoints, rate-limit per agent, require human approval for sensitive operations, and scope credentials per employee. Policies are enforced at the network layer, outside the agent and outside the model, so they are rules rather than suggestions.

Is Hogpass open source?

Yes. Apache 2.0 licensed and developed in the open on GitHub. Self-host it for free with a one-line install, or use Hogpass Cloud if you want a managed vault and dashboard.

How long does setup take?

A few minutes per employee. Start a 7-day free trial with $5 in model credits included, no credit card required. Add your keys to the vault, invite your team, and each person gets their own secured agent.