Skip to content
SPECIFICTION
Get listed

Burkmak vs wallabag

Burkmak

github.com

wallabag

wallabag.org

Side by side

FigureBurkmakwallabag
Price fromFree€0.92/mo
Free planYesYes
Free trial—Yes
Open source—Yes
WebYesYes
Linux—Yes
iOS—Yes
AndroidYesYes
APIYesYes
Self-hostedYesYes
Plans published14
Spec score · Read-It-Later Apps8.5 (#10)8.6 (#9)
Spec score · Read-later apps7.9 (#17)9.4 (#1)
Browser extensionNoYes
Full-text searchYesYes
HighlightingYesYes
LicenseThe repository identifies the project as MIT licensed.The wallabag source code repository identifies the project license as MIT.
Mobile appsYesYes
PrivacyThe product requirements state there are no third-party analytics and that content fetched server-side stays on the self-hosted instance.The hosted service says it is funded by subscriptions rather than advertising, tracking, or selling user data.
PurposeBurkmak 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.wallabag saves web articles, extracts their content, and presents them in a clean reading view for later.

Plans

Burkmak

  • Self-hostedFree

Burkmak pricing →

wallabag

  • wallabag self-hostedFree
  • 3 months€4, paid once
  • 1 year€11 a year
  • The ❤️ subscription€30 a year

wallabag pricing →

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.

Visit github.com

wallabag

wallabag has no write-up on Specifiction yet; its figures are above.

Visit wallabag.org