Inkheartvsshelfmark
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Inkheart | shelfmark | |
|---|---|---|
| Score | 53/100 | 67/100 |
| Rank in category | #30 of 47 in Document Management | #10 of 46 in Download Management |
| GitHub stars | — | 4 159 |
| Stars, last 30 days | — | +149 |
| Stable releases, 12 months | 0 | 30 |
| Latest release | — | v1.7.0 · 13 Nov 2026 |
| Setup | Easy | Moderate |
| Official Docker image | Yes | Yes |
| License | apache-2.0 | MIT |
| Main language | — | Python |
Which one should you pick?
shelfmark scores 67/100 against 53/100 for Inkheart, so it is the safer default.
shelfmark ships more often: 30 stable releases in the past year, against 0 for Inkheart.
If you want the quickest setup, Inkheart is easier to run; shelfmark needs more configuration.
shelfmark is growing faster right now (+149 stars in 30 days).
Key differences
- License: Inkheart is apache-2.0, shelfmark is MIT.
- Features only Inkheart lists: Collections, Cover extraction, Direct page links, Embeddable reader and 8 more.
- Features only shelfmark lists: Audiobook support, Download queue with live progress, Email delivery of downloads, Health endpoint and 9 more.
Inkheart details →shelfmark details →
Swap a project
Keep Inkheart, compare it with
Keep shelfmark, compare it with