AnyTTY Cloud

AnyTTY Cloud adds account-level daemon registration, Internet discovery, Edge selection, P2P coordination, Relay fallback, usage, and billing. It does not replace the open-source daemon and clients, and it does not grant terminal or file access by itself.

Enroll a daemon

Sign in to the Cloud console, register a daemon, and use the generated enrollment command on that daemon machine. Then verify locally:

anytty cloud enroll ENROLLMENT_CODE
anytty cloud status

The exact enrollment command contains account-specific material and should be copied from the console, not reconstructed from documentation or shared in an issue.

Enrollment is not pairing

Enrollment associates a daemon identity with a Cloud account for discovery and routing. Pairing issues a client-bound grant from the daemon. A signed-in app does not automatically inherit daemon access; every client still needs an explicit pairing claim.

P2P and Relay

Cloud first coordinates available network paths. Depending on policy and reachability, a client may establish P2P or fall back to Relay. Route policy supports auto, p2p, relay, and smart_route; Relay transport supports auto, udp, and tcp.

Relay forwards protected traffic and has no terminal/file authority. The service still processes operational metadata needed for accounts, discovery, routing, diagnostics, usage, and billing.

Runtime and Edge

anytty cloud status
anytty cloud edge
anytty cloud disable
anytty cloud enable

disable pauses Cloud without deleting enrollment; enable resumes it. Edge selection can be inspected and reselected. Disabling Cloud does not stop Local, SSH, or separately configured Direct routes.

Plans and usage

Plan names, prices, and limits can change; the Cloud plan page and checkout are authoritative at purchase time. The console exposes current subscription, orders, and usage. P2P traffic and Relay-metered traffic may have different accounting, so inspect the usage view when diagnosing a limit.

Device management

The console can register daemons, generate enrollment commands, block or restore a daemon, delete its registration, and manage Edge preference. Removing a Cloud registration does not automatically revoke daemon-local client grants; inspect anytty access list on the daemon as part of retirement.

Account security and deletion

The security area manages password and persistent sessions. Account deletion is permanent and requires password confirmation. The console states that profile, daemon registrations, subscriptions, orders, usage records, and sign-in credentials are removed. Before deletion, cancel or understand active billing and preserve any records you are legally required to keep.

Cloud credentials and daemon grants are separate. A suspected compromise requires reviewing account sessions and password, daemon registrations, and daemon-local grants.

Choosing Cloud

Use Local on the same machine, SSH where trusted host access already exists, Direct on a controlled reachable network, and Cloud when Internet discovery, P2P coordination, or Relay fallback is needed. Configure multiple trusted routes when resilience matters, but never use fallback to bypass identity or authorization failures.