> ## 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 vs QuickNode

QuickNode provides managed blockchain infrastructure, RPC endpoints, data services and dedicated clusters across many networks. Novacula is built for teams that want to deploy and manage blockchain nodes on infrastructure they control, with direct visibility into node health and operations.

## **Novacula vs QuickNode: Compare Infrastructure, APIs and Operations**

| Feature | Novacula | QuickNode | What this means for you |
| :- | :- | :- | :- |
| Infrastructure and deployment | Nodes run on infrastructure your team controls: bare metal, virtual machines or Kubernetes. The Hub deploys, configures and monitors them; Agents and Operators on your side run them. | QuickNode operates the nodes and provides managed endpoints, plus Dedicated Clusters of two or more mirrored nodes that QuickNode runs on its own infrastructure. | Novacula is for teams that want to own the node environment. QuickNode removes node deployment and maintenance work. |
| Where your requests go | Requests are served by your own nodes. The Hub receives per-request metadata only: method, outcome, byte counts and duration. Request bodies never leave your infrastructure. | Every request and response passes through QuickNode’s infrastructure. | With Novacula your RPC traffic stays inside your perimeter. |
| Client choice and upgrades | You choose the client and the pinned version per node, for example geth or reth on Ethereum. Every version change is a checked transition: in place, resync or blocked, and security-urgent, recommended or optional. An automatic upgrade policy applies a channel inside a daily window, and a failed in-place upgrade rolls back on its own. | Standard endpoints run a managed mix of Geth, Nethermind, Erigon and Reth chosen by QuickNode. Choosing a client requires a Dedicated Cluster. Version pinning is not documented. QuickNode performs the upgrades. | Novacula gives you control over what runs and when it changes, on standard nodes. |
| Debug and trace access | Read-only debug tracers and trace methods are served from your own nodes on every network the client supports, on every plan. Method and range limits are your node’s own. | QuickNode's plan table lists Trace and Debug from the Build plan up; the Ethereum and Base method pages add limited use on the Free Trial. eth\_getLogs is limited to 5 blocks per query on the Free Trial and 10,000 blocks on paid plans. | Novacula does not gate methods by plan. |
| Endpoint reliability | A pool puts several of your own nodes behind one domain and one TLS certificate. Unhealthy or unsynced members leave rotation automatically, and a request that never reached a member is retried on the next one. The pool endpoint serves HTTP JSON-RPC only. | Endpoints are backed by QuickNode’s fleet, with load balancing and failover operated by QuickNode. | Both give you one address to point clients at. The difference is whose fleet stands behind it. |
| Operational visibility and alerts | Node health, synchronization, peers, resource usage, metrics and process logs in the Hub. Preset alerts, no query language to learn, delivered to Slack, Microsoft Teams, Telegram or a webhook. | No node-level metrics such as peers, sync or resources are documented, for standard endpoints or for Dedicated Clusters | Novacula reports on the nodes themselves and alerts you where your team already works. QuickNode reports on the endpoints in front of them; its documentation describes no node-level monitoring for Dedicated Clusters either. |

## **Novacula vs QuickNode FAQs**

<AccordionGroup>
  <Accordion title="What is the main difference between Novacula and QuickNode?">
    Novacula is designed for teams that want to run and manage blockchain nodes on infrastructure they control. QuickNode provides managed blockchain infrastructure, APIs and data services, including dedicated clusters that QuickNode operates on its own infrastructure.
  </Accordion>

  <Accordion title="Does Novacula replace QuickNode?">
    Not necessarily. Teams can run Novacula-managed nodes alongside third-party managed RPC services when that architecture fits their requirements.
  </Accordion>

  <Accordion title="Who controls the infrastructure with Novacula?">
    Your team controls the infrastructure where the nodes run, while Novacula centralizes deployment, monitoring and supported lifecycle operations.
  </Accordion>

  <Accordion title="How does monitoring differ between Novacula and QuickNode?">
    Novacula focuses on node health, synchronization, peers, resources, metrics and process logs, with preset alerts delivered to Slack, Microsoft Teams, Telegram or a webhook. QuickNode provides visibility into managed endpoint usage, request activity, logs and API metrics, with a Prometheus export of endpoint metrics available to Enterprise customers.
  </Accordion>

  <Accordion title="How does QuickNode pricing work?">
    QuickNode primarily uses plans with included API credits and request-per-second limits. It also offers Flat Rate RPS pricing on Ethereum, Base, Optimism, Arbitrum, BSC, Polygon and Solana mainnet endpoints, and custom Enterprise options. Plan structure is as published in September 2026.
  </Accordion>

  <Accordion title="When may Novacula be a better fit than QuickNode?">
    Novacula may be a better fit for teams that want direct control over where nodes run and which clients they run, need node-level operational visibility, or want requests served by nodes on infrastructure they control.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.