Distributed infrastructure

A network shaped around the work.

ITZA can operate from accessible edge hardware through high-performance enterprise servers. Clusters match the application, and the wider network grows as clusters are added.

View live testnet
Distributed ITZA nodes connecting home, studio, regional, and enterprise infrastructure
Scale without a single hardware profile

Edge / Dedicated / Regional / Enterprise

CLUSTER MODEL

Independent where it matters. Connected where it counts.

A cluster is an operating unit with its own validators, policies, performance target, and ledger. Deterministic coordination connects those units without collapsing them into one bottleneck.

Public

Open participation

Public APIs, application discovery, shared identity, and broad validator participation.

Dedicated

Product-specific capacity

Configure timing, throughput, storage, and governance around one workload.

Private

Controlled boundaries

Owner-gated validators, permissioned queries, encrypted epochs, and movement controls.

SECURE AND SERVE

Launch a node.
Deliver your platform.

As soon as an app is deployed, a company, an independent developer, or anyone else can launch a node to help secure the network, including their own deployment, and start delivering the actual platform right away. The same node participates in network security and serves the application, its assets, and its public interfaces directly from the hardware.

Open the live node portal
ITZA node portalTestnet live
ClusterRoot network
InterfacesRPC + BOLT + Web
StatusConnected

LIVE PORTAL

Operate from the node itself.

The live portal demonstrates the breadth of the network surface available from a validator.

Monitor the network

Track cluster health, block height, epochs, transaction throughput, validator timing, bandwidth, and resource use.

Manage identity and assets

Create and inspect wallets, resolve readable handles, work with credentials, and manage encrypted data.

Deploy any app

Deploy and update any app on ITZA. Use WASM or EVM contracts where needed, and let the same node serve as the application gateway.

Use advanced primitives

Access escrow, arbitration, staking, governance, permissions, signatures, and certified randomness.