A browser,
managed.
Starling is a web browser engine with no Chromium, no Gecko, no WebKit underneath — a managed-first engine, written from the ground up in .NET. Parser, layout, paint, and a JavaScript runtime, all its own.
Real sites. No borrowed engine.
This is Starling drawing a live site — parser, cascade, layout, and paint pipeline, end to end. Every box and glyph on screen is computed by code written for Starling, running on .NET.
render preview · add assets/render.png
Honest numbers, backed by tests.
Starling is experimental. Each figure is measured by a real test suite — Test262, Web Platform Tests, and Starling's own specs. Nothing rounded up.
A managed-first browser is a bet — that the engine no longer needs C++.
Ladybird proved an independent engine is viable. Arc and Dia ship in Swift. Starling pushes the idea further: a browser engine written in a managed language, in the open, beholden to no vendor.
No borrowed engine
HTML parsing, the DOM, the CSS cascade, layout, paint, and a JavaScript runtime — all written for Starling. Nothing forked from Blink or WebKit.
Managed by design
Built on .NET, multi-process by architecture. The bet is that memory safety and tooling can come from the platform, not from years of hardening.
WASM as a first-class citizen
The long game: earn parity on real sites, then let WebAssembly reach the DOM directly — not as a guest behind a JavaScript bridge.
Read the code. Run the engine. Watch it earn the web.
Experimental software · built in the open · not yet hardened for daily use
