I host Wallabag, besides the features already mentioned here, two others I use frequently and are crucial to my workflows are the following integrations:

• Koreader integration, so I can access my articles on any ereader
• Logseq integration, so that all read articles and highlights/annotations are synced with my knowledge base

I was really enjoying wallabag for a while, but after an update (or something?) the container no longer connects to the db and I haven’t been smart enough to figure out why yet.

BUT when it works it’s got a nice interface and the Firefox extension clips articles quickly. Biggest downside I’ve run into is the iOS app can’t make highlights or annotations, and it sometimes randomly reloads an article while reading and ‘forgets’ its place.

I am using wallabag since a long time (selfhosted). And I am loving it. With the Android app I can simply share to the app to save Websites from any Browser. But I have no experience with Readdeck.

I just set up Readeck a few weeks ago, and I’ve been liking it. Very minimalist, utilitarian. One feature I’d like that isn’t included is the ability to add specific labels or collections to the sidebar, but that’s my only quibble so far.

It has an official browser extension for adding urls to it, but if you can’t or don’t want to use that, it has a nice api. I use the api to add bookmarks from my phone using a termux-url-opener script, which is as easy as the extension - just hit the “share” button and select termux, and it does the rest.

I have no experience with Wallabag, but I have been pretty happy with Readeck. Skimming through Wallabag’s documentation, I would say they are pretty similar, while both have unique features. For example, Wallabag has annotations (you can only highlight in Readeck), and Android and iOS apps; whereas Readeck can export collections to eBooks, has RSS feeds for pretty much anything (all articles, unread, archives, collections, etc.) and its browser extension allows to only save part of a page (by selecting it first) and to directly send the page content to your instance (which is useful when saving paywalled content)