Connect services across your hosts

Grant a workspace access to a specific service on another owned host; membership alone grants no traffic, and observed connection health stays visible.

The two-host backend grants fixed TCP Docker service endpoints through explicit per-workspace connections, with observed route health and revocation. It is not a general subnet VPN. Physical two-host connectivity/revocation is not live-verified; the sample shows existing service access controls without creating a tunnel.

How it works

  1. Open project Workflows

    Open Workflows from Projects or Sessions with Shift+W, or use the browser action.

  2. Configure and start work

    Choose accounts, hosts and limits, then start a task, request review or connect a tracker. CLI and scoped MCP tools expose the same operations.

  3. Keep live actions explicit

    Live actions require configured permissions, accounts and budgets; the demo only reads sample records.

Read the documentation

Try the interface

INTERACTIVE DEMO

Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.

YOUR AGENTS. YOUR INFRASTRUCTURE.

Put your server to work.

Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.