A · leads
ego-lite
97.0
23,377 stars · MIT
Workflow Automation
ego-lite leads by 4.4 · narrow
A · leads
97.0
23,377 stars · MIT
B
92.6
23,434 stars · AGPL-3.0
ego-lite versus skyvern is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. ego-lite is written mainly in JavaScript; skyvern is written mainly in Python. The composite score is 97.0 for ego-lite and 92.6 for skyvern.
skyvern has 23,434 GitHub stars to ego-lite's 23,377, a gap of 57 (1.00×). Forks are 1,324 for ego-lite and 2,246 for skyvern. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 93 versus 100.
Push history: ego-lite was last pushed on 17 November 2026 (0 days ago), and skyvern was last pushed on 17 November 2026 (0 days ago). Open issues stand at 291 for ego-lite (0.012 per star) and 301 for skyvern (0.013 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
ego-lite is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for ego-lite and 52 for skyvern. This is a procurement signal, not legal advice.
In Workflow Automation, both ego-lite (23,377 stars) and skyvern (23,434 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: ego-lite is open source, skyvern is open source.
The lead is split. ego-lite is furthest ahead on license flexibility (96 to 52), while skyvern is furthest ahead on fork community (100 to 93). Choose the dimension a rollout cannot compromise on.
ego-lite finishes ahead at 97.0 against skyvern at 92.6, a 4.4 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | ego-lite | skyvern |
|---|---|---|
| GitHub stars | 23,377 | 23,434 |
| Forks | 1,324 | 2,246 |
| Open issues | 291 | 301 |
| Adoption | 100 | 100 |
| Activity | 100 | 100 |
| Community | 93 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 97.0 | 92.6 |
The fastest browser for AI agents to run browser automation, built for sharing your logged-in browser state with your AI agents, like Codex or Claude Code, without disturbing you. Zero cost, zero config.
Automate browser based workflows with AI
skyvern has more GitHub stars: 23,434 versus 23,377 for ego-lite. The gap is 57 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both ego-lite and skyvern as self-hostable. Confirm each project's deploy docs before you plan a migration.
ego-lite is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
ego-lite scores 97.0 and skyvern scores 92.6. This page calls that a narrow lead for ego-lite.