Skip to main content
This page is the canonical catalog of every deployment available in Chainstack Self-Hosted — the protocols, networks, clients, client versions, resource requirements, and exposed ports. The System requirements and Deploying nodes pages link here for the per-deployment details.

​
Available deployments

vCPU and RAM figures are the standard preset totals. Ethereum networks also ship a Light preset that uses half the CPU and RAM with the same storage — see EVM Layer 1 below.
The sections below group these deployments by architecture family. Each family shares the same client topology, networking guidance, and operational caveats.

​
EVM Layer 1 (execution + consensus)

Runs a paired execution client and consensus client. vCPU and RAM are split evenly across the two clients. These deployments bootstrap from a pre-built chain snapshot rather than syncing from genesis. Snapshot bootstrap temporarily requires about 2× the steady-state storage while the archive is downloaded and extracted — provision the node’s volume at the peak. See Initial sync times. Each Ethereum network offers two preset tiers:
  • Standard — 8 vCPU / 32 GiB total, for production.
  • Light — 4 vCPU / 16 GiB total with the same storage, for evaluation. You can move between tiers without resizing disks.

​
Exposed ports

The execution client’s auth RPC port (8551) and the consensus client’s P2P port (13000) are used internally between clients and are not exposed.

​
EVM Layer 2 — OP Stack

Runs a paired execution client and rollup (consensus) client. vCPU and RAM are split across the two clients.
OP Stack deployments require an Ethereum Layer 1 RPC endpoint and a Beacon API endpoint that you supply. The node uses them to derive Layer 2 state from Layer 1.
Optimism Mainnet bootstraps from a pre-built snapshot (plan for ~2× storage during deploy). Base, Unichain, and Zora sync without a snapshot.

​
Exposed ports

The execution client’s auth RPC port (8551) is used internally between clients and is not exposed.

​
Polygon PoS

Runs a paired execution client (Bor) and consensus client (Heimdall). vCPU and RAM are split across the two clients.
Polygon PoS requires an Ethereum Layer 1 RPC endpoint that you supply. Heimdall uses it to track checkpoints on Ethereum.

​
Exposed ports

The Bor P2P port (30303) and the Heimdall CometBFT RPC (26657) and P2P (26656) ports are used internally and are not exposed.

​
Starknet

Runs a single full node client (Pathfinder v0.22.5).
Starknet requires an Ethereum Layer 1 RPC endpoint that you supply.

​
Exposed ports

​
TRON

Runs a single full node client (Java-Tron GreatVoyage-v4.8.1.1).

​
Exposed ports

The gRPC API port (50051) is used internally and is not exposed.

​
Bitcoin

Runs a single full node client (Bitcoin Core 31) with the transaction index (txindex) enabled.

​
Exposed ports

The P2P port (8333) is used internally and is not exposed.

​
Coming soon

See the FAQ for the roadmap.
Last modified on July 6, 2026