12 min read

Overview

For teams running blockchain workloads in production, a fast endpoint is only part of the job. You also need to trace incidents, control access, and pass the security reviews that larger customers require. Quicknode covers many of these needs on every paid plan. For teams that need more, the Enterprise plan adds capabilities such as:

• Higher or custom limits for requests and data delivery
• A named Solutions Engineer who helps plan and operate your workload
• Custom roles, SAML SSO, and Activity Logs
• Longer Observability history and endpoint log retention, with data export to your own monitoring tools

This guide walks through each production requirement, shows what paid plans already include, and explains what Enterprise adds. Each capability carries one of three labels:

• Enterprise feature: available on Enterprise plans only.
• Higher allowance: the capability exists on other paid plans, and Enterprise raises the limit or makes it custom.
• Scoped service: an option that Quicknode agrees for a specific workload. An Enterprise plan does not include every scoped service by default.

Whether you're evaluating Quicknode, comparing plans, or already on Enterprise, use the labels to see what you can configure yourself and what to raise with Quicknode.

TL;DR

• Enterprise offers higher or custom limits for requests and data delivery
• A named Solutions Engineer helps with architecture, evaluation, and production needs
• Enterprise adds the Observability API, endpoint logs API, data export, custom roles, SSO, and request filters
• Dedicated infrastructure, flat-rate billing, SLAs, and support terms are agreed per workload

What You Will Learn

• How to trace an incident with metrics, logs, and change history in the tools your team already uses
• How to give each team only the access it needs, and keep a record of every change
• How to limit which clients and requests reach your endpoints
• How to identify which limit your workload is reaching and discuss a higher or custom allowance with Quicknode
• How to choose between dedicated infrastructure and a fixed monthly RPC cost

What You Will Need

• Nothing is required. This guide explains Quicknode capabilities and has no code to run.
• Familiarity with Quicknode endpoints and the dashboard helps. To try the capabilities that paid plans include, create a Quicknode account.

Production Requirements at a Glance

Use this table to jump to the requirement you have. Each section explains the need, what is already on paid plans, what Enterprise adds, and where to start.

Requirement	Capabilities	Availability	Section
Plan and operate your workload	Named Solutions Engineer	Scoped service	Solutions engineering
Investigate an incident across endpoints	Observability API, endpoint logs API, Prometheus Exporter, CSV and JSON export, longer retention for Observability data and endpoint logs	Enterprise feature, higher allowance	Investigate incidents
Control who can change the account, and audit changes	Custom roles, SAML SSO, Activity Logs, member-change emails	Enterprise feature	Account access
Restrict which clients and requests reach an endpoint	Request filters, endpoint mTLS, IP custom header, Stealth Mode	Enterprise feature, scoped service	Endpoint traffic
Increase request capacity and data delivery limits	RPC throughput, API credits, endpoints, platform API limit, Streams, Webhooks, gRPC, IPFS, Enterprise backfilling	Higher allowance, scoped service	Scale
Workload isolation	Dedicated Clusters, Hybrid Dedicated gRPC	Scoped service	Isolation options
Predictable RPC costs	Enterprise Flat Rate RPS	Scoped service	Flat-rate billing
Pass uptime, support, and due-diligence reviews	Contractual SLA, 24/7 support, security reports, volume pricing, early chain access	Scoped service	Operational requirements

Work with a Solutions Engineer Who Knows Your Stack

Enterprise accounts get a named Solutions Engineer (SE): a technical partner who learns your architecture, chains, methods, and traffic patterns, and works with you from evaluation through production.

Plan and Validate Your Workload

Your SE helps map your requirements to Quicknode products, review architecture, and define proof-of-concept success criteria. If you are migrating from another provider or self-hosted nodes, they help plan the move by chain or workload.

Review and Improve Production Operations

Once you are in production, your SE helps review usage and performance, investigate issues, and identify opportunities to tune costs. When an issue needs Engineering, they bring the workload context and evidence into the escalation. They also carry your product requests to the relevant team with your use case attached.

Agree on the scope and cadence of this work with Quicknode, including architecture reviews, monitoring, and any custom engineering requests. For contractual support coverage and response commitments, see Uptime, Support, and Compliance Requirements.

Investigate Incidents and Usage Across Endpoints

When production traffic goes wrong, you need to find the cause quickly and keep the evidence where your team works. This section shows how to get metrics, logs, and history out of Quicknode and into your incident process.

