NO SHARED INVENTORY
Models, runtimes, Hermes agents, and tool permissions spread across sites without a common source of truth.
Private beta access is opening
The command deck
for local AI fleets.
Dafoe gives IT and MSP teams one operator-grade surface to discover, govern, deactivate, fail over, and enforce policy across self-hosted agentic AI runtimes, Hermes agents, models, tools, and workflows.
LIVE CONTROL PREVIEW
Watch authority move through every runtime before a human has to chase it.
The waitlist is for teams running local models, internal agents, and tool-calling workflows that need a real command layer before the estate gets wider.
DAFOE AUTHORITY policy lock active
01 Hermes tools scoped
02 Ollama health nominal
03 Lab GPU standby route
04 Client edge policy synced
CONTROL PLANE DAFOE / CORE
AUTHORITY ACTIVE
HEALTHY
Runtime / west-01 Ollama · Llama 3.3 HEALTHY
Runtime / edge-04 Open WebUI · Qwen GOVERNED
Agent / Hermes Hermes · Tools 08 STANDBY
Runtime / lab-02 LM Studio · Mistral policy.sync12/12
health.probepass
route.verifyready
01 / THE PROBLEM Local agentic AI is multiplying.
Local agentic AI is multiplying.
Control is not.
Self-hosted agentic AI gives teams ownership of where intelligence runs and what it can touch. It also creates a live execution surface: agents calling tools, reading local data, chaining workflows, and making decisions inside networks your endpoint, MDM, and observability stack was never built to command.
NO KILL AUTHORITY
When an agent touches the wrong tool, endpoint, or data path, shutdown is slow, manual, and incomplete.
NO CONTROLLED FALLBACK
Runtime and agent failures turn into outages because failover logic is embedded—or missing entirely.
02 / CONTROL SURFACE Five functions.
Five functions.
One command authority.
D 01
Deactivation
Stop a model, agent, tool, workflow, or entire runtime fleet from one authority point.
$ dafoe disable --scope fleet REMOTE KILLSCOPED ACTIONAUDITED
A 02
Availability fallback
Move workloads to approved local or remote capacity when health, latency, or policy conditions change.
$ dafoe route --fallback edge-04 HEALTH ROUTINGGRACEFUL FAILOVERSLO-AWARE
F 03
Fleet
Discover and inventory heterogeneous runtimes, agents, models, and tools across offices, data centers, labs, and client sites.
$ dafoe fleet discover DISCOVERYINVENTORYTOPOLOGY
O 04
Orchestration
Apply desired state and coordinate runtime, model, and tool lifecycle across the fleet from one place.
$ dafoe fleet apply policy.yaml DESIRED STATECOORDINATIONLIFECYCLE
E 05
Enforcement
Set boundaries for models, tools, data access, network routes, and execution at runtime.
$ dafoe policy enforce P-104 POLICY AS CODEGUARDRAILSEVIDENCE
03 / OPERATING MODEL From unknown estate
From unknown estate
to governed fleet.
Dafoe sits above your runtime layer. It does not replace the tools you already operate—it makes them controllable as a system.
- 01
CONNECT
Deploy a lightweight Dafoe connector beside each supported runtime or management boundary.
- 02
DISCOVER
Build a live inventory of models, agents, tools, workflows, endpoints, and dependencies.
- 03
DEFINE
Express operating rules as versioned policy: who can run what, where, and under which conditions.
- 04
CONTROL
Enforce, reroute, quarantine, or deactivate with a complete record of every action.
04 / ARCHITECTURE Control above.
Control above.
Execution where you choose.
Keep agents, inference, and sensitive data inside your environment. Dafoe coordinates the authority layer without forcing a single runtime, model vendor, or deployment pattern.
OPERATORS
IT OPERATIONSMSP NOCSECURITYPLATFORM TEAM
HTTPS / mTLS
DAFOE CONTROL PLANE
InventoryPolicy engineHealth routerCommand log
OUTBOUND CONNECTORS
RT-01 Hermes agent runtime CONNECTED
RT-02 OpenClaw autonomous agent CONNECTED
RT-03 Ollama model runtime CONNECTED
RT-04 LM Studio local model lab CONNECTED
RT-05 Open WebUI operator console CONNECTED
RT-06 Wayland agent surface CONNECTED
YOUR NETWORK BOUNDARY Agents, models, and data remain under your control
05 / SECURITY POSTURE
Authority must be controlled, too.
Dafoe is designed for privileged operations: explicit scope, strong identity, minimal access, and an evidence trail built into every command.
SECURE BY OPERATIONCONTROL / SCOPE / EVIDENCE
Least-privilege connectors
Narrow, explicit permissions at every managed boundary.
Signed command chain
Verify the origin and integrity of high-impact control actions.
Immutable audit trail
Maintain evidence for operator actions, policy changes, and runtime events.
Network-aware design
Operate across segmented, private, and intermittently connected environments.
06 / USE CASES Built for the teams
Built for the teams
who carry the pager.
Govern the agentic AI already inside your network.
Create a shared operating model for Hermes, departmental runtimes, sanctioned models, and internal agent deployments.
Operate many client estates from one practice.
Standardize discovery, policy, response, and reporting while preserving tenant and network boundaries.
Contain risk without hunting for every process.
Revoke tools, quarantine runtimes, disable agents and models, and preserve an auditable chain of action.
Keep local inference available by design.
Route around unhealthy nodes, coordinate capacity, and understand dependencies before they fail.
INITIAL ACCESS Get the private beta brief
01 Fleet control assessment 02 Design-partner roadmap 03 Priority beta access
Get the private beta brief
and a design-partner seat.
Join the Dafoe waitlist for early architecture notes, operator interviews, and access windows for teams actively running self-hosted agentic AI.
Map the runtimes, agents, tools, and shutdown paths you already have.
Preview the command, fallback, policy, and audit surfaces before release.
Get first access when Dafoe opens seats for local AI operators.