01 / PLATFORM MAP

What’s possible on ITZA?

ITZA is a foundation for applications that need identity, shared state, programmable behavior, and durable storage to work together.

◈

Ship a complete ITZApp

Build with HTML, CSS, JavaScript, and WebAssembly. Package the application as a ZIP or TGZ asset and serve it from the network.

APPLICATIONS

▣

Store app-data on-chain

Keep application state close to the contract and make important records part of a verifiable product.

APP DATA

⌂

Give customers their own wallets

Keep customer-owned data in customer wallets, with clear ownership, recovery, and permission boundaries.

CUSTOMER DATA

✦

Store files

Store images, documents, application packages, and other verifiable file assets with predictable rent and ownership.

FILES

▤

Use native SQL

Build familiar data-driven features with SQL-backed contract state, without leaving the application platform.

NATIVE SQL

◎

Simplify login

Give users a friendly network-wide sign-in experience, register a username across the network, and make people easy to find.

⌁

Communicate in real time

Connect users directly with a few lines of code, with end-to-end encryption available when the conversation needs it.

REALTIME

✉

React to events instantly

Deliver contract and application notifications in real time, without building a polling loop.

EVENTS

◇

Add a contract brain

Use WASM contracts for deterministic rules, storage and retrieval, authorization, and application-specific logic.

CONTRACTS

◌

Build decentralized products

Distribute application state and logic across a network designed to keep the product available without one central server.

DECENTRALIZED

↔

Load-balance geographically

Serve hosted applications through geographically distributed RPC nodes, with network redundancy built into the delivery model.

RESILIENCE

Financial building blocks

Move value when your product needs it.

ITZA applications can work with transfers, application and contract wallets, and multiple permitted currencies. Build the financial path into your product instead of bolting it on later.

Transfer funds to someoneBuild a simple person-to-person payment flow.→Fund an app or contractSend value now and let the contract use it later.→Handle currenciesMake the currency, balance, and fee path explicit.→

The application stack

One product. Four connected layers.

Each layer can stand alone. Together, they form an application that is useful, programmable, and accountable.

01ExperienceITZApp web interfaceHTML · CSS · JavaScript

02BehaviorWASM contract logicJSON input · deterministic output

03IdentityWallets and ownershipkeys · signatures · permissions

04StateAssets and storagefiles · objects · rent · SQL