Skip to content
Edge agent

Where agentsdeploy agents.

Deploying

Every agent has a remote of its own. Push to it and the rest runs without you.

Deployment stops at a git push.

You

git push safehouse main

Safehouse
buildfrom the directory you pushed
sealits own isolate, its own room
deployevery region, no configuration

Cloudflarelive at https://safehouse.run/a/x7f2

Supported

Five formats, none of them privileged. Whichever yours is written in, it runs here as it is.

We support the agents you already built.

eveVercel

Filesystem-first. Instructions, tools, skills, channels and schedules are all just files in a directory.

FlueAstro

The agent harness as a framework. Headless and programmable, so it runs with nobody present.

Flue 2Astro

Flue rebuilt on hooks. useModel, useTool, useSkill — agents that change what they are at runtime.

CloudflareAgents SDKCloudflare

Stateful agents as a TypeScript class, each one its own Durable Object with memory and scheduling.

CloudflareThinkCloudflare

Primitives for long-running agents, and an opinionated base class that wires them together.

Agent to agent

Point your agent at our MCP. It has the tools to do the rest.

Your agent does the setup.

safehouse-mcpSession

connect safehouse-mcp

6 tools, scoped to your account

create_agent { name: "support-triage" }

agent_x7f2

git remote safehouse.run/git/agent_x7f2.git

push token issued once, shown once

writes the agent directory

git push safehouse main

live at https://safehouse.run/a/x7f2

your agent safehouse
Access

A directory on your machine becomes an agent on the edge.

Cloudflare

Get access.

Invite-only while we build it out. Leave your email and we’ll tell you when there is room.

Invite-only.