head to head · open source
slate vs BrowserOS
slate has 31,746 GitHub stars, 3,306 forks, 653 open issues and last shipped 8 days ago. BrowserOS has 14,245 stars, 1,531 forks, 82 open issues and last shipped yesterday. slate leads on adoption by 123% (31,746 vs 14,245 stars). slate is written in TypeScript under MIT; BrowserOS is written in TypeScript under AGPL-3.0. slate has attracted 10% as many forks as stars, BrowserOS 11%. BrowserOS was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (browser), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| slate | BrowserOS | |
|---|---|---|
| GitHub stars | ★ 32K | ★ 14K |
| License | MIT | AGPL-3.0 |
| Written in | TypeScript | TypeScript |
| Last push | 2026-10-28 | 2026-11-04 |
| Forks | ⑂ 3.3K | ⑂ 1.5K |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick slate if
- You weight community size — 32K stars and counting
- You want the MIT license terms
- Your stack matches TypeScript
- You value the larger contributor base for long-term maintenance
pick BrowserOS if
- You want the BrowserOS feature set and don't need the biggest community
- You prefer the AGPL-3.0 license terms
- Your stack matches TypeScript
- You evaluated both and BrowserOS fits your workflow better
About slate
A completely customizable framework for building rich text editors. Why? · Principles · Demo · Examples · Documentation · Contributing! Slate lets you build rich, intuitive editors like those in Medium, Dropbox Paper or Google Docs—which are becoming table stakes for applications on the web—without your codebase getting mired in complexity. It can do this because all of its logic is implemented with a series of plugins, so you aren't ever constrained by what is or isn't in "core". You can think of it like a pluggable implementation of contenteditable built on top of React. It was inspired by libraries like…
read the full slate overview →
About BrowserOS
Website · Docs · Enterprise Free · Open source · Everything runs on your machine A second browser, just for your AI agents. Import your logins from Chrome in one click, connect Claude Code, Codex, or any MCP agent, and hand off your web tasks. Agents run in parallel in their own tabs. You watch live, or replay any session like a video. BrowserOS neo is not a Chrome replacement. It is a secondary browser that sits next to Chrome, made friendly to agents. Get started 1. Install BrowserOS neo Prefer a direct download? Grab it for macOS or Windows. 2. Import from Chrome One click brings over your logins, bookmarks…
read the full BrowserOS overview →
More in Productivity & Utilities
Related comparisons
More Browsers & Extensions projects
Compare either of these against the rest of the Browsers & Extensions field.
Frequently asked questions
Is slate or BrowserOS more popular?
slate has 31,746 GitHub stars and BrowserOS has 14,245. slate has the larger community by that measure.
Are slate and BrowserOS free?
Both are open source. slate is licensed under MIT and BrowserOS under AGPL-3.0. Neither carries a licence fee.
What is the difference between slate and BrowserOS?
slate is written in TypeScript and BrowserOS in TypeScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, slate or BrowserOS?
Choose slate if you want the larger community (31,746 stars) or its MIT licence terms. Choose BrowserOS if its feature set, stack or AGPL-3.0 licence fits better. Both are self-hostable.