A stack for the
machine economy.
Six layers. From the device on the street to the fiber under the ocean. Composable end to end.
It starts at the surface.
These are the things doing the work. A scooter that holds its own wallet. A 3D printer that pays for its own filament. A washing machine that takes payments from guests. They look ordinary. They behave like economic peers — they have an identity, they have a balance, they transact.
Every operator gets one screen.
The Virtual Cockpit is what each operator uses to run their part of the machine economy. Marco wants fleet management, peer coordination, revenue splits. Ana wants a job queue, materials tracking, designer payouts. Jorge wants device-level billing and access control. Same infrastructure. Different cockpits. The layer below assembles them.
Cockpits are assembled, not bought.
Dappster is the layer that turns ‘describe what you need’ into ‘here is your application.’ A library of audited modules — chat, video, wallet, machine-to-machine payments, machine identity, hardware control — that snap together. AI picks the modules. You own the deployment. Alvin is the vertical bridge: the orange shafts connecting each machine on the surface to its corresponding modules below. Every Alvin link gives one physical device a persona — identity, wallet, autonomous agency.
Cloud Engines: private subnets, configurable.
Dappster doesn’t run on AWS. It runs on a Cloud Engine — a configurable private subnet on the Internet Computer Protocol. Cloud Engines let you specify the security, performance, and resilience parameters of the subnet your application runs on. Same node hardware as the public network. Same chain-key cryptography. Tunable. Governed on-chain by the Network Nervous System. Node providers earn 80% of engine revenue; the remaining 20% is used to buy and burn ICP tokens — tying network usage directly to token supply.
Engines sit on the Internet Computer.
ICP isn’t a chain that replaces a wallet. It replaces a cloud. Independent data centers, standardized node hardware, subnets formed across geographies, an on-chain DAO that governs upgrades, identity, and economics. Smart contracts on ICP — called canisters — hold both code and state. Users pay no gas. The application funds its own compute. Machines (including AI agents) can hold their own wallets, sign their own transactions, and run continuously without a human in the loop. Cloud Engines are subnets you configure. The rest of ICP is subnets DFINITY and the community already configured.
The old internet is the cables.
Submarine fiber. Terrestrial backhaul. BGP. The protocols that moved packets between continents for the last forty years are still down there. In this stack, they do one job: carry traffic between ICP nodes. The trust layer, the compute layer, the identity layer, the storage layer — those moved up. What’s left is wire.
From machine to cable.
One stack, six layers, one direction of dependency: A scooter holds a wallet. The wallet lives in a canister. The canister runs on a Cloud Engine. The Cloud Engine is a subnet on ICP. ICP runs on nodes in independent data centers. The nodes talk to each other over the same fiber the public internet uses. The whole thing is composable. Swap any module, replace any cockpit, run on a different Cloud Engine, change subnet parameters via NNS proposal. You own the deployment from the surface down to the silicon.