For example, the error rate on a production endpoint rises after a deploy. To act, you need the affected endpoint and method, the time the errors started, and whether transactions still reached the network. You also want the evidence in the tools your team already uses for incidents.

On every paid plan, the Observability dashboard shows account-wide traffic, usage, performance, errors, and transactions in one place, with filters for network, method, endpoint, and tag. The Errors and Transactions tabs need the Accelerate plan or higher. For many investigations, this is the right first stop.

Enterprise adds ways to move that data out of the dashboard and into your own workflow:

• Observability API (Enterprise feature): read-only Admin API methods for account usage, traffic, errors, and recorded transaction submissions. Use it to pull incident data into a runbook, a status report, or an internal tool. Enterprise accounts request access through Quicknode. See the Observability API overview.
• Endpoint logs through the API (Enterprise feature): retrieve an endpoint's logs with filters and pagination through the Admin API or the Quicknode CLI (qn endpoint logs). Other paid plans view endpoint logs in the dashboard.
• Prometheus Exporter (Enterprise feature): scrape Quicknode metrics into Prometheus and chart them next to your own services. The Integrations tab in Observability shows the scrape endpoint for your account. The Prometheus Exporter guide builds a Grafana dashboard from it.
• CSV and JSON export (Enterprise feature): export Traffic, Usage, Errors, and Transactions data with your filters kept, for a postmortem or further analysis.

Enterprise also keeps this data longer, which helps when an incident comes to light days after it started. Each dataset has its own retention policy. The pricing page compares retention across plans, and the dashboard guide covers Activity Logs:

Dataset	What it records	Enterprise	Self-service
Observability history	Aggregated traffic, usage, errors, and transaction records	90 days	30 days on Business
Endpoint logs	Error logs and transaction logs for one endpoint	Up to 14 days	One day on Business
Activity Logs	Account and endpoint configuration changes, with the member who made each one	Indefinitely, for active Enterprise accounts	Enterprise feature, enabled on request

When an endpoint's error rate rises after a deploy, each dataset answers a different part of the investigation. Observability history shows when the error rate changed, and on which endpoint and method. Endpoint error logs show failed requests, while transaction logs record transactions submitted through the endpoint. Their retention window is shorter, so pull them early in the investigation. Activity Logs show whether someone changed the endpoint configuration just before the errors started; Account access covers them in more detail.

Control and Audit Account Access

As your team grows, set account-level access controls so people can view only the resources and modify only the settings their role requires. Keep a record of changes so you can see who changed what and when.

For example, a data team needs to watch usage and manage Streams. They should not be able to delete a production endpoint or change billing.

All paid plans include role-based access control (RBAC) with three built-in roles (Admin, Billing, and Viewer), plus teams that limit which endpoints, API keys, Streams, and Webhooks a member can see. The Team Management and RBAC guide explains members, teams, and roles. The Advanced Account and Team Management guide shows how to organize a large account with tags and teams.

These controls are enough for many teams. When an organization needs finer roles, central sign-in, or a full audit trail, Enterprise adds:

• Custom roles (Enterprise feature): select individual permissions for a role, so the role matches a job instead of the nearest built-in role. Create them on the Roles page. See Custom Roles.
• SAML SSO (Enterprise feature): members sign in to Quicknode through your company identity provider. Joiners, leavers, and sign-in policies then follow the process your company already runs. Quicknode sets up SSO onboarding with you. SSO accounts have restrictions on joining other accounts, so review them before you onboard existing users.
• Activity Logs (Enterprise feature, enabled on request): a record of who changed what, and when, across endpoints, security settings, rate limits, members, API keys, and billing. Read them on the Account page Activity tab, on an endpoint's Activity Logs tab, or through the Activity Logs API, which needs an API key with the Admin role. Contact Quicknode to enable them. The dashboard guide lists the logged events.
• Member-change emails (Enterprise feature): owners and admins receive an email when a member is invited to or removed from the account. The email is an early signal of an unexpected access change. Activity Logs keep the full record; the emails cover member invitations and removals only.

Protect RPC Endpoint Traffic

A production endpoint should accept only the clients and requests that you expect, and reject the rest. For example, if an RPC endpoint is used only by a backend service, configure it so that backend service is the only client that can access it.

All paid plans include token authentication, JSON Web Tokens (JWT), IP and domain allowlists, method allowlists and blocklists, and rate limits by method from the Accelerate plan. The Endpoint Security Best Practices guide compares them.

