A · leads
serviette
97.3
58,707 stars · MIT
Self-Hosted
serviette leads by 2.0 · narrow
A · leads
97.3
58,707 stars · MIT
B
95.3
16,893 stars · Apache-2.0
serviette versus SurfSense is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Python. The composite score is 97.3 for serviette and 95.3 for SurfSense.
serviette has 58,707 GitHub stars to SurfSense's 16,893, a gap of 41,814 (3.48×). Forks are 1,551 for serviette and 1,613 for SurfSense. On the log scale used inside this pair, adoption is 100 versus 89, and the fork community is 100 versus 100.
Push history: serviette was last pushed on 10 November 2026 (7 days ago), and SurfSense was last pushed on 14 November 2026 (3 days ago). Open issues stand at 6 for serviette (0.000 per star) and 64 for SurfSense (0.004 per star). Issue-health scores are 96 and 96; activity scores are 92 and 100.
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. SurfSense 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. License scores in this pair are 96 for serviette and 96 for SurfSense. This is a procurement signal, not legal advice.
In Self-Hosted, both serviette (58,707 stars) and SurfSense (16,893 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: serviette is open source, SurfSense is open source.
The lead is split. serviette is furthest ahead on adoption (100 to 89), while SurfSense is furthest ahead on recent activity (100 to 92). Choose the dimension a rollout cannot compromise on.
serviette finishes ahead at 97.3 against SurfSense at 95.3, a 2.0 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 | serviette | SurfSense |
|---|---|---|
| GitHub stars | 58,707 | 16,893 |
| Forks | 1,551 | 1,613 |
| Open issues | 6 | 64 |
| Adoption | 100 | 89 |
| Activity | 92 | 100 |
| Community | 100 | 100 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.3 | 95.3 |
A no-code RAG server that keeps answers in sync with your documents. Works with 8 vector databases. Built on Pathway.
Air-gapped, privacy-focused, open-source NotebookLM alternative. AI agent that researches, transforms, and edits your documents. Join our Discord: https://discord.gg/ejRNvftDp9
serviette has more GitHub stars: 58,707 versus 16,893 for SurfSense. The gap is 41,814 stars.
SurfSense was pushed more recently: 14 November 2026 versus 10 November 2026 for serviette. That is 4 days apart.
Yes. This catalog marks both serviette and SurfSense as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. SurfSense 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
serviette scores 97.3 and SurfSense scores 95.3. This page calls that a narrow lead for serviette.