Skip to main content
This guide takes you from zero to a running blockchain full node serving RPC. By the end you will have a connected executor, your first node syncing, and an RPC endpoint you can copy and use.

​
Prerequisites

  • An email address you can receive messages on.
  • One of:
    • A Linux host (x86_64) with sudo access — to run the Agent, which manages nodes as systemd services on that host.
    • A Kubernetes cluster (1.27+) with cluster-admin access — to run the Operator, which manages nodes as pods in that cluster.
You don’t need to open any inbound ports. The executor connects outbound to Novacula.

​
Steps

1

Sign in and create your organization

Sign in to the Novacula console. On sign-up, a personal organization is created for you and you become its Owner — the role that can connect executors and invite teammates.
2

Connect an executor

In the sidebar, open Executors → Connect Executor, then choose the backend that matches where you’ll install:
  • Agent — for a bare-metal or VM host. Runs your nodes as systemd services.
  • Operator — for a Kubernetes cluster. Runs your nodes as pods.
Give the executor a name. The flow generates an API key (prefix exc_) and shows it once — the install command on screen already includes it, so copy that command directly.
The API key is shown only once. If you navigate away before installing, you’ll need to start a new Connect Executor flow.
Run the command on your host or cluster:
  • Agent — paste the one-line curl … | sudo … sh installer on your Linux host. It downloads the binary, writes its config, and starts the service.
  • Operator — run the helm upgrade --install command against your cluster. It deploys the controller into the novacula-system namespace.
Full walkthroughs: Connect an executor, then Provision on bare-metal or Provision on Kubernetes.
3

Deploy your first node

In the sidebar, open Nodes → Deploy Node and work through the wizard:
  • Target — pick the executor you just connected, then a chain, network, client, and version. The wizard offers only what your executor supports, so every combination here is one it can run.
  • Resources — accept the per-network defaults, or override CPU / RAM / disk.
  • Custom config — leave empty for the first run; you can add overrides later.
  • Review — confirm your choices and deploy. The Advanced section is where you choose how the RPC endpoint is published.
See Deploy a node for every field explained.
4

Confirm it's online and copy the RPC endpoint

The executor’s status turns online in the Executors list once it checks in (within about 30 seconds of install). Open the node’s detail page to watch it boot and sync; the RPC endpoint appears there once the node is reachable. Click it to copy the URL, and you’re ready to send requests.

​
Next steps