SELF-HOSTED · YOURS

A fleet of AI agents
you actually own, run, keep, host, and trust.

Sandboxed, long-lived AI agents on your own infrastructure. Provisioned, scaled, paused, and watched from a single self-hosted console.

Your agents Your data Your stack
Activity LIVE
12:04:31 RUN agent-4b2e started research task
12:04:29 OK crawl-a3f1 ✓ 847 pages indexed
12:04:27 RUN draft-7c91 generating report
12:04:24 OK agent-2a10 ✓ task complete
12:04:20 PSE worker-5f33 paused · waiting
12:04:17 RUN claude-code driver booting
12:04:14 OK task-3b22 ✓ summary written
12:04:10 ERR agent-1a55 retry 2/3 · backoff
12:04:07 OK snapshot saved · agent-4b2e
Fleet Pulse
47 / 50 running
running paused error

One API. Swappable brains.

vanilla opencode codex claude-code

Multi-tenant workspaces

Agents, keys & data isolated per team or client

owner · admin · member

Plain Docker · REST + SSE API · Self-hosted · Your keys, encrypted · Provision in under 5 seconds

Infrastructure, not a chat box

Agenhood gives agents an operational home.

01

Long-lived, not ephemeral

Each agent keeps a writable /workspace volume across restarts, pauses, and weeks of idle. Files, memory, and history persist.

02

Sandboxed by default

Every agent runs in its own hardened container: read-only root, dropped capabilities, egress filtering. An unhinged agent can't touch the host or its neighbours.

03

Pluggable brains

One identical API, swappable execution engines. Vanilla, Opencode, Codex, or Claude Code. Pick the right brain per agent and switch anytime.

04

Self-hosted & yours

Single-VM deploy, your keys, your data. No vendor lock-in, no per-seat tax, nothing leaving your stack. One command: make prod.

The fleet

Each in its own sandbox, each with a memory.

Provision from a template in seconds. Idle agents auto-pause to save resources and auto-wake on the next task. The fleet breathes on its own.

Fleet pulse
47 / 50 running
3 active 1 paused 1 error
research-01 running
claude-code sonnet
2m ago 62% load
ingest-bot running
vanilla haiku
just now 42% load
report-writer paused
opencode gpt-5
1h ago paused
crawler-eu running
vanilla sonnet
30s ago 14% load
codex-fixups error
codex gpt-5
5m ago needs recovery
archivist archived
claude-code opus
3d ago archived
PLUGGABLE DRIVERS

One API. Swappable brains.

Claude Code
driver · claude-code

Anthropic's agent via claude -p, including subscription OAuth. Connect Claude Code once and assign it to any agent in the fleet.

PATCH /v1/agents/{id} {"driver":"claude-code"}

Chain them into pipelines. Set them loose on a schedule. Come back to finished work.

q3-report-pipeline 4 steps · 96% success
  1. researcher
    Gather sources
  2. 2
    analyst
    Extract metrics
  3. 3
    writer
    Draft report
  4. 4
    reviewer
    Proof & format
Scheduled last run · Succeeded
Every Mon & Wed at 9:30 AM
America/New_York · recurring
Mon Jun 30 workflow · q3-report
Wed Jul 02 prompt · daily-digest
Mon Jul 07 workflow · q3-report
Yours to own

Your keys. Your data. Your VM. No lock-in.

<5s
To provision an agent
1 cmd
Deploy to one VM · make prod
0 lost
Snapshots after every task
Sandbox

Read-only root filesystem, dropped Linux capabilities, egress filtering (private ranges & cloud metadata blocked), CPU/memory limits.

Your keys

Bring any provider's API key, or connect your Claude and ChatGPT subscriptions. Kept on your VM, revocable in a click. No per-seat SaaS tax.

Persistence

Automatic snapshots after every task, non-destructive rollback to any point, and optional Git backup that auto-pushes on completion.

For developers

The console is just a client.

Everything the web console does is a first-class REST call with a Server-Sent-Events stream. Create named, revocable API keys and drive your whole fleet from your backend.

Read the API docs →
REST + SSE API v1
  • GET /v1/agents list
  • POST /v1/agents/:id/tasks 202
  • GET /v1/agents/:id/tasks/:id/stream SSE
  • POST /v1/workflows/:id/run 202
  • GET /v1/schedules list
Same API · every client
Web console Your backend Webhooks
FAQ

Common questions.

What is Agenhood?

Self-hosted infrastructure for a fleet of long-lived AI agents. Each agent runs in its own sandboxed container with a persistent workspace, internet access, and a pluggable driver.

Is it self-hosted?

Yes. Single-VM deploy on plain Docker with your own keys and data. No vendor lock-in, no per-seat SaaS tax, nothing leaves your stack.

Which agent engines (drivers) are supported?

One identical API across swappable brains: Vanilla, Opencode, Codex, and Claude Code. The driver is part of an agent's config and can be swapped anytime.

How do you keep my data and agents secure?

Every agent runs in a hardened container: read-only root filesystem, dropped capabilities, network egress filtering, and CPU/memory limits. LLM keys are stored server-side, encrypted, and never sent to the browser.

Can I watch what an agent is doing?

Yes. Every task streams over Server-Sent Events (assistant messages, tool calls, results, file changes, a live token meter), and reconnects resume where they left off.

How do I get access?

Accounts are provisioned by admins; you self-host the stack. Use Get started, or sign in if you already have an account.

Get started

Deploy your fleet.

Put a fleet of sandboxed agents to work on your own infrastructure, provisioned in seconds and watched live from one console.

Get started

Admin-provisioned · Self-host in one command · Your data never leaves your VM