Skip to main content
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. For ports, networks, default storage, and the exact clients and versions per chain, see the per-chain pages: Bitcoin, BSC, Ethereum, HyperLiquid, Igra, Monad, Sui, 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 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.

​
Saved views

A saved view remembers how you’ve arranged the list — its filters, search, grouping, sorting, and display settings — so you can switch between arrangements instead of setting them up each time. The view selector shows the active view (or All nodes), with a Modified marker when the current arrangement has drifted from what you saved.
  • Save view captures the current arrangement under a name; Save changes updates the selected view, and Save as new view forks it into another.
  • Rename and Delete view manage the ones you have. Deleting a view never touches the nodes themselves.
Saved views live in your browser, per organization — a personal convenience, not shared with teammates, and clearing site data removes them.

​
Statuses

A node’s status reflects what its executor most recently reported:

​
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), a Node metadata panel, an Automatic updates card, and a Resources panel with an Edit resources action. Node metadata carries the chain, network, node type, Runtime, and age, then the node’s components with their clients and running versions plus any version update on offer. Runtime is Systemd or Docker for a node on an Agent (Systemd also when the node has no runtime recorded) and Kubernetes for a node on an Operator; a stopped node’s compact summary shows it too. The Automatic updates card is where Owners and Admins let the Hub apply supported version updates on its own — see Automatic updates. Lifecycle actions live in the node’s header, not this tab.
  • Connections — only for nodes that depend on something beyond their own processes: an L2’s L1 endpoints or a Tron node’s event streaming destination. See Edit a running node.
  • 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.
  • Logs — live process output, per role.
There is no configuration tab: a node’s client config is fixed at deploy. See Edit a running node for what can change and what needs a redeploy.

​
What you can do

​
Who can do what

  • Create, edit, run lifecycle actions, manage automatic updates, and delete: owner and admin.
  • Read status, logs, metrics, and events: any organization member.
See Roles and permissions.

​
Where nodes run

You never need to log into the host — every action is in the UI. The executor that owns a node runs it on your infrastructure, whether that’s bare metal or Kubernetes.