Skip to content
DevUtils Online

Workflow Automation

Archon vs skyvern

Archon leads by 6.1 · narrow

A · leads

Archon

97.9

23,938 stars · MIT

B

skyvern

91.8

23,434 stars · AGPL-3.0

Archon versus skyvern is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Archon is written mainly in TypeScript; skyvern is written mainly in Python. The composite score is 97.9 for Archon and 91.8 for skyvern.

Archon has 23,938 GitHub stars to skyvern's 23,434, a gap of 504 (1.02×). Forks are 3,536 for Archon and 2,246 for skyvern. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 94.

Push history: Archon 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 214 for Archon (0.009 per star) and 301 for skyvern (0.013 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.

Archon 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 Archon and 52 for skyvern. This is a procurement signal, not legal advice.

In Workflow Automation, both Archon (23,938 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: Archon is open source, skyvern is open source.

Archon is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, self-hosting. The widest gap is license flexibility at 44 points (96 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).

Archon finishes ahead at 97.9 against skyvern at 91.8, a 6.1 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

Archon versus skyvern metrics
Signal Archon skyvern
GitHub stars 23,938 23,434
Forks 3,536 2,246
Open issues 214 301
Adoption 100 100
Activity 100 100
Community 100 94
Issue health 84 84
License 96 52
Self-hosting 100 100
Composite 97.9 91.8

Questions this page answers

Which has more GitHub stars, Archon or skyvern?

Archon has more GitHub stars: 23,938 versus 23,434 for skyvern. The gap is 504 stars.

Which was updated more recently, Archon or skyvern?

Both were last pushed on 17 November 2026.

Can I self-host both Archon and skyvern?

Yes. This catalog marks both Archon and skyvern as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, Archon or skyvern?

Archon 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.

Who wins the Archon vs skyvern score?

Archon scores 97.9 and skyvern scores 91.8. This page calls that a narrow lead for Archon.

Related comparisons