An Internet-Native Runtime
A first-class application host where the network is a runtime primitive — one language, capability-based security, direct GPU rendering. The web, rebuilt from first principles.
Who we want to build it with
Systems researchers, runtime engineers, and foundations interested in open web infrastructure
Logged 20 July 2026
The browser has become an operating system running inside another operating system — duplicating process management, memory management, networking, and rendering, while applications pay the tax in performance, battery life, and security surface.
The Internet-Native Runtime is our long-horizon research thesis: a first-class application host where applications live on the network, execute locally with declared hardware capabilities, and render directly through the OS compositor. One unified language replacing the HTML/CSS/JS stack. Capability manifests instead of sandbox workarounds — making entire vulnerability classes (XSS, CSRF, supply-chain script attacks) architecturally impossible rather than merely mitigated.
Why this matters
- A single codebase that ships everywhere with native-level performance — no Electron, no per-platform teams.
- 30–60% less CPU energy consumption compared to equivalent web apps.
- A package ecosystem where every dependency’s capabilities are declared and auditable before install.
Where we are
This is an idea we are actively thinking and writing about — mapping the architecture, the security model, and the governance structure such a project would need. It is far bigger than any one company, which is exactly the point: it would need to live as an open, foundation-governed effort.
If you work on runtimes, languages, compilers, capability security, or open internet infrastructure — or you fund people who do — we would love to compare notes.