Host-backed sessions
Run agents where developers already have repositories, tools, credentials, and build systems configured.
Use case · self-hosted orchestration
Self-hosted orchestration for coding agents.
AFK supports developer-machine daemons, shared company servers, Docker-backed sessions, and on-prem deployment patterns so teams can operate autonomous coding agents closer to their source code and network boundaries.
• Daemon-owned execution keeps process ownership close to the workspace.
• Shared daemon deployments let teams run agents on company-controlled infrastructure.
• Docker-backed sessions provide isolated execution lanes for remote repository work.
• Org and team visibility can sit above host, Docker, and daemon-backed execution contexts.
Shared daemon model
Operate a company-controlled daemon for teams that need central access without moving code into a third-party coding environment.
Docker isolation
Use containerized workspaces for remote sessions, repository automation, and safer execution boundaries.
Many teams want autonomous coding agents, but not at the cost of unclear execution boundaries. AFK separates the browser command surface from daemon-owned execution so teams can choose where the work runs.
That model supports local developer workflows, shared internal infrastructure, and Docker-backed remote sessions while preserving the same browser-visible session lifecycle and approval controls.
Related searches: self-hosted coding agent orchestration, on-prem AI coding agents, Docker coding agent execution, shared daemon coding agents, private coding agent platform