Raindrop.io vs Karakeep: Managed Polish or Self-Hosted Control?

Raindrop.io is a managed bookmark service with polished apps, visual organization, and collaboration. Karakeep is an open-source “bookmark everything” system designed with self-hosting as a first-class use case. The hard choice is not feature count. It is who operates the storage, search index, crawler, AI, upgrades, backups, and recovery.

Bottom line

• Choose Raindrop.io when you want a mature hosted experience, nested collections, broad first-party clients, easy collaboration, and no infrastructure duty.
• Choose Karakeep Cloud when Karakeep's capture/search model fits but you do not want to run it.
• Self-host Karakeep when data location, extensibility, local-model options, and control are worth ongoing administration.

Current pricing is more nuanced than “paid versus free”

Karakeep's official pricing, checked 21 September 2026, lists:

• Cloud Free: 10 bookmarks and 20 MB storage.
• Cloud Pro: $4/month or $40/year, with 50,000 bookmarks, 50 GB, AI tagging, and full-text search.
• Self-hosted: free software with unrestricted features; you supply infrastructure and support.

Raindrop's official plan page offers a much more capable free tier: unlimited bookmarks, collections, highlights, and devices, plus 100 MB/month uploads. Pro adds permanent copies, full-text search, AI assistance, annotations, reminders, link checks, daily backups, and 10 GB/month uploads. Its displayed checkout price can depend on region and billing channel.

Self-hosting is not zero-cost. Budget storage, backups, a domain/TLS if exposed publicly, server time, monitoring, upgrades, and any commercial model API. A small home server may cost little in cash but still has an operator.

Capture and content preservation

Both products have browser extensions and iOS/Android apps. Raindrop additionally emphasizes a broad polished client set across Mac and major browsers. For ordinary “save this URL” capture, either is sufficient.

Karakeep goes further into acquisition. Its official feature list includes fetched titles/descriptions/images, RSS auto-hoarding, OCR for images, mobile offline reading, highlights, full-page archival through Monolith, and optional video archival through yt-dlp. Those features make it attractive when links are evidence or source material rather than pointers.

But archival must be configured and tested. Karakeep's Docker guide describes full-page archival and screenshots as optional features, and video downloads add substantial storage and legal considerations. Authenticated, paywalled, or highly interactive pages can fail. Raindrop Pro's permanent copies are simpler operationally, but are still a vendor-managed rendition rather than your own independently verified preservation pipeline.

Organization, search, and AI

Raindrop uses nested collections, tags, visual layouts, filters, and shared collections. Human curation is the default; AI suggestions and assistance are paid enhancements. It is the stronger product for a carefully arranged, browsable library where covers and hierarchy communicate meaning.

Karakeep organizes with lists and tags, supports collaborative lists and bulk actions, and emphasizes full-text plus semantic search. Optional LLM processing can generate tags and summaries. It can use external OpenAI-compatible services or local models through Ollama, making the privacy/cost/quality trade-off explicit.

“Local AI” is not automatically private: verify that embeddings, OCR, metadata extraction, and fallbacks are also configured to stay local. It also is not free in operational terms; model memory, compute, latency, and upgrades become your responsibility. Users who enjoy tuning retrieval may see that as control. Everyone else may see a maintenance queue.

Self-hosting reality

The supported Docker installation requires Docker and Docker Compose and runs multiple persistent services, including Meilisearch. The docs recommend pinning versions when you want controlled upgrades and call out special care for Meilisearch migrations. A production deployment additionally needs HTTPS, authentication policy, outbound-fetch safeguards, capacity planning, and tested restore procedures.

A responsible self-hosting checklist is therefore:

1. Pin a known-good release instead of tracking release blindly.
2. Back up all persistent volumes and configuration, not merely exported bookmark rows.
3. Restore those backups into a clean environment at least once.
4. Monitor free disk space; screenshots, page archives, PDFs, and video grow faster than URLs.
5. Restrict registration and protect secrets; do not expose a default compose stack unchanged.
6. Decide whether model requests may leave the server.

Raindrop removes nearly all of that work but also removes server-level control. You trust the provider's availability, account controls, retention, and data processing.

Collaboration and platform fit

Raindrop's shared collections are easy to hand to nontechnical colleagues, and its visual layouts suit editorial, design, and team resource sets. Karakeep supports shared lists, but the self-hosted administrator also owns invitations, uptime, upgrades, and support. Karakeep Cloud narrows that usability gap.

For one privacy-conscious technical user, Karakeep can be compelling. For a mixed-skill team that just needs shared links to work on every device, Raindrop is usually lower risk. For an organization requiring SSO or managed isolation, compare Karakeep's custom team offering with Raindrop's current business controls rather than assuming a consumer plan is adequate.

Imports, exports, and exit risk

Raindrop's importer accepts HTML, CSV, JSON, TXT, and ENEX. Its backup/export guide offers HTML, CSV, and TXT; bookmarks, collections, tags, highlights, and notes are covered, while uploaded files require a separate ZIP. Pro adds automatic daily backups, but an export is not the same as a disaster-recovery restore.

Karakeep documents importers for browser bookmarks, Pocket, Linkwarden, Omnivore, and other sources, and its cloud pricing page says bookmarks can be exported at any time. Before adopting it, verify the exact export available in the version or cloud plan you will use. Preserve both a portable bookmark export and server backups because an application export may omit archives, screenshots, videos, user accounts, sharing rules, or search state.

Moving between the two is not lossless. Nested Raindrop collections may not map cleanly to Karakeep lists; generated tags and semantic indexes do not become a Raindrop hierarchy. In either direction, test URLs, titles, original timestamps, notes, tags, highlights, uploaded files, archived content, and duplicates on a sample before moving the full library.

Who should avoid each?

Avoid Raindrop if self-hosting is mandatory, you need control over archive files, or local-model AI is a firm requirement. Avoid self-hosted Karakeep if nobody owns patching, backups, restore testing, security, and storage. Avoid Karakeep Cloud Free for anything beyond evaluation: ten bookmarks is intentionally a trial-sized limit.

When Save This One is the honest alternative

Save This One fits a narrower hosted use case: free link capture, tags, notes, search, reader view, imports, API access, and MCP, without running a server or designing a collection tree. It does not offer Karakeep's self-hosting, full-page/video archival, local AI, or semantic infrastructure, and it does not match Raindrop's visual collections, native-app breadth, file handling, or collaboration. Choose it only when “save and retrieve links” is genuinely the whole job.

The durable decision is operational: managed breadth with Raindrop, controllable infrastructure with Karakeep, managed Karakeep semantics through its cloud, or a deliberately smaller hosted library.