A
neko
95.0
22,688 stars · Apache-2.0
Self-Hosted
serviette leads by 2.2 · narrow
A
95.0
22,688 stars · Apache-2.0
B · leads
97.2
58,707 stars · MIT
neko versus serviette is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. neko is written mainly in Go; serviette is written mainly in Python. The composite score is 95.0 for neko and 97.2 for serviette.
serviette has 58,707 GitHub stars to neko's 22,688, a gap of 36,019 (2.59×). Forks are 1,662 for neko and 1,551 for serviette. On the log scale used inside this pair, adoption is 91 versus 100, and the fork community is 100 versus 99.
Push history: neko 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 144 for neko (0.006 per star) and 6 for serviette (0.000 per star). Issue-health scores are 84 and 96; activity scores are 100 and 92.
neko 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. 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 96 for neko and 96 for serviette. This is a procurement signal, not legal advice.
In Self-Hosted, both neko (22,688 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: neko is open source, serviette is open source.
The lead is split. neko is furthest ahead on recent activity (100 to 92), while serviette is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
serviette finishes ahead at 97.2 against neko at 95.0, a 2.2 point narrow 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 | neko | serviette |
|---|---|---|
| GitHub stars | 22,688 | 58,707 |
| Forks | 1,662 | 1,551 |
| Open issues | 144 | 6 |
| Adoption | 91 | 100 |
| Activity | 100 | 92 |
| Community | 100 | 99 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 95.0 | 97.2 |
A self hosted virtual browser that runs in docker and uses WebRTC.
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 22,688 for neko. The gap is 36,019 stars.
neko was pushed more recently: 16 November 2026 versus 10 November 2026 for serviette. That is 6 days apart.
Yes. This catalog marks both neko and serviette as self-hostable. Confirm each project's deploy docs before you plan a migration.
neko 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. 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 97.2 and neko scores 95.0. This page calls that a narrow lead for serviette.