head to head · open source

donutbrowser vs puppetry

donutbrowser has 4,213 GitHub stars, 439 forks, 28 open issues and last shipped yesterday. puppetry has 888 stars, 127 forks, 25 open issues and last shipped 5 months ago. donutbrowser leads on adoption by 374% (4,213 vs 888 stars). donutbrowser is written in Rust under AGPL-3.0; puppetry is written in JavaScript under MIT. donutbrowser has attracted 10% as many forks as stars, puppetry 14%. donutbrowser was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (browser-automation), 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.

donutbrowser ★ 4.2K puppetry ★ 888 category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

donutbrowser puppetry
GitHub stars ★ 4.2K ★ 888
License AGPL-3.0 MIT
Written in Rust JavaScript
Last push 2026-11-04 2026-06-19
Forks ⑂ 439 ⑂ 127
Self-hosting Yes Yes
Data ownership Your server Your server

pick donutbrowser if

  • You weight community size — 4.2K stars and counting
  • You want the AGPL-3.0 license terms
  • Your stack matches Rust
  • You value the larger contributor base for long-term maintenance

full donutbrowser profile →

pick puppetry if

  • You want the puppetry feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches JavaScript
  • You evaluated both and puppetry fits your workflow better

full puppetry profile →

About donutbrowser

Donut Browser Open Source Anti Detect Browser donutbrowser.com Features Unlimited browser profiles: each fully isolated with its own fingerprint, cookies, extensions, and data Anti detect Chromium engine: powered by Wayfern, a privacy focused Chromium fork whose fingerprint spoofing is not detected by Cloudflare, reCaptcha v3, or other browser fingerprinting and anti bot services DNS AdBlocker: block ads, trackers, and other unwanted content with per profile DNS blocking Proxy support: HTTP, HTTPS, SOCKS4, SOCKS5 per profile, with dynamic proxy URLs VPN support: WireGuard configs per profile Local API & MCP…

read the full donutbrowser overview →

About puppetry

Puppetry ⚠️ Project Deprecated After observing the market for many years since the last update, I’ve decided to officially deprecate Puppetry . Over time, it became clear that Playwright has evolved to cover almost everything I originally aimed to achieve with this project — and they do it much better. The idea of codeless end to end testing , while exciting at the time, has proven to be a technological dead end. Today, with the rise of AI assisted development , it’s possible to create robust end to end tests simply by narrating what you want to achieve — something that goes far beyond the original Puppetry…

read the full puppetry overview →

More in Infrastructure & Operations

Related comparisons

More Orchestration & Scheduling projects

Compare either of these against the rest of the Orchestration & Scheduling field.

Frequently asked questions

Is donutbrowser or puppetry more popular?

donutbrowser has 4,213 GitHub stars and puppetry has 888. donutbrowser has the larger community by that measure.

Are donutbrowser and puppetry free?

Both are open source. donutbrowser is licensed under AGPL-3.0 and puppetry under MIT. Neither carries a licence fee.

What is the difference between donutbrowser and puppetry?

donutbrowser is written in Rust and puppetry in JavaScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, donutbrowser or puppetry?

Choose donutbrowser if you want the larger community (4,213 stars) or its AGPL-3.0 licence terms. Choose puppetry if its feature set, stack or MIT licence fits better. Both are self-hostable.