Choose your subsсription

• Ethereum
• Polygon PoS
• BNB Smart Chain
• Avalanche
• NEAR
• Fantom
• Solana
• Harmony
• StarkNet
• Tezos
• Hyperledger Fabric
• Corda
• Bitcoin
• Quorum
• MultiChain

• Amazon Web Services
• Microsoft Azure
• Google Cloud Platform
• Virtuozzo

• Asia-Pacific
• Europe
• the United States

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.

Our Growth, Business, and Enterprise plans address specific needs related to your blockchain adoption journey. We anticipate enterprises taking advantage of our multi-cloud and multi-region deployment options to run the services and applications, as well as enjoying advanced customization options of the networks and nodes. Management, infrastructure and support costs per node are higher on the premium plans, therefore the compute is more expensive.

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 nodes on a public chain.

There is no storage cost for elastic nodes on a public network since Chainstack absorbs this cost.

An elastic node is highly scalable public network node infrastructure accessed through your exclusive endpoint. With an elastic node, you pay for JSON-RPC requests to the node and do not pay for the compute and storage resources used by the node.

A dedicated node is a public network node deployed exclusively for you. With a dedicated node, you pay for the compute and storage resources used by the node and do not pay for JSON-RPC requests to the node.

In offering two options, Chainstack offers great flexibility in choosing the right node type for your requirements.

A request is a single successful JSON-RPC call to a node through an HTTPS or WebSocket Secure endpoint.

A request is considered successful and consumed in the following cases:

• HTTP: the server returns 200
• WebSocket: the server sends a message

For example, sending an eth_getLogs request over HTTP will return all events specified in the request and count as one request.

Sending an eth_subscribe request over HTTP will subscribe to events in real time and each event sent will count as one request.

You can also view your node request metrics on your node details page.

Included requests are the number of requests allocated to your account’s subscription plan.

An extra request is a JSON-RPC call exceeding the monthly allocation of included requests.

A Warp transaction is the transaction sent using the `eth_sendRawTransaction` method to your node that has the Warp feature enabled. The node then propagates the transaction through the high-speed bloXroute transaction relay network and makes it near-instantly available for the validators to pick up and include in the next block.

Included Warp transactions are the number of transactions allocated to your account’s subscription plan that are sent using the `eth_sendRawTransaction` method to your node that has the Warp feature enabled.

An extra Warp transaction is a transaction sent using the `eth_sendRawTransaction` method to your node that has the Warp feature enabled and that is exceeding the monthly allocation of included Warp transactions.

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 elastic or dedicated Ethereum, Polygon, BNB Smart Chain, Avalanche, Fantom, Solana, Harmony, StarkNet, Tezos, or Bitcoin nodes.

A consortium project can contain Hyperledger Fabric, Corda, Quorum, or MultiChain networks.

Network refers to the actual blockchain network. This can be a public blockchain network on Ethereum, Polygon, BNB Smart Chain, Avalanche, Fantom, Solana, Harmony, StarkNet, Tezos, or Bitcoin. Or it can be a consortium-based blockchain network built on Hyperledger Fabric, Corda, Quorum, or MultiChain.

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 Ethereum, Polygon PoS, BNB Smart Chain, Avalanche, Fantom, Harmony, Tezos nodes 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 deployed with your consortium network to provide network services.

You are only charged for the use of peer nodes. The service nodes are always free.

See:

• Hyperledger Fabric service nodes
• Corda service nodes
• Quorum service node
• MultiChain service 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 of the same network in any combination of Chainstack-provided cloud hosting providers and private hosting providers.

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

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

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

• Standard: best effort email support for technical questions and issues.
• Dedicated: 24×5 availability with <12 hour response time.
• Priority: 24×7 availability with guaranteed SLA and priority ticket handling.