Introduction

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.

Novacula is the blockchain node infrastructure platform for running your own full nodes for RPC. Deploy, configure, monitor, and operate JSON-RPC, WebSocket, and gRPC endpoints on bare-metal or Kubernetes you control — no third-party gateway, no traffic leaving your network. On-premise from day one, in every deployment mode. Managed Cloud keeps the control plane on Novacula’s side while the node hardware remains yours; fully Self-hosted puts the entire stack inside your network. Either way, blockchain processes and their data never leave hardware you own. The control plane orchestrates; your servers serve.

​

How it fits together

Executors run on your side. They open outbound HTTPS to the control plane, fetch the latest spec revisions for the nodes they own, and reconcile the underlying processes — never the other way around. See Architecture for the full lifecycle.

​

Two execution backends

Novacula nodes run through one of two backends, both implementing the same ChainAdapter interface:

• Agent — a Linux daemon that manages node processes as systemd services. Use it on bare-metal or virtual machines.
• Operator — a Kubernetes controller that materializes nodes as ConfigMap + StatefulSet. Use it on K8s clusters.

Pick the one that matches your infrastructure — or run both side-by-side under the same organization.

​

Outbound-only

Executors always initiate connections to the control plane over HTTPS. The control plane never reaches into your infrastructure, so you don’t need to expose any inbound ports, open firewall rules, or run VPN tunnels.