A
dokploy
88.4
38,560 stars · license n/a
DevOps
floci leads by 8.9 · clear
A
88.4
38,560 stars · license n/a
B · leads
97.3
31,872 stars · MIT
dokploy versus floci is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dokploy is written mainly in TypeScript; floci is written mainly in Java. The composite score is 88.4 for dokploy and 97.3 for floci.
dokploy has 38,560 GitHub stars to floci's 31,872, a gap of 6,688 (1.21×). Forks are 3,180 for dokploy and 3,521 for floci. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 99 versus 100.
Push history: dokploy 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 833 for dokploy (0.022 per star) and 215 for floci (0.007 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
dokploy 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 dokploy and 96 for floci. This is a procurement signal, not legal advice.
In DevOps, both dokploy (38,560 stars) and floci (31,872 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: dokploy is unpriced in this catalog, floci is open source.
The lead is split. dokploy is furthest ahead on adoption (100 to 98), while floci is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
floci finishes ahead at 97.3 against dokploy at 88.4, a 8.9 point clear 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 | dokploy | floci |
|---|---|---|
| GitHub stars | 38,560 | 31,872 |
| Forks | 3,180 | 3,521 |
| Open issues | 833 | 215 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 99 | 100 |
| Issue health | 70 | 84 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 88.4 | 97.3 |
Open Source Alternative to Vercel, Netlify and Heroku.
Light, fluffy, and always free - The AWS Local Emulator alternative
dokploy has more GitHub stars: 38,560 versus 31,872 for floci. The gap is 6,688 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dokploy and floci as self-hostable. Confirm each project's deploy docs before you plan a migration.
dokploy 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.
floci scores 97.3 and dokploy scores 88.4. This page calls that a clear lead for floci.