Free
A safe starting point for prototypes and light integrations.
$0
- Litenode
- 1 RPS
- 30 days
Connect directly to a Mainnet LiteServer or add archive history. Start free, pay from balance, or reserve throughput for a fixed period.
Use the free tier, pay only for requests, reserve capacity for a fixed period, or request dedicated infrastructure.
A safe starting point for prototypes and light integrations.
$0
Top up your balance and pay only for requests you actually make.
$0.01 / 1K
Choose an RPS limit and reserve access for 30 days.
From $20
Dedicated infrastructure, allowlists, or unusual traffic profiles.
Custom
Choose a billing model, data depth, throughput, and period. Invalid combinations are removed automatically.
What you get
A private liteserver is a TON liteserver whose access keys are issued to one client instead of being published in the public global config. TONNode's Litenode serves current chain state — accounts, recent blocks, get-methods. Archive serves full history since genesis — old blocks, deep transaction walks, block proofs. Both are reached over native ADNL with a standard global.config.json — no SDK fork, no HTTP gateway.
On TON, “RPC” means the native ADNL liteserver protocol — there is no canonical JSON-RPC. A TONNode endpoint is TON RPC in the direct sense: your liteclient speaks ADNL to the node, with no HTTP gateway in between.
Every TON lite server we operate is private: keys issued to you alone, never published in the public config. Archive is a full archive liteserver — every block and transaction since genesis.
A liteserver answers from sealed blocks. To see pending messages before they land in a block, TONNode has a separate product, the TON mempool stream, delivered over WebSocket and paid from the same balance.
| Public global config | TONNode | |
|---|---|---|
| Access keys | Shared by everyone | Issued to you alone |
| Rate limits | Best-effort, contested | Your plan's own budget |
| Archive depth | Varies by server, unknowable | Full history since genesis on Archive plans |
A liteserver whose access keys belong to one client instead of the public global config. You connect over native ADNL with a standard global.config.json; the key inside it identifies your account and your rate limit.
Litenode serves current chain state: balances, recent blocks, get-methods. Archive holds the chain's full history since the genesis block, so deep transaction walks, old blocks and proofs keep answering no matter how far back they reach.
The standard mainnet config with the liteservers array replaced by TONNode's gateway entries carrying an Ed25519 key issued to you alone. ton-lite-client, pytoniq, tonutils-go, tonlib and the lite-client CLI accept it unchanged.
Your query reached past the light node's recent window and your plan has no Archive scope. Add Archive — the same config file starts answering — or keep queries within recent state.
Yes: private Litenode access at 1 RPS for 30 days. There is no request quota — the rate limit is the only cap. No card and no balance required.
Anything that speaks the ADNL liteserver protocol: ton-lite-client (JS/TS), pytoniq (Python), tonutils-go (Go), tonlib-based stacks and the reference lite-client CLI.
Not yet — every plan is mainnet today. For development, TON's public testnet config remains free to use; private testnet endpoints are planned.
TONNode sells dedicated throughput on private liteservers instead of whole machines: reserved 10 RPS is $20 per 30 days, 60 RPS is $90, 450 RPS is $490, and archive history starts at $90. Pay-as-you-go needs no reservation at all — $0.01 per 1,000 requests from balance.
Start with free mainnet access or configure production LiteServer and archive capacity in a few steps.