Burkmak vs KeepR
Burkmak
github.comKeepR
github.comSide by side
| Figure | Burkmak | KeepR |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | — |
| Windows | — | Yes |
| macOS | — | Yes |
| Android | Yes | — |
| API | Yes | — |
| Self-hosted | Yes | — |
| Plans published | 1 | 0 |
| Spec score · Read-It-Later Apps | 8.5 (#10) | 7.5 (#19) |
| Spec score · Read-later apps | 7.9 (#17) | 6.9 (#26) |
| Privacy | The product requirements state there are no third-party analytics and that content fetched server-side stays on the self-hosted instance. | The maker says KeepR has no account, cloud service, telemetry, or runtime network requests. |
| Purpose | Burkmak is a self-hosted, multi-user read-it-later app for saving links, reading articles, highlighting text, syncing with Kobo, and exporting notes to Obsidian. | KeepR manages receipts, expenses, and documents in a searchable library stored on the user's disk. |
Plans
In their own words
Burkmak
Burkmak is a free, MIT-licensed, self-hosted read-it-later application for saving links, reading articles, highlighting passages, syncing with Kobo, and exporting notes to Obsidian. Its reader extracts articles into a clean view with highlights and notes, while tags, read states, favorites, and search organize per-user libraries. Links can be captured through the web app, Android share sheet, or desktop browser bookmarklet. Kobo support provides an OPDS catalog for EPUB and KEPUB downloads plus native store-protocol synchronization that writes reading state back. An Obsidian plugin transfers article notes, highlights, and metadata through Burkmak’s export API. Docker Compose deployment includes backend and web containers, a data volume, and amd64 and arm64 images; the volume stores the SQLite database, cached articles, images, and EPUBs. Product requirements state that server-fetched content remains on the self-hosted instance and no third-party analytics are used. Native Kobo synchronization requires HTTPS, physical-device support remains pending, and the architecture targets one instance rather than horizontal scaling or high availability.