Frameworks & reference architectures
Frameworks for modular, upgradeable on-chain systems.
Our frameworks are open-source, documented, and built to be inspected, forked, and extended. They share a common philosophy: architecture before application.
The model
A stable core, evolving modules.
Each framework keeps a small, stable kernel at the center. The kernel does only a few things — routing, installation, upgrades, and lifecycle — and does them predictably.
Everything that changes lives in modules. A module declares its identity, version, storage namespace, and the exact functions it exposes, so it can be installed, upgraded, and removed without redeploying the system or risking storage collisions.
What every framework provides
A secure, upgradeable foundation.
Kernel-orchestrated architecture
A small, stable core governs routing, installation, and lifecycle while the system around it evolves.
Installable & upgradeable modules
Functionality ships as modules that can be installed, upgraded, and removed without redeploying the system.
Namespaced storage isolation
Each module owns an isolated, collision-free storage namespace — no layout clashes across upgrades.
Explicit interface surfaces
Modules declare the exact callable surface they expose. Nothing is reachable by accident.
Lifecycle hooks
First-class hooks for boot, upgrade, and removal make state transitions explicit and auditable.
Built for system evolution
Designed for long-lived systems that must change safely over years, not single-shot deployments.