TONNodeTONNode

Private TON LiteServer & archive access without operating a node.

Connect directly to a Mainnet LiteServer or add archive history. Start free, pay from balance, or reserve throughput for a fixed period.

Configure accessCompare plans
YOUR APPLICATIONApplication requestsTONNodePrivate node accessMAINNET LITESERVERCurrent blockchain stateARCHIVE LITESERVERHistorical data

Choose how you want to pay

Use the free tier, pay only for requests, reserve capacity for a fixed period, or request dedicated infrastructure.

Free

A safe starting point for prototypes and light integrations.

$0

  • Litenode
  • 1 RPS
  • 100,000 / 30 days

Pay as you go

Top up your balance and pay only for requests you actually make.

$0.01 / 1K

  • 30 RPS Litenode
  • $0.02 / 1K Archive
  • No expiry

Reserved capacity

Choose an RPS limit and reserve access for 30 days.

From $20

  • 10–450 RPS
  • Litenode
  • No per-request charges

Custom

Dedicated infrastructure, allowlists, or unusual traffic profiles.

Custom

  • Dedicated node or isolated pool
  • Custom RPS and concurrency
  • Monitoring, IP allowlists, priority support

Configure node access without guessing

Choose a billing model, data depth, throughput, and period. Invalid combinations are removed automatically.

How do you want to pay?
Data access
Reserved throughput

What you get

What is a private TON liteserver?

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.

Public liteservers vs TONNode

Public global configTONNode
Access keysShared by everyoneIssued to you alone
Rate limitsBest-effort, contestedYour plan's own budget
Archive depthVaries by server, unknowableFull history since genesis on Archive plans

Node access, answered

Get the TON access your workload actually needs.

Start with free mainnet access or configure production LiteServer and archive capacity in a few steps.

Configure accessDocs