Skip to content
HeroRPC

TON logoTON node

A dedicated TON node. Your own API, steady under load.

Running a TON node means keeping a computer in step with The Open Network, so it can answer questions about it. A dedicated TON node answers only your Telegram mini app, wallet or payment service. Its server is sized for TON, and a backup node sits next to it. No public rate limits in your way.

Full
$289/mo
Ready
24 h
your appyour TON nodenodes.herorpc.comin syncbackup nodeincluded
Your TON node and a second one as backup, side by side on mainnet.

02Node type

Full node, liteserver or archive: what TON offers.

TON has several node kinds. We sell the full node, and this is how it differs from the others.

Full node

$289/mo

Keeps
The recent state of the chain. It prunes old blocks
Query
Balances, transactions, blocks and sending messages, through an HTTP API
Cannot
Return the whole history. That is the archive liteserver, which keeps everything
Liteserver
A full node plus a mode that answers light clients over ADNL, TON's own protocol
Disk
About 1 TB for a full node, and about 12 TB for an archive node, per the docs overview

The one-line test

If your service needs today's balances and fresh transactions, a full node is right. If it needs all of TON's history, that takes an archive node, and it takes the biggest disk.

Sources: TON docs, nodes overview, checked October 2026; TON docs, MyTonCtrl setup, checked October 2026

03How it works

How a TON node works: ADNL inside, HTTP outside.

The node itself does not speak HTTP. The front door is what makes it easy to use.

  1. TON node

    The official node software, installed and managed with MyTonCtrl.

  2. One UDP port

    The node needs a single UDP port forwarded, picked at random unless it is set.

  3. HTTP API front

    A plain node answers over ADNL. An HTTP layer in the toncenter style turns that into calls your code already knows.

  4. Your endpoint

    The HTTP API lives on your own nodes.herorpc.com address, behind your key.

TON's own network protocol is ADNL. Light clients talk it directly. Most apps would rather send ordinary web requests.

So a liteserver node needs an HTTP front before an ordinary web app can use it. The docs point to TON Center style APIs for that.

Your endpoint is the front: send HTTP API calls to it with your key in the URL, and the node behind it handles the rest.

04Know the field

TON disk: where two docs pages disagree.

A full node is about 1 TB. The archive number depends on which page of the TON docs you read.

TON node disk, per the TON docs
Full node or liteserver1 TB+
Archive, per the overview and quickstart12 TB+
Archive, per the requirements table20 TB+

The docs call the disk the usual bottleneck, and say to benchmark it before you commit. Archive data is downloaded through TON Storage at install.

  • Full node

    Disk
    About 1 TB
    Source
    TON docs, nodes overview
  • Liteserver

    Disk
    1 TB+ NVMe, traffic peaks near 16 TB a month
    Source
    TON docs, MyTonCtrl setup
  • Archive liteserver

    Disk
    12 TB+ in the quickstart, 20 TB+ in the requirements table, or compressed ZFS
    Source
    TON docs, MyTonCtrl setup
  • Validator

    Disk
    1 TB+ NVMe, about 64 TB of traffic a month typical
    Source
    TON docs, MyTonCtrl setup

All of these run the same node software, set up with MyTonCtrl. We sell the full node.

Sources: TON docs, nodes overview, checked October 2026; TON docs, MyTonCtrl setup, checked October 2026

05TON, specifically

Six TON facts worth knowing before you build.

Small things in the docs that decide whether a TON node behaves.

Five kinds of node

Full node, liteserver, archive liteserver, validator and collator. They all come from the same software.

Traffic is the hidden cost

The docs put a validator at about 64 TB of traffic a month, with peaks near 100 TB. A liteserver peaks near 16 TB.

Disk speed beats size

The docs say disk latency is usually the bottleneck. A big, slow drive is the wrong buy.

One UDP port

The node needs one UDP port forwarded to it. The liteserver port has to be opened as well.

Public endpoints have a place

The docs call public endpoints fine for prototypes. For guaranteed uptime or high volume without limits, they say run your own.

Docs disagree on archive size

The overview and the quickstart say about 12 TB. The requirements table says 20 TB or more. Plan for the larger one.

Sources: TON docs, nodes overview, checked October 2026; TON docs, MyTonCtrl setup, checked October 2026

06Who rents one

Why teams rent a dedicated TON node.

TON apps grow fast, and public APIs are where they hit the wall.

Telegram mini apps and bots

Predictable throughput when a lot of users arrive at once.

Exchanges and payment services

Scan deposits and confirm transfers against a node nobody else shares.

Explorers and analytics

Read blocks and transactions at your own pace for dashboards and alerts.

Wallet backends

Balances and history for your users from an endpoint you control.

07Price check

What a dedicated TON node costs elsewhere.

We could not confirm a published price for a dedicated TON node from other providers, so there is no comparison bar here. Ours is listed up top and in the box below.

08What you get

Set the term for your TON node.

Pick the node type and how long to prepay. The price updates as you choose.

TON logo

Your TON node

Term

  • A dedicated server sized for TON
  • The official TON node software, managed with MyTonCtrl
  • A backup node, included
  • A private endpoint on nodes.herorpc.com
  • Your server logins
  • No setup fee, ready within 24 hours

$289

a month, full node

Billed monthly

Get your TON node

Pay in BTC, ETH, USDT, USDC, BNB, SOL, TRX, LTC, DOGE or XMR.

10Questions

TON node questions

Real questions from node operators, answered plainly.

What is the difference between a TON full node, liteserver and archive node?

A full node keeps recent state and prunes old blocks. A liteserver is a full node that also answers light clients over ADNL. An archive liteserver keeps every block and never prunes.

Why does my TON node sync so slowly?

Disk latency is the usual cause, according to the TON docs. A fast NVMe drive matters more than a big one. Benchmark the disk before you blame the network.

Does a TON node give me an HTTP API?

Not by itself. A plain node speaks ADNL. Your endpoint adds an HTTP API in the toncenter style in front of it, so ordinary web code can call it.

How much disk does TON need?

About 1 TB for a full node. For archive, the docs say 12 TB in one place and 20 TB or more in another, so the safe plan is the larger figure.

How much traffic does a TON node use?

A lot. The docs say a validator typically moves about 64 TB a month and a liteserver peaks near 16 TB. Plan your bandwidth before you plan your disk.

Can a TON node run a validator too?

The same software can. A validator needs far more traffic, about 64 TB a month by the docs, and we sell the full node only.

Will my TON library work with my endpoint?

Libraries that accept a toncenter-style endpoint, such as the TON TypeScript client, can use it in place of a public one.

How much is a TON node a month?

$289, with no setup fee. Prepay 12 months and the monthly price drops 25 percent.

When will my TON node be ready?

Within 24 hours of payment. Your dashboard lists the HTTP endpoint and the server logins once it is.

A TON node that is only yours.

$289 a month, with a backup running beside it, live within 24 hours.