Browser and Office Infrastructure in Intermediate Language with Enhanced Reliability
Broiler is an open-source software platform exploring a deliberately ambitious question:
Can modern browser and office applications be built entirely in managed .NET?
No Chromium. No embedded WebView. No native browser engine. Just managed .NET, modular architecture, open standards, automated verification, AI-assisted engineering, and human review.
Broiler is not a wrapper around an existing browser or office stack. It is a reusable platform for building browsers, office applications, document software, and future web-enabled tools on top of a shared managed runtime — built around a simple idea:
Important application infrastructure should remain understandable, inspectable, portable, and replaceable.
Note
Broiler is under active development and is not yet intended for production use.
| Component | Status |
|---|---|
| Standards verification | Test262, WPT and reftest tooling; current figures require revision-linked evidence (status) |
| Supported Platforms | Windows, Linux, Android, WebAssembly |
| Applications | Browser, Writer, Code, Plate, Mail, Cells |
| Reference Deployment | BOSS |
| Document Formats | RTF, HTML, Markdown, DOCX, ODT, CSV, PDF (preview subset) |
| Native Compilation | Writer (win-x64, linux-x64) and Plate (win-x64) publish paths; Mail (win-x64, win-arm64) validation packaging uses NativeAOT |
| Repository Layout | 27 component submodules — 6 applications, shared libraries and projects under development (Component Map) |
The aggregate checkout pins component repositories as Git submodules and owns integration tooling, tests and BOSS. Components consume one another through NuGet packages, with project references within each repository. The generated map contains 27 components and 74 declared dependency edges, including optional and conditional paths, as of 23 October 2026.
flowchart TD
Apps[Browser / Writer / Code / Plate / Mail / Cells] --> Hosting[Hosting and UI]
Apps --> Web[HtmlBridge / HTML / CSS / DOM / Layout]
Hosting --> Documents[Documents and pagination]
Web --> Engines[JSEAL providers: Broiler.JS and Broiler.VM]
Hosting --> Devices[Graphics / Input / Media / Native]
Documents --> Devices
This is a conceptual overview; direct references, scan scope and source evidence are in the component map. Broiler.VM and Fond have implementation work but retain acceptance gates.
The full wiring — who depends on whom, in both directions — is in the Component Map.
| Application | What it is | Heads |
|---|---|---|
| Broiler Browser | Reference browser — the full web stack end to end | Windows, Linux, Android |
| Broiler Writer | Word processor and reference office application | Windows, Linux, Android, WebAssembly |
| Broiler Code | Code editor with C# language services and a human-review workspace | Windows, Linux |
| Broiler Plate | Read-only viewer — the smallest honest demonstration of what the platform can already read | Windows |
| Broiler Mail | Mail client — Single-account reader with SMTP composition and HTML preview work; provider acceptance and renderer isolation remain open | Windows, Android; Linux placeholder |
| Broiler Cells | Minimal spreadsheet — 100 × 100 grid with A1-style addresses, in-place editing, row/column selection and resizing, CSV open/save | Windows |
| BOSS | Broiler Office Standalone Server — hosts the WebAssembly Writer via ASP.NET Core | self-hosted |
The "Enhanced Reliability" part of the name reflects the project's engineering philosophy.
Managed .NET
+ Modular Architecture
+ Open Standards
+ AI-Assisted Engineering
+ Human Review
+ Automated Verification
--------------------------------------------------
= Enhanced Reliability
AI can generate code rapidly. Reliable browser and office infrastructure requires considerably more. Broiler therefore combines AI-assisted development with modular design, standards compliance, automated verification, and human review.
Each part of that formula is described in Engineering Principles.
| Document | Contents |
|---|---|
| Status and Roadmap | What works today, what is in progress, what comes next |
| Architecture and Deployment | Platform layers, desktop/mobile/web, self-hosting, open infrastructure |
| Component Map | Every component, what it owns, and what it depends on — in both directions |
| Engineering Principles | Managed .NET, standards first, security, modularity, AI + human review |
| Why Broiler | Why the platform exists, why .NET, why another browser and office |
| Project Story | How Broiler started, and acknowledgements |
| Native Compilation | NativeAOT: self-contained native binaries, and what that constrains |
| Current Preview | Screenshots of the browser, the writer, and standards tests |
Each application releases on its own schedule, from its own repository:
| Application | Latest preview | Builds |
|---|---|---|
| Broiler Browser | Releases | win-x64 and linux-x64, each self-contained or framework-dependent · Android .apk / .aab |
| Broiler Writer | Releases | win-x64 and linux-x64, self-contained (NativeAOT) or framework-dependent · Android .apk / .aab |
| Broiler Plate | Releases | win-x64 (NativeAOT) |
| Broiler Code | build from source | no release yet |
| Broiler Cells | build from source | no release yet |
| Broiler Mail | Source and workflows | Windows x64/ARM64 and Android validation packaging; unsigned builds and draft releases |
Then:
- Run the Writer through BOSS
- Build on the platform directly — components publish as NuGet preview packages
- Read the source — each application and each component is its own repository; the Component Map is the index
- Report bugs and compatibility problems on the repository they belong to
Note
The combined development snapshots are discontinued. The last one was the Final Broiler Preview Package of August 2026; everything since then ships per application, from that application's own repository.
Feedback and contributions are always appreciated.
Contributions of all kinds are welcome — code, documentation, testing, ideas, interoperability reports, or security analysis.
Please read CONTRIBUTING.md, CODE_OF_CONDUCT.md and SECURITY.md before opening a pull request.
Broiler is licensed under the Apache License 2.0.
