The simplest pricing in all of Web3

Request unit (RU) is a metric that measures the size and complexity of request processing for Chainstack request-based services.

It provides a unified way to bill users for different features, which allows us to offer a fairer and more flexible pricing structure. Now with request units, users can freely utilize them for:

• Regional Node
• Global Node
• Archive Node
• Subgraphs requests

The current cost for Chainstack services in RU is the following:

Along with request units we are introducing one unified amount of included request units to provide maximum pricing transparency and granular control of usage so you could allocate resources according to your needs.

Current amount of included request units is following:

• Developer plan has 3,000,000 included request units
• Growth plan has 20,000,000 included request units
• Pro plan has 80,000,000 included request units
• Business plan has 140,000,000 included request units
• Enterprise plan has 400,000,000 included request units

Now with request units, users can freely utilize them for:

• Regional Node
• Global Node
• Archive node
• Subgraphs requests

Extra usage is an amount of extra JSON-RPC calls exceeding the monthly allocation of included requests units. Its price depends on your subscription plan. 1M of extra request units cost:

• $20 on Developer plan
• $15 on Growth plan
• $12.5 on Pro plan
• $10 on Business plan
• Starting at $5 on Enterprise plan

When a customer experiences a significant increase in request volume, they may encounter a threshold for the number of requests allowed per second. This update is implemented to ensure the best performance and reliability for every customer.

Rate limits:

1. Developer plan – 25 RPS ≈ 625 CUs/API Credits per second
2. Growth plan – 250 RPS ≈ 6250 CUs/API Credits per second
3. Pro plan – 400 RPS ≈ 10,000 CUs/API Credits per second
4. Business plan – 600 RPS ≈ 15,000 CUs/API Credits per second

Included Archive node requests are now part of one unified quota for included request units.

Dedicated Node compute per hour price starts from $0.50 across all paid subscription plans.

We believe in transparent pricing and think that charging per hour for compute (including traffic) and storage is the best way to let our users pay only for what they use.

• Asia-Pacific
• Europe
• the United States

Chainstack charges node storage at the rate of $0.01 per 20GB/hour. This charge applies only to nodes on (a) a consortium network, and to (b) Dedicated Node on a public chain.

There is no storage cost for Global Node on a public network since Chainstack absorbs this cost.

On Chainstack, a project organizes your blockchain networks and nodes. There are two types of projects: public chain and consortium. Chainstack allows you to create an unlimited number of projects irrespective of the plan you choose.

A public chain project can contain Global, Trader, Dedicated or Unlimited nodes.

A user is someone who signs up on behalf of a member.

Consider Wheels Inc, an auto manufacturer. A user would typically be an IT manager, who is an employee of Wheels Inc and signs up on Chainstack to build a blockchain network on behalf of the organization.

See also Organizations, users, and members.

A member refers to an organization that is a participant in a project. An organization first creates a project and may then invite other organizations to participate in the project.

For example, Wheels Inc, an auto manufacturer, could create a project called Parts Tracking and invite Dreams Delivery, its logistics partner. Once Dreams Delivery accepts the invite, it can view the Parts Tracking project and its constituent networks.

Both Wheels Inc and Dreams Delivery are, therefore, members.

See also Organizations, users, and members.

Bolt is a Chainstack patented node synchronization technology.

Chainstack does regular snapshots of the blockchain data and keeps the data in the platform’s snapshot registry.

The platform restores the latest snapshot to every newly initiated node. As a result, every node deployed with Chainstack and Bolt syncs from the latest snapshot instead of from the genesis block.

Read more at the Chainstack blog.

Chainstack supports deploying nodes for over 25+ protocols on the mainnet in the following modes:

• Full node — a node that stores full blockchain data.
• Archive node — a node that stores full blockchain data and an archive of historical states. To be a part of the mainnet, you can deploy either a full node or an archive node. With a full node, you can query the historical state of the mainnet at only the latest 16 to 128 blocks. To be able to query the historical state of the mainnet at any block, you need an archive node.

A node that you deploy to interact with and be a part of a blockchain network.

Deployment of nodes of the same network in multiple Chainstack-provided cloud hosting providers.

Deployment of nodes of the same network in multiple Chainstack-provided cloud hosting provider regions.

Deployment of nodes and networks to a self-managed infrastructure.

Yes, you can manage your resources through the API. See API documentation.

Chainstack offers various support plans to meet different support needs.

Our support levels are:

• Community: Community support on Discord, Telegram, and knowledge base.
• Standard: Email and community support with <24/5 response time.
• Professional: Email and community support with <6hr response time.
• Premium: <1hr response time, 24/7, including dedicated chat support on Discord, Telegram and Slack, and additional assistance provided by a Technical Account Manager.

This table provides a detailed comparison of API request costs across Chainstack, QuickNode, and Alchemy. It highlights how different blockchain providers measure API usage, with Chainstack using Request Units (RUs), QuickNode using API Credits, and Alchemy using Compute Units (CUs). Each request type has a corresponding multiplier, showing how API consumption scales across different platforms. This comparison helps developers and businesses make informed decisions when choosing a blockchain infrastructure provider based on pricing and request efficiency.