A
core
86.8
8,853 stars · AGPL-3.0
Self-Hosted
serviette leads by 10.0 · clear
A
86.8
8,853 stars · AGPL-3.0
B · leads
96.8
58,707 stars · MIT
core versus serviette is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. core is written mainly in PHP; serviette is written mainly in Python. The composite score is 86.8 for core and 96.8 for serviette.
serviette has 58,707 GitHub stars to core's 8,853, a gap of 49,854 (6.63×). Forks are 2,061 for core and 1,551 for serviette. On the log scale used inside this pair, adoption is 83 versus 100, and the fork community is 100 versus 96.
Push history: core was last pushed on 16 November 2026 (1 day ago), and serviette was last pushed on 10 November 2026 (7 days ago). Open issues stand at 146 for core (0.016 per star) and 6 for serviette (0.000 per star). Issue-health scores are 84 and 96; activity scores are 100 and 92.
core 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. serviette 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 52 for core and 96 for serviette. This is a procurement signal, not legal advice.
In Self-Hosted, both core (8,853 stars) and serviette (58,707 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: core is open source, serviette is open source.
The lead is split. core is furthest ahead on recent activity (100 to 92), while serviette is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
serviette finishes ahead at 96.8 against core at 86.8, a 10.0 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 | core | serviette |
|---|---|---|
| GitHub stars | 8,853 | 58,707 |
| Forks | 2,061 | 1,551 |
| Open issues | 146 | 6 |
| Adoption | 83 | 100 |
| Activity | 100 | 92 |
| Community | 100 | 96 |
| Issue health | 84 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 86.8 | 96.8 |
:cloud: ownCloud web server core (Files, DAV, etc.)
A no-code RAG server that keeps answers in sync with your documents. Works with 8 vector databases. Built on Pathway.
serviette has more GitHub stars: 58,707 versus 8,853 for core. The gap is 49,854 stars.
core was pushed more recently: 16 November 2026 versus 10 November 2026 for serviette. That is 6 days apart.
Yes. This catalog marks both core and serviette as self-hostable. Confirm each project's deploy docs before you plan a migration.
core 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. serviette 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.
serviette scores 96.8 and core scores 86.8. This page calls that a clear lead for serviette.