Karakeep

Every bookmark manager eventually betrays you. Pocket shut down in 2025 after Mozilla decided read-it-later wasn’t worth the server bill, taking a decade of saved articles with it unless you exported in time. Delicious died. Instapaper has changed hands so many times it should come with a chain-of-custody form. The pattern is boring and predictable: you spend years building a personal reference library inside someone else’s business model, and then the business model changes.

Karakeep — until recently called Hoarder, and still carrying that name’s cheerfully undignified honesty in its share-sheet copy — is a response to that pattern. It’s a free, open-source, self-hostable archive for links, notes, images, and PDFs, published on mobile by Localhost Labs. The pitch is structural rather than featural: your bookmarks live on a server you own, the mobile apps are thin clients pointed at that server, and the developer collects nothing because there’s nothing for them to collect. That’s not a privacy promise. It’s a privacy architecture, which is a different and far more durable thing.

The market position is unusual. Karakeep isn’t competing with Pocket on convenience — it can’t, because step one is “run a server.” It’s competing with Raindrop.io on capability and losing on setup, while competing with the entire self-hosted stack (Linkwarden, Wallabag, Archivebox) on polish. Wallabag has been the sensible-shoes option in this category for years; Karakeep is that same idea built with a design sensibility and an AI pipeline.

The reception so far is modest: on iOS the app holds a 4.6/5 across 44 ratings. Those are small numbers, and they should be — the addressable market is “people who own a server.”

• Full-page archival, not just link storage: Save a URL and Karakeep fetches the page, archives it, and extracts a readable full-text copy. When the source 404s in three years — and it will — you still have the content. This is the difference between a bookmark and an archive.
• AI auto-tagging with local model support: Every saved item gets run through an LLM that generates descriptive tags. Point it at a hosted provider, or point it at Ollama on your own hardware and keep the entire pipeline inside your network. The library organizes itself without you ever opening a folder.
• Full-text and semantic search: Everything indexed. Newer builds add semantic search, so you can find the article about “that database thing with the write-ahead log” without remembering a single exact word from it.
• Native share extension: One tap from any app on the device — browser, Mastodon client, Slack, email — and the item is hoarded. This is the feature that determines whether a save-it-later app becomes habit or abandonware.
• Smart rules and custom lists: Automated organization logic on top of manual grouping, plus quick notes and clipboard images stored as first-class items alongside links.
• Cross-platform sync: Same account across web dashboard, mobile apps, and browser extensions for Chrome, Firefox, and Safari.

The Capture Loop

The only metric that matters for a save-it-later tool is whether saving is frictionless enough that you do it without thinking. Everything else is downstream. An archive you don’t feed is an empty archive.

Karakeep’s mobile clients are built around this, and the share extension is why. It’s native, and it does the one thing it needs to do: accept content and get out of the way. Share extensions are normally invisible infrastructure that nobody praises until it’s broken; making it a headline feature suggests the competition has set a low bar.

The payoff is on the other side of the save. Because the server fetches and archives the page rather than storing a pointer, and because the AI tagger fires automatically, the marginal cost of saving something drops to nearly zero and the marginal cost of organizing it drops to actually zero. That combination is the whole product thesis. Traditional bookmark managers make saving cheap and organizing expensive, which is precisely why everyone’s bookmark bar is a graveyard of untitled folders.

Does the AI Tagging Actually Work?

Automated tagging has a long and embarrassing history. The failure mode is tags that are technically accurate and completely useless — every article about software tagged “technology,” “software,” “computers.” Karakeep sidesteps this by feeding the model the extracted full text rather than just the title and URL, which gives it enough context to produce tags with actual specificity.

The genuinely interesting decision is letting you choose the model. Run it against a hosted provider for quality, or against a local Ollama instance for privacy — and critically, the app doesn’t treat the local option as a degraded fallback. If you’ve gone to the trouble of self-hosting your bookmarks specifically so nobody else reads them, shipping every archived page to a third-party API for tagging would be an absurd contradiction. Karakeep is one of very few AI-tagging tools that closes that loop honestly. The tradeoff is real: local models tag more slowly and less precisely than frontier ones, and on modest hardware the queue backs up. But it’s your tradeoff to make, not a product decision imposed on you.

