Projects building on top of Blitz

A non-exhaustive list of projects building on top of Blitz (first-party ones from this repo included for comparison):

### Browsers

| Project | What it does | JS engine |
|---|---|---|
| [Blitz Browser](https://github.com/DioxusLabs/blitz/tree/main/apps/browser) | Blitz's own in-repo multi-platform browser app (URL bar, navigation, tabs). Mostly no-JS | None by default (experimental Boa via `blitz-vibey-script`) |
| [formal-web](https://github.com/gterzian/formal-web) | Modular Rust web-engine prototype with formal verification; Blitz for DOM/CSS/layout/paint | V8 (default), Boa or JavaScriptCore |
| [aurora](https://github.com/johannaweb/aurora) | Experimental browser-engine prototype aimed at agent-controlled browsing; Blitz for DOM/CSS/layout/paint | V8 |
| [Kitesurf](https://blog.cloudflare.com/kitesurf/) | Cloudflare's agent-first headless browser running in Workers; Blitz + Stylo for HTML/CSS parsing, blitz-paint for rendering | V8 isolates (Workers), Boa for `eval` |
| [oxibrowser](https://github.com/project-oxi/oxibrowser) | Pure-Rust headless browser for AI agents / scraping, CDP-compatible | Boa |
| [AginxBrowser](https://github.com/yinnho/aginxbrowser) | Single-binary headless browser for AI agents (HTTP API + MCP + CDP): markdown extraction, search, sessions; Blitz used for screenshot rendering | V8 |

### JS bindings / app runtimes

| Project | What it does | JS engine | JS framework / DOM |
|---|---|---|---|
| [blitz-vibey-script](https://github.com/DioxusLabs/blitz/tree/main/packages/blitz-vibey-script) | Blitz's own in-repo JavaScript layer: runs page scripts against the Blitz DOM | Boa | Implements DOM APIs |
| [kiln](https://github.com/marshallshelly/kiln) | Native desktop apps from built HTML/CSS/TS (Electron/Tauri alternative) with CLI, packaging, CDP DevTools, menus, accessibility | QuickJS-ng (via rquickjs) | Implements DOM APIs (runs unmodified React/Preact builds) |
| [blitsen](https://github.com/krazyjakee/blitsen) | Run built HTML/CSS/JS apps in a native window and ship as a single executable; npm CLI | QuickJS | Implements DOM APIs (web-platform subset) |
| [napi-blitz](https://github.com/jerry4718/napi-blitz) | Node.js N-API binding exposing a browser-like DOM API to render HTML/CSS in native windows | Host runtime (Node/Bun/Deno) | Implements DOM APIs |
| [blitz-quick](https://github.com/SunDoge/blitz-quick) | Experimental DOM-less native UI runtime: JS drives Blitz via a binary opcode FFI protocol | QuickJS | SolidJS (custom `solid-js/universal` renderer) |
| [naivi](https://github.com/WaiSiuKei/naivi) | Vue Vapor AOT runtime on Blitz: same SFCs run on Web DOM, Wasm (Blitz in-browser) and native desktop via a mutation-ops bridge | QuickJS (native), browser JS (wasm) | Vue Vapor |

### Rust GUI framework integrations

| Project | GUI framework | What it does |
|---|---|---|
| [iced_webview_v2](https://github.com/franzos/iced_webview_v2) | [iced](https://iced.rs) | Embeddable webview widget, with Blitz as one of several pluggable engines (alongside litehtml, Servo, CEF) |
| [freya-html](https://github.com/marc2332/freya/pull/2157) | [Freya](https://github.com/marc2332/freya) | HTML/CSS rendering component; Blitz paints directly onto Freya's Skia canvas, replacing the WRY-based `freya-webview` |

### Renderers (HTML → image / PDF)

| Project | What it does | Language / bindings |
|---|---|---|
| [hyper-render](https://github.com/thomasmost/hyper-render) | Library to render HTML to PNG or PDF without Chromium | Rust |
| [fulgur](https://github.com/fulgur-rs/fulgur) | HTML/CSS → PDF engine (wkhtmltopdf alternative) with paged-media support, built on Blitz + krilla | Rust lib + CLI; Node (npm), Python, Ruby and Wasm bindings |
| [og-img](https://github.com/vrypan/og-img) | CLI for generating OpenGraph social-card PNGs from flags or markdown frontmatter | Rust (CLI) |
| [himg](https://github.com/Jamedjo/himg) | HTML → PNG for dynamic OpenGraph images, incl. Rails `.himg.erb` templates | Ruby gem (+ CLI) |

Feel free to share yours in the comments.

No repository file, test, or entry point is named. Clarify where this project list should be maintained and what addition or update is expected before starting.

Written by the indexing model from the issue text.