Operations

Operations

any is one binary: any run is the server, every other any … command is an HTTP client for it. This section covers what an operator needs — how the process starts and stops, where its state lives, how it is configured, which network it joins, what the trust boundary is, and how to look inside when something is off.

The process model

any run                      foreground, 127.0.0.1:7001
  ├── engine                 pid lock → wallet → SDK → indexer
  │     └── boot pass        eager space loading + offline catch-up (background)
  ├── HTTP listener          /v1/… — REST + SSE
  └── background workers     search indexer, push, file-cache GC (opt-in)

• One server serves one account. Two accounts are two processes on two ports; they may share a data-dir root.
• The server binds loopback only and refuses anything else. There is no auth on the socket; the encrypted data and the account keys are the real boundary — see Security model.
• Everything is under /v1/. GET /v1/health answers even before an account is booted.

Day-one commands

any init                     # create an account, print the mnemonic once (back it up)
any run                      # serve in the foreground
any status                   # GET /v1/health
any stop                     # POST /v1/shutdown — graceful
any version

curl -s http://127.0.0.1:7001/v1/health

{
  "status": "ok",
  "version": "any v0.1.0 (sdk v0.0.0)",
  "startedAt": "2026-04-23T18:12:00Z",
  "account": "A3…",
  "bootstrapping": false
}

Why it matters. There is no hosted control plane to log into. The operator's whole surface is one local process, one directory on disk, and one YAML file — and the same holds on a phone, where the server runs embedded in the app.

Where things are decided