2048 MB RAMamd64 / arm64TypeScriptMediumAGPL-3.0-onlyVersion 0.34.1
Instead of a subscription
Self-hosted alternatives to Raindrop.io
Raindrop.io collects bookmarks with previews and collections, and puts full-text search and permanent copies on paid tiers. The archivers here keep the collections and the page copy on your disk from the start.
Catalog
Recipes that cover it
2048 MB RAMamd64 / arm64TypeScriptMediumAGPL-3.0-onlyVersion v2.16.3
512 MB RAMamd64 / arm64 / armv7PHPEasyMITVersion 2.6.15
Requirements
Side by side
| Application | Minimum RAM | Disk estimate | Database | Installation difficulty | Backup | Recipe verification | License |
|---|---|---|---|---|---|---|---|
| Karakeep | 2048 MB RAM | 10 GB | SQLite | Medium | Yes · Restore tested | Fully verifiedRecheck overdue · 0 dCheck is current | AGPL-3.0-only |
| Linkwarden | 2048 MB RAM | 5 GB | PostgreSQL | Medium | Yes | Fully verifiedRecheck overdue · 0 dCheck is current | AGPL-3.0-only |
| Wallabag | 512 MB RAM | 2 GB | SQLite | Easy | Yes · Restore tested | Fully verifiedRecheck overdue · 0 dCheck is current | MIT |
The bill
The subscription against a server
Both figures are editable, because only you know which of them you actually pay. The server is sized from the figure the recipe recommends — the same one the catalog calls a comfortable fit on your profile — and not from the cheapest row of a price list.
Karakeep asks for 4 GB of RAM, 2 vCPU and 10 GB of disk — $24 a month on DigitalOcean Basic.
The difference
- Per month
- $21.67
- Per year
- $260.04
- Over three years
- $780.12
The subscription wins on price by $260.04 a year. What hosting it buys you here is the data, not the money.
Not counted: your own time, a domain, and a backup kept anywhere other than that same server. A machine you already run costs nothing extra — set the server to zero.
Raindrop.io · Pro, billed annually, price checked 2026-09-10Server prices: DigitalOcean Basic, checked 2026-09-10
Migration
What changes when you host it yourself
The data stops leaving your network, and so does the responsibility for it: backups, the restore you have actually tested, and the disk it all sits on.
Feature parity is never exact. Read what each recipe states about limitations and the smoke test before planning a migration.
The bill turns into work: updates, certificates and an eye on the release notes. The catalog shows how much of that each recipe asks for.