Skip to content
DevUtils Online

DevOps

bytebase vs floci

floci leads by 17.7 · decisive

A

bytebase

80.2

14,721 stars · license n/a

B · leads

floci

97.9

31,872 stars · MIT

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

floci has 31,872 GitHub stars to bytebase's 14,721, a gap of 17,151 (2.17×). Forks are 1,013 for bytebase and 3,521 for floci. On the log scale used inside this pair, adoption is 93 versus 100, and the fork community is 85 versus 100.

Push history: bytebase was last pushed on 17 November 2026 (0 days ago), and floci was last pushed on 17 November 2026 (0 days ago). Open issues stand at 173 for bytebase (0.012 per star) and 215 for floci (0.007 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.

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. floci 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. License scores in this pair are 30 for bytebase and 96 for floci. This is a procurement signal, not legal advice.

Only floci is marked self-hostable here (31,872 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: bytebase is unpriced in this catalog, floci is open source.

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

floci finishes ahead at 97.9 against bytebase at 80.2, a 17.7 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.

bytebase versus floci metrics
Signal bytebase floci
GitHub stars 14,721 31,872
Forks 1,013 3,521
Open issues 173 215
Adoption 93 100
Activity 100 100
Community 85 100
Issue health 84 84
License 30 96
Self-hosting 35 100
Composite 80.2 97.9

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, bytebase or floci?

floci has more GitHub stars: 31,872 versus 14,721 for bytebase. The gap is 17,151 stars.

Which was updated more recently, bytebase or floci?

Both were last pushed on 17 November 2026.

Can I self-host both bytebase and floci?

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

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

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

Who wins the bytebase vs floci score?

floci scores 97.9 and bytebase scores 80.2. This page calls that a decisive lead for floci.

Related comparisons