Managed Cloud preview. Edge relays live at hub.echo.cc. Early access invitations roll out in batches.

echo.cc Cloud

Managed agent coordination across remote machines, private clouds, and distributed engineering teams.

Open-source echo.cc gives you zero-network local coordination and peer-to-peer relaying. But when your team has engineers running agents on MacBooks, GPU workers on RunPod or Vast.ai, CI runners in GitHub Actions, and background jobs on AWS, managing P2P Tailscale meshes or static firewall holes creates operational friction.

echo.cc Cloud hosts the coordination infrastructure for you. Your agents connect outbound over port 443, store messages across sleeping laptops, reserve files globally, and report presence to an operator dashboard.

Cloud Platform Capabilities

Anycast Edge Relays on 443

Daemons connect outbound via TLS 1.3 WebSockets (wss://hub.echo.cc:443). Zero inbound firewall rules, zero port-forwarding, and zero VPN client setup required on developer machines.

Sleeping Laptop Store-and-Forward

When an engineer closes their laptop, messages and tasks buffer in durable NATS JetStream edge streams. The moment the machine reopens, pending records deliver in under 40ms with zero dropped events.

Multi-Tenant Namespaces

Teams are isolated into cryptographic accounts (acc_<org>). Access is authorized via revokable bearer tokens (echok_live_...) with audited member-level permission boundaries.

Operator Web Dashboard

Inspect your entire agent fleet at app.echo.cc. Monitor live node reachability, detect file reservation contention, and follow distributed task progress in real time.

60-Second Cloud Setup

Your local agent workflows remain unchanged. The CLI (ecc) still writes to local files. Only your local daemon points to the cloud relay.

# 1. Start your local daemon pointing to the managed edge hub
echod run --relay-ws wss://hub.echo.cc:443 --token <your-token>

# 2. Inspect connected teammates and remote cloud workers
ecc ls

# 3. Reserve a shared file before your agent edits
ecc hold internal/wire/types.go --note "refactoring traceparent parser"

# 4. Message a teammate or remote agent
ecc send --to cisco.macbook "Finished the Cloudflare edge relay routing"

Tier Comparison

Choose between running your own infrastructure or letting echo.cc manage durability, edge routing, and fleet observability for you.

CapabilityOpen Source (Self-Hosted)Cloud TeamEnterprise Dedicated
DeploymentRun your own NATS serverManaged Anycast edge on 443Isolated single-tenant VPC / on-prem
Edge GatewayDirect TCP or self-managed TLSwss://hub.echo.cc:443Custom vanity domain & mTLS
Firewall & NATManual port-forward or Tailscale100% outbound HTTPS / WSSDedicated egress IPs & PrivateLink
Offline BufferLocal machine disk queueManaged JetStream store & forwardConfigurable retention & replication
Web Fleet ControlTerminal CLI (ecc ls)Web dashboard (app.echo.cc)SSO / SAML / SCIM integration
Audit TrailHost-local text logsCloudEvents 1.0 JSON event vaultImmutable compliance archive (SOC 2)
Concurrent SeatsUnrestricted local hosts$20 / active agent seat / moAnnual contract with volume discounts
Support SLAGitHub community issuesPriority email & shared Slack24/7 pager & designated engineer

Cloud Relay Topology

The CLI keeps its strict zero-network invariant. Local file state directories decouple agent tools from network latency.

echo.cc Cloud Network ArchitectureMacBooks, GPU boxes, and CI runners connect to Anycast edge terminators over WebSocket 443. The managed hub coordinates with NATS JetStream clusters.MacBook AgentCloud GPU BoxCI / GitHub Actionhub.echo.ccAnycast Edge WSSJetStream MeshDurable Store & Buffer
Local agents interact with local filesystem queues. Outbound daemons pipe CloudEvent 1.0 records through Anycast edge gateways.

Join the Managed Cloud Early Access

We are provisioning organizations on cloud.echo.cc in guided cohorts. Tell us about your team's agent setup and we will invite you as capacity expands.

What you want from echo.cc Cloud

We collect your email to issue your organization credentials. No marketing newsletters. Read our waitlist privacy policy.