CityOS runs on KELLER-OS kernel primitives and coordinates microgrid power, emergency corridors, anonymous service access and public records — without a hyperscaler in the path.
A cloud smart city is a hyperscaler data centre with sensors attached. Sever the fibre and the traffic signals, the utility meters and the emergency routing go with it — and every transaction in the system is also a record of where a named citizen was.
CityOS inverts both properties. Resource routing is peer to peer across the mesh, so a district that loses its uplink keeps operating as an island and re-merges its ledger afterwards. And identity is never required to use a public service: turnstiles, libraries and sports facilities accept zero-knowledge blinding tokens, which prove entitlement without leaving a persistent identifier behind.
[KELLER-KERNEL] Hardware enclave microkernel initialised. [CIVIC-ROUTING] District 4 solar surplus diverted to District 7 storage. [EMERGENCY] EV ambulance prioritised via cryptographic optical corridor. [PRIVACY] Identity-less access tokens issued for public transit turnstiles.
| Dimension | Cloud smart city | CityOS |
|---|---|---|
| backbone dependency | centralised hyperscaler data centres | fully peer-to-peer mesh and edge relays |
| blackout survivability | immediate failure when fibre is severed | autonomous local islanding, DAG re-merge |
| citizen surveillance | persistent facial and payment tracking | zero-knowledge verifiable credentials |
| emergency latency | 300 ms+ round trip via a cloud API | ≤ 15 ms via hardware enclave routing |
git clone https://github.com/KELLERBABG/CityOS.git cd CityOS && cargo test # kernel primitives and mesh routing