Guides

How Azxa works

What you buy when you host with Azxa — and what we run day to day.

Dedicated node hosting

Azxa operates your blockchain node on isolated hardware. We do not multiplex production trading or DApp traffic through a single shared RPC pool. CPU, RAM, and disk are sized for the chain and your workload.

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 (47+ chains).

What we operate

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

What you build

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

More about the company — About Azxa .