Semantic search in newer builds is the natural extension of the same pipeline, and it’s the feature that turns the archive from storage into something you actually query. Full-text search finds what you remember. Semantic search finds what you half-remember, which is the far more common case six months after saving something.

Where the Mobile Apps Fall Short

Here’s the honest part. The mobile clients are noticeably thinner than the web dashboard. Highlights are missing. In-app editing is limited. Tag management — arguably the thing you’d most want to do from your phone while triaging a backlog on the train — is weaker on mobile than on desktop. There’s no multi-column layout, which on a modern large-screen phone or a tablet is a real waste of pixels.

None of this is fatal, but it defines what the apps are for. Karakeep on mobile is a capture-and-consume device: hoard aggressively, read comfortably, search effectively. Curation happens at a desk. That’s a defensible split, and plenty of tools make it deliberately. But the gap currently reads as unfinished rather than intentional, and the roadmap will be judged on whether it closes.

Then there’s the setup wall. You need a server. Not metaphorically — an actual machine running the Karakeep stack, reachable from your phone, with whatever reverse proxy and TLS arrangement that implies. For anyone who already runs a home lab this is a Tuesday-evening docker-compose job. For everyone else it’s a hard stop. There’s no hosted tier to soften the on-ramp, which is philosophically consistent and commercially limiting in equal measure.

The design language is clean, modern, and mercifully restrained — a card-based library view that lets thumbnails and titles do the work rather than burying content under chrome. It looks like a 2026 app, which is worth stating plainly because self-hosted software has a long tradition of looking like a 2011 phpBB skin. Localhost Labs clearly has a designer, and it shows.

Performance is where self-hosting gets interesting, because Karakeep’s speed is partly your speed. The search index is built for quick lookups, which is the app’s own doing. But archival latency, tagging turnaround, and thumbnail generation all depend on the hardware you point it at. A Karakeep on a Raspberry Pi and a Karakeep on a proper mini-PC are different products in daily use. Complaints about slow tagging are, in a meaningful number of cases, complaints about the server behind the app. The app can’t fix that, but it could communicate it better — surfacing job queue status in the mobile UI would go a long way toward turning “this is broken” into “this is working.”

iOS is the stronger client. The share extension is designed to sit in the share sheet exactly where muscle memory expects it. One design flaw stands out, though: the on-screen keyboard covers the save button when entering a long note. It’s a keyboard-avoidance layout issue, and it’s the kind of thing that sours an otherwise polished experience because it hits during an active task. Fix it and the iOS app has little left to apologize for.

Android trails, and the platform’s fragmentation means more rough edges across a wider range of devices. The share intent is solid — arguably Android’s sharing model suits Karakeep’s “hoard from anywhere” premise better than iOS’s does. But the absence of a multi-column layout stings more here, where large-screen phones and tablets are common and the ecosystem has spent years pushing developers toward adaptive layouts. On a foldable, the current UI is a phone app stretched wide.

Both platforms share the same foundational quirk: the first-run experience assumes you already have a server URL and credentials in hand. There’s no onboarding wizard, because there’s no onboarding to wizard — the hard part happened before you opened the app.

Karakeep is self-hosted software that doesn’t ask you to accept ugliness as the price of ownership. The archival pipeline is thoughtfully built, the AI tagging addresses the organization problem that has defeated bookmark managers since the browser bookmark bar, and the option to run that tagging on a local model is the sort of principled follow-through that most “privacy-focused” products quietly skip.

The mobile apps are the weak link, and they’re weak in a forgivable direction — they capture and consume well while punting curation to the desktop. That’s a gap, not a flaw, provided it keeps closing. The iOS keyboard bug should have been fixed three releases ago.

What you’re really getting — for free, which is its own argument — is permanence. In a category littered with shutdown notices, Karakeep’s answer is that nobody can shut down your server but you. For the right audience, that’s worth a weekend of docker-compose.