Blocklet Technology
Identity-bound, capability-scoped deployable units. Not plugins. Not containers. The composable building blocks of ArcBlock's decentralized infrastructure.
What a Blocklet Is
A Blocklet is not a plugin you install into a host application. It is not a Docker container you orchestrate with Kubernetes. A Blocklet is an identity-bound, capability-scoped deployable unit — a self-contained component that has its own DID identity, declares its capabilities explicitly, runs within a clear boundary, and can be composed with other Blocklets or replaced independently.
In AI-Native Engineering (AINE) terms, a Blocklet is a Chamber — the isolated runtime boundary for a computational actor. This is not a retroactive mapping; Blocklet Technology was the early implementation that informed the AINE framework. Blocklet Server is the Web Scaffold — the first real-world Chamber Runtime.
Two principles define Blocklet Technology: "Everything is Blocklet" and "Everything can Self-Host."
Core Properties
DID Identity
Every Blocklet has its own DID — a persistent, verifiable identity that is a blockchain account. This identity is not assigned by a registry; it is cryptographically generated. The Blocklet can sign, authenticate, and be held accountable. Its identity persists across deployments, updates, and migrations.
Clear Runtime Boundary
A Blocklet runs within a well-defined boundary. It has its own process space, data directory, network interface, and lifecycle. The boundary is enforced by Blocklet Server, not by convention. This is what makes Blocklets safely composable — they cannot interfere with each other because the runtime guarantees isolation.
Capability Declaration
A Blocklet explicitly declares what it can do and what it needs. These declarations are not documentation — they are machine-readable contracts that the runtime enforces. A Blocklet that declares it needs database access gets database access. One that does not declare it, does not get it. Capabilities are scoped, auditable, and revocable.
Composable and Replaceable
Blocklets compose through well-defined interfaces, not through shared state or tight coupling. You can swap one Blocklet for another that implements the same interface. You can nest Blocklets. You can route between them. This composability is what enables "Everything is Blocklet" — the entire server-side stack is built from Blocklets.
Two Defining Principles
Everything is Blocklet
All server-side components are Blocklets. The web server is a Blocklet. The database adapter is a Blocklet. The authentication service is a Blocklet. The AI agent runtime is a Blocklet. There is no distinction between "core" and "extension" — everything is a composable, replaceable, identity-bound unit. This eliminates the traditional platform/plugin split and its associated fragility.
Everything can Self-Host
Every Blocklet can be deployed independently. There is no mandatory cloud service, no required SaaS dependency, no vendor lock-in at the infrastructure level. You can run your entire stack on your own hardware, in your own datacenter, on a Raspberry Pi. Fully decentralized deployment is not a feature — it is an architectural guarantee. Self-hosting is a first-class deployment target, not an afterthought.
Related Products
Blocklet Server
The runtime for Blocklets. Manages lifecycle, enforces boundaries, handles identity, and provides the infrastructure for composition. The Web Scaffold — the first Chamber Runtime implementation.
Learn more →AIGNE Framework
AIGNE agents deploy as Blocklets. The framework uses Blocklet Technology for isolation, identity, and lifecycle management of AI actors in production.
Learn more →Related Articles
From Blocklet to Chamber
The evolution from Blocklet Technology to the Chamber concept in AI-Native Engineering. How practical experience building Blocklets informed the AINE framework.
AnnouncementIntroducing AIGNE Framework
AIGNE deploys AI agents as Blocklets, bringing AI-native capabilities to the proven Blocklet runtime infrastructure.
Build with Blocklets
Deploy your first Blocklet, explore the composition model, and experience truly decentralized infrastructure.