Skip to content
DevUtils Online

Workflow Automation

sim vs skyvern

sim leads by 7.0 · clear

A · leads

sim

97.9

30,151 stars · Apache-2.0

B

skyvern

90.9

23,434 stars · AGPL-3.0

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

sim has 30,151 GitHub stars to skyvern's 23,434, a gap of 6,717 (1.29×). Forks are 3,915 for sim and 2,246 for skyvern. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 100 versus 93.

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

sim is listed as Apache-2.0, 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 sim and 52 for skyvern. This is a procurement signal, not legal advice.

In Workflow Automation, both sim (30,151 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: sim is open source, skyvern is open source.

sim 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).

sim finishes ahead at 97.9 against skyvern at 90.9, a 7.0 point clear 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.

sim versus skyvern metrics
Signal sim skyvern
GitHub stars 30,151 23,434
Forks 3,915 2,246
Open issues 330 301
Adoption 100 98
Activity 100 100
Community 100 93
Issue health 84 84
License 96 52
Self-hosting 100 100
Composite 97.9 90.9

sim

Sim is the collaborative workspace to build, deploy, and monitor AI agents and workflows. Used by 100,000+ builders.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, sim or skyvern?

sim has more GitHub stars: 30,151 versus 23,434 for skyvern. The gap is 6,717 stars.

Which was updated more recently, sim or skyvern?

Both were last pushed on 17 November 2026.

Can I self-host both sim and skyvern?

Yes. This catalog marks both sim 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, sim or skyvern?

sim is listed as Apache-2.0, 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 sim vs skyvern score?

sim scores 97.9 and skyvern scores 90.9. This page calls that a clear lead for sim.

Related comparisons