Linkwarden
A bookmark manager that preserves pages - screenshot, PDF, readable HTML - so your links never rot.
One-click deploy, from $13/mo on a Miget plan.
Bookmarks are promises the web keeps breaking - the page moves, changes, or vanishes. Linkwarden fixes that by preserving every save: a screenshot, a PDF, a readable HTML copy, and an archive.org snapshot, alongside collections, tags, and full-text search across all of it.
This template runs the app on a managed Postgres behind a thin proxy (its port is fixed at 3000). Page archiving uses an in-container headless Chromium, so give it about a gigabyte - or flip to a lighter bookmarks-only mode. Archived copies live on the volume.
The case for owning this got made for us: Pocket shut down in 2025 and deleted everyone’s saved articles; Raindrop keeps your library on their servers. Linkwarden keeps both the links and readable copies on infrastructure you control.
Upstream project: Linkwarden
#what you get
- Auto-preservation: screenshot, PDF, readable HTML, archive.org
- Collections, nested folders, tags, full-text search
- Browser extensions and a mobile app
- Sharing and collaborative collections
- Managed Postgres; archives on the volume
- AGPL-3.0
#topology
| Service | Role | Public |
|---|---|---|
| linkwarden | app + archiving (:3000, fixed) | no |
| web | nginx :5000 -> linkwarden:3000 | yes |
| db | Postgres - managed service on Miget, container locally | no |
#miget sizing
// this stack needs
2 GiB RAM · 15 GB disk · 3 services
Archiving runs Chromium - ~1 GiB with it on; set DISABLE_PRESERVATION=true for a lighter bookmarks-only deploy. Archives accumulate on the volume.
Hobby - recommended fit
$13/mo
1 vCPU · 2 GiB · 50 GiB disk
Headroom for your own apps: 2 GiB at $19/mo
Professional - production
$43/mo
2 vCPU · 4 GiB · 25 GiB disk
Dedicated resources, production SLOs - plan details
One Miget plan is a fixed pool of compute - the whole stack (managed databases included) deploys inside it, and anything left over runs your other apps. No per-service or per-seat math.
#vs. the managed service
What the hosted equivalents charge, against the flat Miget plan this stack fits on. Prices as of June 2026, sources linked.
| Service | Plan | Monthly | What you get |
|---|---|---|---|
| Linkwarden on Miget ★ | 2 GiB plan | $13 | this whole stack, flat - no usage meters, and room left for your own apps |
| Raindrop.io | Pro | usage-based | ~$28/yr - and Pocket shut down in 2025 with all user data deleted, which is the whole argument for owning your bookmarks |
#vs. other PaaS
Estimated monthly cost of running this exact stack (2 GiB RAM, 15 GB disk, 3 containers) elsewhere, from published June 2026 rates.
| Platform | Est. monthly | Notes |
|---|---|---|
| Miget ★ | $13 flat | compose stacks first-class: one deploy, dedicated vCPU, managed Postgres/Valkey, volumes and TLS all included in the plan |
| Heroku | ~$100 | no volumes; nothing between 1 GB ($50) and 2.5 GB ($250) dynos - 2 GB containers cost far more than shown |
| Render | ~$29 | per-service instances (0.5 GB $7, 2 GB $25) - every container is its own paid service |
| DO App Platform | ~$29 | no persistent volumes - stateful containers need managed DBs/Spaces (base $5 Spaces included here) |
| Railway | ~$22 | usage-based ($10/GB RAM-mo); vCPU billed separately at $20/vCPU-mo on top |
| Fly.io | ~$14 | cheapest sticker price - but burstable shared CPUs (1/16 core; dedicated vCPUs cost ~2-3×), no compose deploys (one app per container, manual wiring), managed DBs billed extra |
Estimates assume RAM fully allocated at published on-demand rates - and sticker price isn't the whole comparison: the cheaper rows buy burstable shared CPUs, per-service wiring instead of a compose deploy, and managed databases billed separately. Heroku and DO App Platform have no persistent volumes at all - stateful stacks like this one need workarounds there.
#deploy it
On Miget
- Create a Compose Stack in app.miget.com pointing at the templates repository
- Set the stack path to
linkwarden -
Set the required variables:
NEXTAUTH_SECRET, session secretNEXTAUTH_URL, the https domain WITH the /api/v1/auth suffix
- Deploy. Miget layers
compose.miget.yaml(RAM, privacy, volumes, managed services) automatically
Locally first?
Every template is portable, vanilla Docker Compose - the Miget overrides are ignored locally:
git clone https://github.com/deployable-sh/stacks
cd miget-compose-templates/linkwarden
docker compose up -dSame files, same behavior. The template README covers connection strings and scaling notes.
#faq
Why archive pages instead of just saving links?
Because links die: studies put link rot in the double-digit-percent range within a few years. Linkwarden saves a screenshot, PDF, and readable copy at bookmark time, so a 404 later still leaves you the content you actually wanted.
What is the NEXTAUTH_URL gotcha?
It must include the /api/v1/auth path (e.g. https://links.example.com/api/v1/auth), not just the domain - the most common Linkwarden setup mistake. The README and env example both flag it.
Can I make it lighter?
Yes - set DISABLE_PRESERVATION=true to skip the Chromium archiving and run a bookmarks + tags + search service in well under a gigabyte. You lose the saved copies, keep everything else.
Ship Linkwarden today
One compose stack, 2 GiB of RAM, from $13/month flat, and it runs on your laptop with the same files.