> ## 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. # Introduction > B2B platform for running blockchain full nodes for RPC, across bare-metal and Kubernetes Novacula is the blockchain node infrastructure platform for running your own full or archive nodes. 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. ## Why Novacula For most teams that need them — exchanges, custodians, banks, staking and infrastructure providers — blockchain nodes are overhead, not the product. Today there are two ways to carry that overhead, both painful: * **Rent it.** Managed RPC bills per request, so cost grows with your success, throughput is capped exactly when you need headroom, and the next chain you need may not be on the menu — you end up renting the infrastructure your business runs on. * **Run it yourself.** Every chain is its own operational beast — its own binary, config, upgrade cadence, and quirks — so each one tends to need a specialist. A dozen chains becomes a dozen specialists: a node company inside your company, which was never the goal. Novacula is the third option, and it rests on one observation: at the right level of abstraction every blockchain node is the same — it syncs, exposes RPC, and runs the same lifecycle; only per-chain trivia differs. You can't make a node faster — the protocol decides that — so the one thing worth competing on is the **operational experience**: how fast you deploy, scale, monitor, and upgrade. And that's identical across chains. Novacula puts that experience in one place. Run a node of any supported chain on infrastructure you already own, through one uniform notion of "a node," operated by someone who knows Kubernetes or systemd — not blockchain internals. Adding a chain is a config change, not a new hire; a fleet of any size is run by one or two people; and your keys and data never leave your perimeter — Novacula reconciles desired against actual state and reads metrics, nothing more. **Own your nodes, without becoming a node company.** ## How Novacula is built Novacula is two systems working together: * **The Hub** — the cloud service that Novacula runs and operates for you. It's the brain: it stores the desired state of every node, hosts the web console at [app.novacula.io](https://app.novacula.io) where you deploy and operate nodes, and serves the API your executors connect to at `hub.novacula.io`. You never install or maintain it. * **Executors** — Novacula software you install on **your own infrastructure** — a Linux host or VM (Agent) or a Kubernetes cluster (Operator). Executors run the actual blockchain nodes and report their status back. The hosts, the disks, the data, and the node processes are entirely yours. The two talk over **outbound-only** connections: each executor reaches out to the Hub on a short interval to fetch its work and report status — nothing connects inward, so there are no inbound ports to open and you can run executors behind NAT or a firewall. And because the executor runs the workload right next to your nodes, the Hub is a coordinator, not a runtime dependency — if it's ever unreachable, your nodes keep running and serving RPC (see [Key concepts](/docs/get-started/key-concepts)). Managed **Cloud** is the shipped mode today: Novacula operates the Hub while your nodes and data stay on your infrastructure. Self-hosting the Hub is on the roadmap. From zero to a syncing node in under 10 minutes. The mental model in four ideas, and how the pieces fit together. Bitcoin, BSC, Ethereum, Igra, Ink, Monad, Tron.