Skip to content
DevUtils Online

Workflow Automation

cli vs prefect

cli leads by 1.2 · narrow

A · leads

cli

96.8

32,362 stars · Apache-2.0

B

prefect

95.6

24,170 stars · Apache-2.0

cli versus prefect is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. cli is written mainly in Rust; prefect is written mainly in Python. The composite score is 96.8 for cli and 95.6 for prefect.

cli has 32,362 GitHub stars to prefect's 24,170, a gap of 8,192 (1.34×). Forks are 1,997 for cli and 2,668 for prefect. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 96 versus 100.

Push history: cli was last pushed on 03 November 2026 (14 days ago), and prefect was last pushed on 17 November 2026 (0 days ago). Open issues stand at 137 for cli (0.004 per star) and 876 for prefect (0.036 per star). Issue-health scores are 96 and 70; activity scores are 92 and 100.

Both cli and prefect are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In Workflow Automation, both cli (32,362 stars) and prefect (24,170 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: cli is open source, prefect is open source.

The lead is split. cli is furthest ahead on issue health (96 to 70), while prefect is furthest ahead on recent activity (100 to 92). Choose the dimension a rollout cannot compromise on.

cli finishes ahead at 96.8 against prefect at 95.6, a 1.2 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.

cli versus prefect metrics
Signal cli prefect
GitHub stars 32,362 24,170
Forks 1,997 2,668
Open issues 137 876
Adoption 100 97
Activity 92 100
Community 96 100
Issue health 96 70
License 96 96
Self-hosting 100 100
Composite 96.8 95.6

cli

Google Workspace CLI — one command-line tool for Drive, Gmail, Calendar, Sheets, Docs, Chat, Admin, and more. Dynamically built from Google Discovery Service. Includes AI agent skills.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, cli or prefect?

cli has more GitHub stars: 32,362 versus 24,170 for prefect. The gap is 8,192 stars.

Which was updated more recently, cli or prefect?

prefect was pushed more recently: 17 November 2026 versus 03 November 2026 for cli. That is 14 days apart.

Can I self-host both cli and prefect?

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

Which license is easier to embed in a commercial product, cli or prefect?

cli 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the cli vs prefect score?

cli scores 96.8 and prefect scores 95.6. This page calls that a narrow lead for cli.

Related comparisons