> ## Documentation Index > Fetch the complete documentation index at: https://docs.novacula.io/llms.txt > Use this file to discover all available pages before exploring further. # Nodes overview > What a node is in Novacula, how it maps to running processes, the statuses you'll see, and where to go for each action A **node** is one blockchain full node, attached to one network, that you run to serve RPC for your apps, indexers, and other consumers. You create and operate it entirely from the UI under **Nodes** — Novacula handles the heterogeneous machinery of each chain and gives you a uniform node to manage. Each node carries a **name** (unique within its executor), the **chain** and **network** it runs (for example Ethereum mainnet), the **clients** and versions it runs, and the **executor** that hosts it. A node belongs to exactly one executor; to move it to a different host, delete it and deploy a new one. ## A node can be several processes Some chains run as a single process; others split into cooperating roles, and a node groups them as one unit. Logs and metrics surface per process, so you can stream one role's output independently of the other even though they belong to the same node. | Chain | Processes per node | Clients | | -------- | ---------------------------------------------------------------------------------- | ------------------------------------------- | | Bitcoin | 1 | `bitcoind` | | BSC | 1 | `geth` | | Tron | 1 | `java-tron` | | Ethereum | 2 — execution + consensus, sharing a JWT secret over the Engine API | execution: `geth` · consensus: `lighthouse` | | Igra | 2 — kaspad + execution, sharing a JWT secret over the Engine API | `kaspad`, `igra-reth` | | Ink | 2 — execution + rollup, sharing a JWT secret over the Engine API (Kubernetes only) | `op-reth`, `op-node` | | Monad | 3 — consensus + execution + RPC | `monad-bft`, `monad-execution`, `monad-rpc` | For ports, networks, default storage, and the exact clients and versions per chain, see the per-chain pages: [Bitcoin](/docs/chains/bitcoin), [BSC](/docs/chains/bsc), [Ethereum](/docs/chains/ethereum), [Igra](/docs/chains/igra), [Ink](/docs/chains/ink), [Monad](/docs/chains/monad), [Tron](/docs/chains/tron). ## The Nodes list **Nodes** lists the active nodes in your organization with their chain, network, executor, and current status. Filter by chain, status, or executor, and use [groups and tags](/docs/nodes/groups-and-tags) to organize a long fleet. Select a node to open its detail page. Inactive nodes are **hidden by default** to keep the list focused on what's live; turn on the explicit filter to show them. Links from the Dashboard — for example a card or a critical alert — open the list pre-filtered to the relevant nodes, carrying that filter through so you land on exactly the rows the alert is about. ## Statuses A node's status reflects what its executor most recently reported: | Status | Meaning | | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Provisioning** | The executor is setting the node up for the first time. | | **Downloading snapshot** | The node is bootstrapping from a snapshot before first start. The node page shows download progress, speed, and attempts. See [Node lifecycle](/docs/nodes/node-lifecycle#snapshot-bootstrap). | | **Starting** | Processes are launching. | | **Syncing** | Online but still catching up to the network's chain tip. | | **Running** | Healthy and serving. | | **Stopping** | Processes are shutting down after a stop request. | | **Stopped** | Intentionally or unexpectedly stopped; data is preserved. | | **Error** | A process or a lifecycle action failed — open the node to see the error details. | | **Deleting** | The node is being torn down. | ## On the node detail page The node detail page is where everything about a single node lives, organized into tabs: * **Overview** — headline telemetry (head block, sync %, peers), a **Lifecycle** panel (executor, desired vs reported state, last seen), **Storage Volume**, **RPC Endpoints** (with copy/open actions), and **Hardware Specs**. Lifecycle actions live in the node's header, not this tab. * **Monitoring** — sync progress, peers, disk usage, and other health metrics, per process. * **RPC** — the node's reachable RPC endpoint and its exposure settings, with an **Edit** action (dialog: **Edit RPC exposure**) and RPC-key management. * **Query** — run ad-hoc PromQL queries against the node's own metrics and chart the result; start from a preset recipe or write your own. See [Node monitoring](/docs/nodes/monitoring#query). * **Logs** — live process output, per role. * **Configuration** — the node's active settings, with an **Edit** action. ## What you can do | Want to | Go to | | -------------------------------------- | --------------------------------------------------------- | | Create a new node | [Deploy a node](/docs/nodes/deploy-a-node) | | Change clients, resources, or config | [Edit node configuration](/docs/nodes/edit-configuration) | | Control how RPC is reachable | [RPC exposure](/docs/nodes/rpc-exposure) | | Move to a newer client version | [Upgrade a node](/docs/nodes/upgrade-node) | | Start, stop, restart, or delete | [Node lifecycle](/docs/nodes/node-lifecycle) | | Organize or find a node in a long list | [Groups and tags](/docs/nodes/groups-and-tags) | | Watch live process output | [Node logs](/docs/nodes/logs) | | Read sync, peers, and health metrics | [Node monitoring](/docs/nodes/monitoring) | ## Who can do what * **Create, edit, run lifecycle actions, and delete:** owner and admin. * **Read status, logs, metrics, and events:** any organization member. See [Roles and permissions](/docs/platform/roles-and-permissions). ## Where nodes run You never need to log into the host — every action is in the UI. The [executor](/docs/executors/overview) that owns a node runs it on your infrastructure, whether that's [bare metal](/recipes/provision-on-bare-metal) or [Kubernetes](/recipes/provision-on-kubernetes).