tempo process in follow mode (no local consensus engine) and serves the standard Ethereum JSON-RPC. How it fills its data directory depends on where it runs: as a systemd service on an Agent, or as a pod on the Operator, it bootstraps from a snapshot on first deploy and falls back to a peer sync if the snapshot isn’t available; as a Docker container on an Agent it always syncs from peers, with no snapshot step.
Tempo runs on both executor backends — a bare-metal Agent (as a systemd service or a Docker container) or the Kubernetes Operator (as a pod). To provision a host, see Provision on bare-metal or Provision on Kubernetes.
To deploy, open Deploy Node, pick Tempo, then choose a network.
Networks and resources
moderato is Tempo’s test network. Defaults are pre-filled in the deploy wizard.
Node type
Full only — a reth--full node that keeps full history and follows the chain; it takes no part in consensus.
Ports
Ports are managed for you and aren’t user-overridable.
Configuration
Tempo runs with a managed configuration — the chain, data paths, and RPC/P2P wiring are set for you; there are no client config overrides at deploy time.Metrics
Block height, peers, and sync progress are surfaced in the node view — see Node monitoring.What you can build
- Public RPC node — accept the defaults and expose
:8545(HTTP) behind your own proxy.