tempo process in follow mode (no local consensus engine) and serves the standard Ethereum JSON-RPC. On first deploy it bootstraps from a snapshot; if the snapshot isn’t available it syncs from peers instead.
Tempo runs only on a bare-metal executor (Agent) — it isn’t offered on the Kubernetes (Operator) backend. To provision a host, see Provision on bare-metal.
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.