Guides

How Azxa works

What you get with Azxa — shared RPC pool and dedicated node hosting — and what we run day to day.

Shared & dedicated RPC

Shared pool — start from $49/mo with an API key and regional endpoints. Ideal for DApps, indexers, and moderate traffic.

Dedicated nodes — isolated hardware sized for your chain and workload. We do not multiplex production trading traffic through a single shared gateway.

Regions

Infrastructure runs in Tokyo and Europe. Choose the region that matches your users, venues, or latency targets. Multi-region or redundant setups are available on request.

Node modes

Full node — canonical chain head, suitable for most RPC workloads.
Archive — historical state where the protocol supports it (common on EVM stacks).
Testnet — dev and staging environments aligned with mainnet configs.

Exact modes per network are listed on each network page (48+ chains).

What we operate

Chain client deployment, sync, and upgrades (including hard forks)
Monitoring, alerting, and operator response
JSON-RPC and WebSocket on your node or shared edge
Optional IP allowlists and access controls

What you build

Your bots, indexers, wallets, and backends connect via the API layer. Method-level reference lives under Networks in this documentation.

Questions about architecture or migration — contact the team .