Enterprise adds controls for tighter requirements:

• Request filters (Enterprise feature): a method allowlist checks only the method name. A custom request filter matches a pattern against the JSON-RPC request body, such as a parameter value that your application always sends. A request that matches no filter is rejected. See Request Filters.
• Endpoint mTLS (Enterprise feature): the endpoint accepts only clients that present a trusted client certificate. In the dashboard, open the endpoint Settings, then Authentication. Add the certificates that your clients will present first, then enable mTLS. No separate request to Quicknode is needed. Endpoint mTLS protects requests to your RPC endpoint. It is separate from mTLS on a Streams webhook destination, which protects the delivery from Quicknode to your server.
• IP custom header (Enterprise feature): when your traffic passes through a proxy or a load balancer, Quicknode sees the proxy address. Set the header that carries the original client IP, so IP-based security controls apply to the real client. See the IP custom header method.
• Stealth Mode (scoped service): logging suppression for sensitive activity, available on shared and dedicated infrastructure. Discuss the scope with Quicknode. See the Enterprise page.

Scale Requests and Data Delivery

As your workload grows, you may reach limits on RPC requests, data delivery, or platform API calls. This section explains those limits and what Enterprise increases.

For example, RPC traffic increases after a launch, and requests begin hitting the endpoint’s throughput limit. Identify which limit is constraining the workload. Each limit has its own unit, and raising one does not impact the others. The pricing page compares these limits across plans. The table shows what changes on Enterprise:

Limit	What it counts	Scale plan	Enterprise	Reference
API credits	Usage across Quicknode products	950 million	Custom allowance	Pricing
RPC throughput	Requests per second (RPS) to your endpoints	250	Custom, scoped to the workload and its methods	Pricing
Endpoints	Endpoints on the account	50	Unlimited	Pricing
Platform API rate limit	Combined administrative API calls	60 RPS sustained; burst capacity of 120 requests	250 RPS sustained, with a burst capacity of 500 requests	Platform API Rate Limits
Streams destinations	Destinations for one Stream	Up to four	Up to six	Streams destinations
Solana Streams	Active Solana Streams at the same time	5	10	Pricing
Webhooks	Active Webhooks; included payloads	50; approximately 31.7 million	Custom	Pricing
Solana gRPC	Accounts per stream subscription	10	Custom	Pricing
Hyperliquid streaming	Concurrent streams; named filters per stream	15; up to 25	Custom	Hyperliquid pricing
IPFS	Storage, bandwidth, and pinning	35 GB/month storage; published usage rates	Custom terms	Pricing

Two limits need a closer look:

• Platform API rate limit. Every plan has a limit on calls to the platform APIs, and it is separate from your RPC endpoint throughput. One shared bucket covers all five APIs, so an automation that creates endpoints draws from the same capacity as a Streams sync. On Enterprise, the bucket sustains 250 requests per second. The burst capacity of 500 requests absorbs short spikes; it does not allow 500 RPS as a steady rate. Requests above the limit return HTTP 429, so throttle and retry with exponential backoff and jitter.
• Streams destinations. One Stream can deliver the same data to more systems, for example a webhook for alerts, a PostgreSQL database for queries, and S3-compatible storage for an archive. More destinations per Stream means you do not need to duplicate a Stream to feed another system.

Where the table says Custom, there is no single Enterprise number. Tell Quicknode what your workload needs, measured in the unit of that limit, and the allowance is set for it.

Data delivery also covers history. When a Stream needs a larger-scale historical backfill, Enterprise backfilling (scoped service) gives you a custom solution with dedicated support, arranged through Sales. See Streams backfilling.

Isolate Your Workload

When a workload needs capacity that other customers do not share, choose infrastructure that matches its isolation requirements. For example, a trading backend may need dedicated capacity during market spikes.

Requirement	Option	What to know
Full workload isolation, or a custom geography or configuration	Dedicated Clusters	Infrastructure for your organization only. Quicknode scopes the deployment with you for your workload. An Enterprise plan does not put every endpoint on dedicated hardware.
A reserved Solana gRPC node with automatic failover to a shared pool	Hybrid Dedicated gRPC	A single reserved gRPC node with automatic failover to a shared pool. It is not a cluster, and it is available on Solana only.

