One agent per employee,
one workspace for the company.

Your company builds the skills, MCP servers and CLIs once. Every employee's agent inherits all of it and adds a personal scope of its own, in an isolated VM.

A company workspace in Hogpass. A shared layer across the top holds 12 skills, 8 connected MCP servers and 6 CLIs, built once and available to everyone. Below it, maya in finance, raj in engineering and wei in support each have their own agent that inherits the shared layer and adds a personal scope, each in its own VM with its own credentials.

Shared, built once

Skills, MCP servers and CLIs live at the company level. Write a skill on Monday and every agent in the org has it on Monday.

Personal, sealed off

Each employee's agent gets its own VM and its own scope. Two people on the same team cannot see each other's data or credentials.

Ready in seconds

No install, no keys to copy, no setup call. A new hire opens Hogpass and their agent already knows the company's tools.

Keys stay in the vault

Real credentials never touch the agent. Hogpass holds them and issues a scoped pass at the gateway, so a leaked or stolen .env exposes nothing.

.envproxied by hogpass

OPENAI_API_KEY=sk-proj-Xh4mQ2████████f8Kwhogpass-managed ✓

STRIPE_SECRET_KEY=sk_live_51Hx8m████████Rq2vhogpass-managed ✓

GITHUB_TOKEN=ghp_uV4nR7Tk████████p3Xzhogpass-managed ✓

AWS_SECRET_ACCESS_KEY=aK9dPmXw████████L7Rqhogpass-managed ✓

DATABASE_URL=postgres://acme:pg4s█████@db.acme.iohogpass-managed ✓

SLACK_BOT_TOKEN=xoxb-8214-Ju7wK████████m2Nphogpass-managed ✓

ANTHROPIC_API_KEY=sk-ant-api03-R5kT████████v8Nqhogpass-managed ✓

7keys exposed to agents

Want this for your environment?

An MCP gateway covers one path. Hogpass covers all four.

When every employee has an agent, tool-level permissions are not enough. Enforcement happens at the network layer, so it does not matter which route the agent takes.

MCP tool calls

Governed

CLI commands

Governed

curl and raw HTTP

Governed

The code the agent writes

Governed