Independent control. Connected operations.

Public, private, or hybrid participation

Private clusters support owner-authorized validator admission. Permission tokens can independently govern trading, access to other wallets' records, and movement of assets outside the cluster. Public clusters serve open participation use cases.

Explicit governance and authority

Signed cluster certificates define timing, fees, capacity parameters, storage limits, and security requirements. Authority certificates support delegation and expiry. Clusters can require proposal approval for applications, contracts, assets, and currencies.

Controlled reads and encrypted history

Permissioned RPC queries require authorization and signed requests. Private clusters can encrypt epoch data and apply inbound transaction controls. These mechanisms support a deployment's security requirements; organizational policies determine how they are operated.

Technical controls support compliance work. Jurisdiction-specific compliance depends on the actual deployment, processes, and applicable requirements.

SQL with coordinated state changes

Per-contract relational databases support structured application records. Database writes are validated and committed with successful contract execution. A failed execution rolls back its requested changes, reducing partial state within that transaction boundary.

Issued currencies with explicit controls

Define your currency's supply, precision, and permissions through mint certificates. Private-cluster options include encrypted ledger data, owner lists, and transaction reversals. Currencies configured with bank-ledger requirements operate within a single cluster.

Predictable pricing and storage responsibility

Fiat-pegged hosting and usage pricing helps teams budget in familiar terms while the corresponding coin amount adjusts. Storage rent can be assigned independently of asset ownership, and storage classes distinguish active data from archival needs.

Independent participants

Each organization can operate a cluster with its own admission, permissions, and workload profile. Shared processes need not imply unrestricted access to another participant's underlying records.

Atomic cross-cluster operations

Our native commit protocol coordinates all-or-nothing operations across clusters. Participating actions succeed together or roll back together, with permissions and currency-specific controls enforced throughout the operation.

Applications across industry boundaries

Build trade-document workflows, supply-chain provenance, institutional settlement, and records exchange on ITZA. Define your participants, authoritative data, access policies, and external integrations around the way your business operates.

Dedicated performance configuration

Configure block cadence and capacity through cluster certificates. Choose accessible computers for smaller workloads or higher-performance, colocated nodes for demanding latency and throughput requirements. The protocol stays the same as your hardware and capacity grow.

Operate and inspect from the nodes

Node interfaces expose cluster health, validator timing, transaction tracking, bandwidth, and resource use. Snapshot synchronization and archival mechanisms support node operation and recovery.

Define a deployment you can evaluate

Begin with the workload, participants, data boundaries, service requirements, and acceptance criteria. A pilot should demonstrate actual application behavior, recovery, integration, and measured performance before broader rollout.