ITZALabs
Orbit App Store

The platform

One architecture.
Every layer.

ITZA connects the application surface to the runtime, data, identity, storage, coordination, and physical network beneath it. Each layer was designed as part of the same system.

Read the technical overview

SCALE OUT

Capacity grows by adding independent clusters.

Workloads stop competing for one global execution lane. Each cluster can be tuned to its hardware and purpose while deterministic cross-cluster coordination keeps the larger system connected.

Cluster ALocal applicationsCompact edge hardware
ITZA protocolAtomic coordinationShared identity and routing
Cluster BHigh-throughput workloadsEnterprise hardware
HorizontalCapacity adds linearly
IndependentPolicies and governance
InteroperableOne protocol surface

PLATFORM CAPABILITIES

The important parts are built in.

Use protocol primitives for common requirements. Add contracts where a product needs custom behavior.

Clustered horizontal scaling

Each cluster runs its own validators, leader schedule, ledger, timing, and workload profile. New clusters add capacity instead of dividing a fixed global limit.

  • 10ms to 1s block cadence
  • Configurable throughput target
  • Atomic cross-cluster operations

Every node is the interface

Once an app is deployed, anyone can launch a node to help secure the network and their deployment while immediately serving the app. Every node exposes HTTP and HTTPS RPC, the BOLT binary fast path, application assets, network discovery, and live event subscriptions.

  • No separate RPC provider
  • 35 query endpoints
  • Self-healing client connections

Two contract runtimes

ITZA supports native deterministic WASM and EVM-compatible bytecode, so applications can choose performance, language flexibility, or ecosystem compatibility.

  • Preflight simulation
  • Atomic rollback
  • Transparent execution cost

Contract SQL

Each contract can have an isolated relational database with deterministic execution rules and familiar indexed queries.

  • Private database per contract
  • Free read-only execution
  • Schema migrations and indexes

Identity and reputation

Readable handles, cluster-linked identities, credentials, reviews, permissions, and cryptographic signatures are available as native building blocks.

  • KYC registrar model
  • One-person uniqueness checks
  • Portable reviews and reputation

Application delivery

Applications can be published into the network and served by its nodes with discovery, custom domains, delegated TLS, events, and push.

  • Frontend and backend together
  • Domain and SNI routing
  • Contract-published updates

Storage with a lifecycle

Object data can use HDD, SSD, or tape classes. Rent keeps abandoned state from growing forever, while funded reserves support permanence.

  • Deterministic rent pricing
  • Validator archival mesh
  • Recoverable historical epochs

Configurable trust boundaries

The same protocol supports open networks, dedicated application clusters, and controlled institutional environments.

  • Owner-gated admission
  • Signed permissioned reads
  • Encrypted epoch data

DEVELOPER SURFACE

Five interfaces. One feature set.

Choose the integration that fits the product. Promotion from development to testnet to mainnet is a configuration change, not a rewrite.

Command lineJavaScript + WASMHTTP RPCBOLT binary protocolNative mobile libraries