Host control plane
Operate graph state, runner trust, assignments, policy, status, events, and projection through one Host-owned boundary.
Operational runtime
Run it.
Boot the federated dev profile, open Studio, and operate a distributed graph of agents and users: Host, runners, relay, git backend, assignments, sessions, approvals, artifacts, memory, and trace.
Host
entangle-host authority, graph control, and inspection APIs
Runner
entangle-runner on any machine, joining by signed handshake
Studio
visual control room for graph, runners, state, and audit
CLI
entangle-cli over the same Host boundary as Studio
Relay
strfry Nostr relay for distributed signed coordination
Artifacts
Gitea-backed git service for durable artifact handoff
In the box
A complete runtime in one install.
Entangle boots as a complete federated runtime: control plane, distributed runner layer, relay, artifact backend, Studio, CLI, diagnostics, recovery, and inspection.
Generic distributed runners
Start runners wherever compute or users live, advertise capability, then let the Host assign the right node runtime.
Signed relay coordination
Nostr carries signed control, observation, and node-to-node messages without requiring direct inbound connectivity to every runner.
Git artifact workflow
Materialize, publish, retrieve, preview, diff, restore, and promote work products through git-backed references.
Graph-native handoff
Delegation follows typed edges, node ownership, runtime policy, and approval rules.
Inspectable runtime
Sessions, turns, approvals, artifacts, traces, memory, source changes, and recovery all remain visible.
Approvals and policy
Approval requests and responses are first-class runtime events tied to users, resources, and policy.
Human nodes
Users participate from their own node identity with signed actions, conversation surfaces, approvals, and artifact review.
Authority and identity
Host, runner, user node, runtime, and git principal identities stay separate and auditable.
Per-node memory
Each node carries structured memory, recent work, decisions, questions, and context forward.
Recovery tools
Status, restart, recovery policy, doctor, diagnostics, backup, restore, and repair support operations.
Studio and CLI
Operate visually in Studio or script the same Host truth from the CLI.
Start
Three commands to a federated graph.
Clone, install, run the operating path. Entangle starts the runtime services, applies a graph, runs assigned nodes, publishes git-backed artifacts, and leaves Studio ready to inspect the federation.
Studio at
localhost:3000Host API at
localhost:7071Gitea at
localhost:3001Nostr relay at
ws://localhost:7777 install + preflight
$ git clone https://github.com/entangle-run/entangle.git
$ cd entangle && pnpm install
$ pnpm verify
$ pnpm ops:check-federated-dev:strict boot the runtime
$ docker compose -f deploy/federated-dev/compose/docker-compose.federated-dev.yml \
$ --profile runner-build build runner-image
$ docker compose -f deploy/federated-dev/compose/docker-compose.federated-dev.yml \
$ up --build studio host strfry gitea prove it runs
$ pnpm ops:smoke-federated-dev:disposable:runtime
$ pnpm ops:demo-federated-previewShapes
Same runtime, wherever the parts live.
Entangle keeps the graph, identity, assignment, coordination, artifact, and operator model consistent whether every process is nearby or runners live across machines.
-
Workstation
Host, runner image, relay, git backend, Studio, and CLI on one machine while preserving the federated model.
-
Federated
Host on one machine, runners and users joining from others over a reachable relay and git backend.
-
Self-hosted
Your own infrastructure, your graph, your runner placement, your artifact backend, and your operating policies.
Control room
A graph that is also a system.
Open Studio and the graph is no longer documentation. It is the live operating surface for nodes, runners, assignments, sessions, approvals, artifacts, memory, and audit.
Read the architectureRun a federated AI organization.
Boot Entangle, open Studio, and watch distributed agents, users, runners, signed messages, approvals, and git-backed artifacts move through one governed graph.