head to head · open source
page-agent vs workflow-use
page-agent has 29,646 GitHub stars, 2,641 forks, 94 open issues and last shipped 4 days ago. workflow-use has 4,247 stars, 356 forks, 61 open issues and last shipped 2 days ago. page-agent leads on adoption by 598% (29,646 vs 4,247 stars). page-agent is written in TypeScript under MIT; workflow-use is written in Python under AGPL-3.0. page-agent has attracted 9% as many forks as stars, workflow-use 8%. workflow-use 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.
← all 20902 open source comparisons
Side by side
| page-agent | workflow-use | |
|---|---|---|
| GitHub stars | ★ 30K | ★ 4.2K |
| License | MIT | AGPL-3.0 |
| Written in | TypeScript | Python |
| Last push | 2026-11-04 | 2026-11-06 |
| Forks | ⑂ 2.6K | ⑂ 356 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick page-agent if
- You weight community size — 30K stars and counting
- You want the MIT license terms
- Your stack matches TypeScript
- You value the larger contributor base for long-term maintenance
pick workflow-use if
- You want the workflow-use feature set and don't need the biggest community
- You prefer the AGPL-3.0 license terms
- Your stack matches Python
- You evaluated both and workflow-use fits your workflow better
About page-agent
Page Agent The GUI Agent Living in Your Webpage. One script gives any web page its own AI agent. 🌐 English 中文 🚀 Demo 📖 Docs 📢 HN Discussion 𝕏 Follow on X ✨ Features 🎯 Easy integration No need for browser extension / python / headless browser . Just in page javascript. Everything happens in your web page. 📖 Text based DOM manipulation No screenshots. No multi modal LLMs or special permissions needed. 🧠 Bring your own LLMs Works with most mainstream models, including locally deployed ones. See supported models. 🐙 Optional chrome extension for multi page tasks. And an MCP Server (Beta) to control it from…
read the full page-agent overview →
About workflow-use
Deterministic, Self Healing Workflows (RPA 2.0) ⚙️ Workflow Use is the easiest way to create and execute deterministic workflows with variables which fallback to Browser Use if a step fails. You just show the recorder the workflow, we automatically generate the workflow. ❗ This project is in very early development so we don't recommend using this in production. Lots of things will change and we don't have a release schedule yet. Originally, the project was born out of customer demand to make Browser Use more reliable and deterministic. 🚀 NEW: Generation Mode Automatically generate workflows from natural…
read the full workflow-use overview →
More in Data & Analytics
Related comparisons
More Data Extraction & Web Scraping projects
Compare either of these against the rest of the Data Extraction & Web Scraping field.
Frequently asked questions
Is page-agent or workflow-use more popular?
page-agent has 29,646 GitHub stars and workflow-use has 4,247. page-agent has the larger community by that measure.
Are page-agent and workflow-use free?
Both are open source. page-agent is licensed under MIT and workflow-use under AGPL-3.0. Neither carries a licence fee.
What is the difference between page-agent and workflow-use?
page-agent is written in TypeScript and workflow-use in Python. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, page-agent or workflow-use?
Choose page-agent if you want the larger community (29,646 stars) or its MIT licence terms. Choose workflow-use if its feature set, stack or AGPL-3.0 licence fits better. Both are self-hostable.