The public code of the digital state
The OpenStateStack Foundation stewards the open-source building blocks a country needs for its digital transformation — identity, payments, registries, messaging, and more — released as working, zero-knowledge-native code, and connected by a neutral network on which a credential proven in one nation is verified in another. Sovereign by design. Open by default. Held in common.
Open source (OSRUL) · zero-knowledge by design · no kill-switch · no lock-in
The cost of starting from scratch.
spent every year worldwide maintaining fragmented, ageing government IT.
the typical custom national build — hundreds of millions, per nation.
proprietary systems a nation cannot fully audit, control, or exit.
Every nation needs the same handful of digital building blocks. Today each one rebuilds them alone. There is a commons for that.
Three public goods, one Foundation.
The building blocks
Open-source, zero-knowledge-native code for identity, payments, registries, and more.
The network
A neutral settlement and interoperability layer — verified once, trusted across borders.
The treasury
Public-good funding for the audits, research, and contributors that keep the commons alive.
Blueprint, working code, live network.
Open blueprints told the world what a digital state needs. The Foundation ships the working code that builds it — and runs the network that connects the deployments.
- 01
A specification
Read what a digital state needs, block by block, aligned with open standards.
- 02
A public repository
Clone working, audited, zero-knowledge-native code — not slideware.
- 03
A reference deployment
See a nation already running it, in production, under its own control.
Sovereign by design.
Your data never leaves your borders.
Deployments run inside national infrastructure. The Foundation holds no copy and no keys.
No kill-switch, no vendor lock-in.
Open code under an open license, with a sovereign-rollup option. Nothing can be weaponised against you.
Privacy proven with zero-knowledge.
Verify a claim without revealing the data behind it — auditable by design.
Read the repositories. Run a node. Find a funded issue.
Engineer-to-engineer.
Clone the repositories, run a local node in one command, and ship against the building blocks. Then find a funded issue worth your time.
# runs against a local OSS node
npx @openstatestack/cli init my-state
cd my-state && oss node up
oss blocks add identity payments registriesThe proof is in production.
The Foundation names only approved, real deployments and partners. Everything else is omitted, never implied. As deployments clear publication, they appear here and on the deployments page — each linking to verifiable evidence.
// pending approval — reference deployments and partner logos surface in QUESTIONS_FOR_HUMAN.md before publication.
Built in the open, with an AI agent.
This site was designed, written, and shipped by AEGIS — a proprietary AI software-engineering platform from Neurofabric.ai, an OpenStateStack ecosystem company. The Foundation uses AEGIS under a free licence for its public-good projects; the site’s own source is open. AEGIS is a build tool, not one of the open-source building blocks the Foundation stewards.
Read the code. Read the Mandate.
The Foundation’s two highest-trust actions — verifiability over persuasion. The Foundation does not sell.
- 1 The U.S. federal government alone spends more than $100 billion a year on IT, of which agencies report roughly 80% goes to operating and maintaining existing and legacy systems; worldwide government IT spending was forecast at about $590 billion in 2023. A $100B+ annual maintenance burden is conservative at global scale. U.S. GAO, GAO-23-106821; Gartner (2023 forecast)
- 2 Large IT programmes routinely run for years and over budget. A McKinsey–University of Oxford study of large IT projects found they ran on average 45% over budget, 7% over schedule, and delivered 56% less value than predicted; public-sector cost overruns run far higher than private-sector ones, and most large public projects overran their schedules. McKinsey, public-sector IT projects
- 3 A European Commission study on building open ICT systems (“Against lock-in”) found that at least 40% of public procurers perceived vendor lock-in — typically from a lack of interoperability or data portability — and estimated EU public bodies waste about €1.1 billion a year for want of supplier competition. European Commission, COM(2013) 455