Self-Hosted Bookmark Manager: Linkding, Shaarli, Wallabag — and When to Skip Self-Hosting Entirely

If you're searching for a self-hosted bookmark manager, you already know why: you don't want a company holding your library, you don't want to depend on someone else's business staying solvent, and you'd rather run a Docker container than trust a startup's uptime. That's a completely reasonable position. Here's an honest map of the real options — and an honest case for when self-hosting isn't actually buying you what you think it is.

The real self-hosted options

Linkding

The most popular pick for a reason: a single lightweight Docker container, tags, a browser extension, a REST API, and a clean, fast UI with no bloat. Backups are just "copy the SQLite file." If you're going to self-host a bookmark manager, this is the default good choice.

You run: the container, its updates, and its backups.

Shaarli

Older, PHP-based, minimal — one file config, no database server required. It doubles as a shareable link-blog (public/private links, RSS), which Linkding doesn't really do. Feels dated but is genuinely low-maintenance once it's up.

You run: a PHP host, updates, and backups.

Wallabag

The self-hosted read-it-later app — think "Instapaper you own," with full article archiving. If your priority is capturing full article text (not just links), this is the closest self-hosted match. Heavier than Linkding or Shaarli (needs a proper database), so plan for that.

You run: the app, its database, updates, and backups.

What self-hosting actually costs you

This is the part self-hosting posts often skip. Running any of the above means you're now responsible for:

A server, even if it's a $5/mo VPS or a Raspberry Pi under your desk.
Updates — security patches don't apply themselves, and bookmark managers handle credentials and, in Wallabag's case, fetch arbitrary web content.
Backups you've actually tested. "I have a backup" and "I've restored from that backup and it worked" are different claims. A dead disk with no tested restore is worse than no backup — false confidence.
Uptime and access from your phone. Self-hosted means it's down when your home internet is down, unless you've also set up dynamic DNS or a tunnel.
You, at 11pm, when it breaks. There's no support line. The tradeoff for ownership is that debugging is entirely on you.

None of that is a reason to avoid self-hosting — plenty of people want exactly this level of control and enjoy the tinkering. It's a reason to be honest that "self-hosted" and "zero-maintenance" are different things, and to pick the option that matches how much of that you actually want to sign up for.

What you're really after (usually)

Talk to most people looking for a self-hosted bookmark manager and the actual goals are: own your data, don't get locked in, keep it private, don't pay a subscription for basic organization. Self-hosting is one way to get those things. It's not the only way.

Cowpin is a hosted alternative that gets you most of the same guarantees without the server:

Export anytime, in a standard format — the actual antidote to lock-in. If a hosted service can't promise a one-click export you can walk away with, that's the real problem "self-host it" is trying to solve — and Cowpin solves it directly instead.
A real, open API (Pinboard-compatible), so you can still script your library, back it up yourself, or point your own tools at it, without running the server.
Full-text search and auto-archiving included — the features Wallabag gives you self-hosted, without the database to maintain.
Free while in beta, no subscription pressure to worry about.
We patch it, back it up, and keep it up — the maintenance burden above is simply ours, not yours.

The honest trade: you're giving up "nobody but me ever touches this data" for "nobody has to SSH in at 11pm to fix it." For a lot of people that's the right trade. For people who specifically want zero-trust, fully-offline-capable, never-touches-someone-else's-server ownership, it isn't — and Linkding is a genuinely great answer for that.

How to choose

You enjoy running services and want total control: Linkding (general bookmarks) or Wallabag (read-it-later/archiving). Both are solid, real open-source projects worth using.
You want minimal upkeep, tiny footprint, PHP-only: Shaarli.
You want the ownership guarantees (export, open API, no lock-in) without running a server: Cowpin — hosted, but built so you're never trapped.

Whatever you pick, do the one thing that actually matters regardless of platform: make sure you can get all your data out, in a real format, at any time. That's the property worth optimizing for — "self-hosted" is one way to guarantee it, not the only one. Try Cowpin free if you want that guarantee without the server.