A · leads
prefect
96.5
24,170 stars · Apache-2.0
Workflow Automation
prefect leads by 4.3 · narrow
A · leads
96.5
24,170 stars · Apache-2.0
B
92.2
23,434 stars · AGPL-3.0
prefect versus skyvern is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Python. The composite score is 96.5 for prefect and 92.2 for skyvern.
prefect has 24,170 GitHub stars to skyvern's 23,434, a gap of 736 (1.03×). Forks are 2,668 for prefect 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 98.
Push history: prefect 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 876 for prefect (0.036 per star) and 301 for skyvern (0.013 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
prefect 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 prefect and 52 for skyvern. This is a procurement signal, not legal advice.
In Workflow Automation, both prefect (24,170 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: prefect is open source, skyvern is open source.
The lead is split. prefect is furthest ahead on license flexibility (96 to 52), while skyvern is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
prefect finishes ahead at 96.5 against skyvern at 92.2, a 4.3 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 | prefect | skyvern |
|---|---|---|
| GitHub stars | 24,170 | 23,434 |
| Forks | 2,668 | 2,246 |
| Open issues | 876 | 301 |
| Adoption | 100 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 98 |
| Issue health | 70 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 92.2 |
Prefect is a workflow orchestration framework for building resilient data pipelines in Python.
Automate browser based workflows with AI
prefect has more GitHub stars: 24,170 versus 23,434 for skyvern. The gap is 736 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both prefect and skyvern as self-hostable. Confirm each project's deploy docs before you plan a migration.
prefect 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.
prefect scores 96.5 and skyvern scores 92.2. This page calls that a narrow lead for prefect.