Skip to content
DevUtils Online

DevOps

act vs bytebase

act leads by 20.5 · decisive

A · leads

act

99.1

72,721 stars · MIT

B

bytebase

78.6

14,721 stars · license n/a

act versus bytebase is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. act is written mainly in Go; bytebase is written mainly in TypeScript. The composite score is 99.1 for act and 78.6 for bytebase.

act has 72,721 GitHub stars to bytebase's 14,721, a gap of 58,000 (4.94×). Forks are 2,126 for act and 1,013 for bytebase. On the log scale used inside this pair, adoption is 100 versus 86, and the fork community is 100 versus 90.

Push history: act was last pushed on 16 November 2026 (1 day ago), and bytebase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 318 for act (0.004 per star) and 173 for bytebase (0.012 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.

act 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. bytebase is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for act and 30 for bytebase. This is a procurement signal, not legal advice.

Only act is marked self-hostable here (72,721 stars, deploy score 100). bytebase is not (14,721 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: act is open source, bytebase is unpriced in this catalog.

act is ahead on every scored dimension that is not level. Level dimensions: recent activity. The widest gap is license flexibility at 66 points (96 vs 30), and the tightest is recent activity at 0 points (100 vs 100).

act finishes ahead at 99.1 against bytebase at 78.6, a 20.5 point decisive 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.

act versus bytebase metrics
Signal act bytebase
GitHub stars 72,721 14,721
Forks 2,126 1,013
Open issues 318 173
Adoption 100 86
Activity 100 100
Community 100 90
Issue health 96 84
License 96 30
Self-hosting 100 35
Composite 99.1 78.6

bytebase

Database governance built for humans and agents — controlling changes and access across every major database.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, act or bytebase?

act has more GitHub stars: 72,721 versus 14,721 for bytebase. The gap is 58,000 stars.

Which was updated more recently, act or bytebase?

bytebase was pushed more recently: 17 November 2026 versus 16 November 2026 for act. That is 1 days apart.

Can I self-host both act and bytebase?

Only act is marked self-hostable. bytebase is not.

Which license is easier to embed in a commercial product, act or bytebase?

act 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. bytebase is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the act vs bytebase score?

act scores 99.1 and bytebase scores 78.6. This page calls that a decisive lead for act.

Related comparisons