Dedicated blockchain nodes
Your own nodes on dedicated servers, provisioned as code, monitored, upgraded on a schedule and taken out of rotation automatically when they fall behind.
We run dedicated, self-hosted blockchain nodes for crypto-asset service providers, payment firms and exchanges that need their own auditable infrastructure instead of a shared RPC provider. We deploy nodes for any public chain, including Bitcoin, Ethereum and its L2s (Polygon, Arbitrum, Optimism, Base), Solana, BNB Chain, TON and TRON, and for private EVM networks. Pricing starts at €350 per network per month, and setup takes 1–2 weeks.
We agree which chains, how many nodes per chain, full or archive, and where they run.
Servers ordered in your name, built with Terraform and Ansible, and joined to a private mesh VPN.
Nodes sync, health checks and load balancing are switched on, and failover is tested.
Monitoring, alerts, rolling upgrades and a monthly report on sync health and changes.
We are not limited to a fixed list. A node is a client binary, a disk, a sync process and a health check, and we build all four as code for whatever chain you need. These are the major networks:
| Family | Networks |
|---|---|
| Bitcoin and forks | Bitcoin, Litecoin, Dogecoin, Bitcoin Cash |
| Ethereum and EVM | Ethereum, BNB Chain, Polygon PoS, Arbitrum, Optimism, Base, Avalanche C-Chain, Gnosis, private EVM networks |
| Other L1s | Solana, TON, TRON, XRP Ledger, Cardano, Polkadot, Cosmos SDK chains, NEAR, Aptos, Sui, Stellar |
Networks in bold run in our production fleet today. Anything else (another L2, an appchain, a testnet or a private network) is available on request: we check the client software and hardware needs and quote it the same way.
A node can accept connections and still be hours behind the chain. If your deposit service reads from it, payments look missing. Standard load-balancer checks do not see this.
Our health checks ask each node what block it is on and compare it with the network. Only nodes that are in sync receive traffic. A node that falls behind after an upgrade, a restart or a disk problem is removed automatically and put back when it has caught up.
Everything is defined as code. Terraform creates the servers, Ansible configures them, and access goes through a mesh VPN with policies in Git. When an auditor asks who can reach your nodes, how they are changed and how you would rebuild them, the answer is a repository, not a memory.
The servers are rented in your name, so the infrastructure stays yours if you ever stop working with us.
We do not provide custody, staking or validator services, and we do not hold private keys. We run the infrastructure that your applications read from and broadcast through.
Eight blockchain networks on dedicated servers, built with Terraform and Ansible. A custom health daemon knows when a node has fallen behind the chain and takes it out of rotation on its own.
Any public chain, and private EVM networks. The major ones are listed in the table on this page: the Bitcoin family, Ethereum and EVM chains (Polygon, Arbitrum, Optimism, Base, Avalanche and others) and other L1s such as Solana, TON, TRON, XRP Ledger, Cardano and Cosmos-based chains. Eight of them run in our production fleet today. For any other network we check the client software and its hardware needs, then quote it the same way.
Our fee starts at €350 per network per month, excluding VAT. The dedicated servers are separate: they are rented in your name, so you own the infrastructure. Heavy networks such as Solana or archive Ethereum need larger servers.
For many projects, that is fine. Regulated firms often need more: data that no third party can see or filter, no shared rate limits, and infrastructure they can describe to an auditor. Your own nodes give you that.
Our health check compares the node's block height with the network. If it lags, the load balancer stops sending it traffic until it catches up, and an alert goes out. Your application keeps talking to healthy nodes.
No. We run nodes for reading chain data and broadcasting transactions. Key management and custody stay with you and your custody provider.
Usually 1–2 weeks. Most of that time is the initial sync, which depends on the network.
Tell us which networks you need and how you use them. We will suggest a layout and send a fixed setup quote.