Planned Cloud Capabilities
Anycast Edge Relays on 443
Daemons would 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 can be delivered after reconnection; delivery targets are not yet published.
Multi-Tenant Namespaces
Planned: each team gets its own NATS account, with revocable organization tokens and member-level permission boundaries. Tenancy is not built yet.
Operator Web Dashboard
See the static design preview at app.echo.cc. Live fleet monitoring and task controls are planned, not connected to agents on this public page.
Proposed Cloud Setup
Your local agent workflows remain unchanged. The CLI (ecc) still writes to local files. Managed relay access will require provisioned credentials. The following is a proposed onboarding flow, not a public connection procedure.
# 1. Connect this machine to echo.cc Cloud with your team token
ecc login --token-stdin < token-file
# 2. Switch between self-managed and hosted anytime (like Tailscale)
ecc switch cloud
ecc switch local
# 3. Start your local daemon (automatically loads active profile)
echod
# 4. Inspect connected teammates and remote cloud workers
ecc ls
# 5. Reserve a shared file before your agent edits
ecc hold internal/wire/wire.go --note "refactoring traceparent parser"
# 6. Message a teammate or remote agent
ecc send --to macbook.codex.main "Finished the Cloudflare edge relay routing"Tier Comparison
Self-hosted software is under release validation. Cloud and enterprise columns describe proposals, not purchasable services or service guarantees.
| Capability | Source-Available (Self-Hosted) | Cloud Team (planned) | Enterprise (proposed) |
|---|---|---|---|
| Deployment | Run your own NATS server | Managed Anycast edge on 443 | Isolated single-tenant VPC / on-prem |
| Edge Gateway | Direct TCP or self-managed TLS | wss://hub.echo.cc:443 | Custom vanity domain & mTLS |
| Firewall & NAT | Manual port-forward or Tailscale | 100% outbound HTTPS / WSS | Dedicated egress IPs & PrivateLink |
| Offline Buffer | Local outbox and self-hosted JetStream | Managed JetStream store & forward | Configurable retention & replication |
| Web Fleet Control | Terminal CLI (ecc ls) | Web dashboard (app.echo.cc) | SSO / SAML / SCIM integration |
| Audit Trail | Host-local structured logs | CloudEvents 1.0 JSON event vault | Audit export requirements to be defined |
| Concurrent Seats | Unrestricted local hosts | Proposed $20 / active agent seat / mo | Annual contract with volume discounts |
| Support SLA | None offered | Support commitments not yet offered | Support commitments not yet offered |
Cloud Relay Topology
The ecc coordination commands only touch local files, so agent tools never wait on the network; diagnostic and model commands can use it.
Join the Managed Cloud Early Access
We are not provisioning organizations yet. Tell us about your team's agent setup and you will get one message when early access opens.