The Custom RPC Options page covers dedicated and hybrid deployments, where Dedicated Clusters appear as the Fully Dedicated Setup. Hybrid Dedicated gRPC reserves a node but uses a shared pool for failover; choose Dedicated Clusters when you need full workload isolation.

Plan for Predictable RPC Costs

A workload can need a predictable bill without requiring dedicated hardware. For example, a team running a steady indexer on one chain may want the same RPC bill every month. Enterprise Flat Rate RPS sets a fixed monthly price for configured capacity. Enterprise Flat Rate RPS does not lock the workload to a single region. Deployment scope is agreed with Quicknode.

Requirement	Option	What to know
A fixed monthly RPC cost for steady traffic on one chain	Enterprise Flat Rate RPS	A billing option with fixed requests-per-second and concurrent-connection limits. It does not add isolation. Enterprise accounts set it up through Sales, on annual terms.

The Flat Rate RPS page explains how fixed pricing differs from credit-based billing.

Uptime, Support, and Compliance Requirements

Before a company signs, its procurement and security teams ask about commitments, not features. This section lists what Quicknode can put in a service agreement, so you know what to ask for. The Enterprise page lists what Quicknode offers:

• Contractual uptime SLA: the service agreement documents uptime commitments and service credits.
• Support: dedicated support with a premium SLA, 24/7 on-call engineering, and a named Solutions Engineer and Support Engineer. The service agreement documents response and resolution times. On the Business+ tiers (the three tiers above the Business plan), priority support is available as a paid add-on; the pricing page compares support across plans.
• Security and compliance reports: SOC 1 Type 2, SOC 2 Type 2, and ISO 27001 reports are available on request, and Quicknode answers security questionnaires. The reports describe Quicknode's controls. They do not certify your own application. See Quicknode Security.
• Volume pricing: pricing that reflects the workload you commit to.
• Early chain and network access: test new chains and testnets before general availability. Quicknode confirms availability for each chain or network.

These are scoped services, and each one follows the service agreement. When you talk to Quicknode, ask for the terms that apply to your workload rather than assume one standard package.

Conclusion

Production requirements rarely arrive as a plan name. They arrive as an incident to explain, a team to onboard, a security review, or a workload reaching its capacity limits. Start from the requirement, check what paid plans already cover, and use the labels in this guide to see whether the answer is an Enterprise feature, a higher allowance, or a scoped service.

If you are evaluating Enterprise, take the requirements from the table at the top to a conversation with a Solutions Engineer. If your account is already on Enterprise, follow the links in each section to configure a capability or to request it.

Next Steps

• Set up access for each team: follow the Team Management and RBAC guide to plan roles and teams.
• Harden your endpoints: compare the controls in Endpoint Security Best Practices.
• Bring metrics into your monitoring: build a Grafana dashboard with the Prometheus Exporter.
• Track usage and alerts: see how to monitor RPC usage and set up alerts with the Admin API.
• Find related guides: see all guides tagged Enterprise.

Frequently Asked Questions

Which Enterprise capabilities extend products that are on other paid plans?

Many of them. The Observability dashboard, built-in roles and teams, method allowlists, Streams, and the platform APIs are on paid plans. Enterprise adds the Observability API, endpoint logs through the API, the Prometheus Exporter, data export, custom roles, request filters, and higher or custom limits on top of them.

Do all Enterprise endpoints run on dedicated infrastructure?

No. Dedicated Clusters and Hybrid Dedicated gRPC are scoped services that Quicknode agrees separately for a workload. An Enterprise plan on its own does not put every endpoint on dedicated hardware.

How do Observability history, endpoint logs, and Activity Logs differ?

They are three datasets with separate retention. Observability history holds aggregated traffic, usage, and error data. Endpoint logs record failed requests and transaction submissions for one endpoint over a shorter retention window. Activity Logs record configuration changes and who made them. The pricing page and the dashboard guide list the retention for each.

Which Enterprise capabilities can I set up myself, and which need a request?

Custom roles, request filters, and endpoint mTLS are configured in the dashboard or through the Admin API. Activity Logs and Observability API access are enabled on request. SSO onboarding, custom allowances, and scoped services such as Dedicated Clusters are set up with Quicknode.

Is every service in this guide included in every Enterprise agreement?

No. Enterprise features are part of the Enterprise plan, but scoped services, custom allowances, support terms, and uptime commitments follow each service agreement. Ask Quicknode which ones apply to your workload.