Karakeep vs Cowpin: Self-Hosted Read-It-Later Without Running a Stack

Let's start where a fair comparison should: Karakeep is one of the best projects in this category. It started life as Hoarder, renamed in 2025, and today it's AGPL-3.0, actively developed, and among the most starred bookmark / read-it-later repos on GitHub. Links, notes, images, AI-assisted tagging, full-text search, browser extensions, RSS ingest, highlights, rules, native iOS and Android apps, and a real API. Self-hosting is free; Karakeep Cloud is in public beta with a free tier and Pro around $4/month.

If you're already running Karakeep on a box you trust and you're happy, this post is not trying to talk you out of it.

What this post is for: you're weighing run the stack yourself (or pay for Karakeep Cloud) against use something hosted, and you want the trade stated plainly — plus, if you try Cowpin, what actually moves over today.

Two different centers of gravity

Karakeep is an everything drawer: links, clipped text, images, AI organisation, mobile-first capture. The name is deliberate — it's built to hoard stuff, not just URLs.

Cowpin is a tag-first link library with archived page text, semantic search, in-app highlights, and an agent-facing API (including MCP for Cursor and other tools). We are narrower on purpose: fewer surfaces, stronger search and export on the pages you save.

Neither framing is universally "better." They answer different questions.

What self-hosting Karakeep buys you

Same three wins as any good self-hosted tool:

Nobody can flip a shutdown switch on your instance. Your Postgres (or whatever you run) is the source of truth.

The archive can live on your disk. Karakeep's value is partly keeping what you saved — not just the URL.

Marginal cost is flat. Ten links or ten thousand, it's still your VPS bill.

If that trio is what you optimize for, Karakeep self-host is a serious answer. So is linkding or Wallabag — this post is Karakeep specific because it's the one people mention next to "AI tags + mobile apps."

What it costs you

The honest list:

• You operate it. Backups you have restored from, image updates, TLS, DB upgrades, and the week the container won't start.
• Mobile access to your home box means a domain, certificates, and either exposing a port or running a tunnel — each is a thing that breaks quietly.
• Feature surface = attack surface. More moving parts (AI providers, asset storage, workers) means more to configure and more to patch.

Karakeep Cloud trades ops for a subscription — same product direction, less Saturday debugging.

Where Cowpin is different (not "better")

Three axes that actually diverge:

Search that answers questions. Cowpin indexes archived page text and supports semantic search plus "ask your library" — plain-language retrieval over what you saved. Karakeep's search is strong inside its own model; Cowpin optimizes for find the paragraph you half remember.

Highlights with a clean export path. Select text in the reader, export per page or your whole library to Markdown for Obsidian or Notion.

Zero operations. No Docker, no worker queue, no backup drill. That's the whole pitch on this axis.

Cowpin is hosted and younger than Karakeep. We don't ship native iOS/Android apps — we ship a PWA, a browser extension, and API automation. Karakeep wins outright if native mobile capture is non-negotiable.

Karakeep → Cowpin: what Netscape HTML moves today

Karakeep can export bookmarks as JSON or Netscape HTML (Settings → export). Cowpin's HTML importer is built for that Netscape format — the same path we document for linkding.

Practical paths:

1. Backup JSON (Settings → export/backup) — Cowpin detects Karakeep’s { bookmarks: [...] } export automatically on upload.
2. Netscape HTML — same as before if you prefer browser-compatible export.

Field-by-field reality checked against Karakeep's Netscape exporter (link bookmarks only — text notes and image assets are omitted from that format):

That table is intentionally conservative. If you rely on Karakeep highlights or image/text bookmarks, Netscape and JSON both have gaps — use JSON for links and accept skipped assets, or stay on Karakeep for those items.

About archived text: like every migration post we've written, the heavy archive does not travel in a bookmark export. Cowpin fetches what it can after import; dead links stay dead.

Cowpin → Karakeep: the way back out

Karakeep imports Netscape HTML from its settings UI (same format browsers use). Cowpin exports Netscape HTML with tags, privacy, notes, read-later, and save dates — so the door swings back: try Cowpin, export, import into Karakeep if you decide you want the stack after all.

We have not run that round trip against every Karakeep release; if you hit an edge case, tell us and we'll fix it the same way we fixed linkding's TOREAD gap.

How to decide

Stay on Karakeep (self-host or Cloud) if: you want AI tagging, notes + images in one vault, native mobile apps, and you're willing to operate — or pay — for that bundle.

Try Cowpin if: you want hosted search and highlights, agent/API automation, or your Karakeep install has been "almost ready" for months and you mainly need a durable link library now.

Or split roles. Keep Karakeep as capture + mobile; mirror link exports into Cowpin for search and reading. Netscape HTML makes that boring instead of heroic.

Export Netscape HTML from Karakeep, import into Cowpin, and you'll have your link library — tags and dates intact for typical libraries — in about a minute. Cowpin is free while we're finding our first users, and you can export back out whenever you like.

Import your library →