Documents and notes decision

Raindrop.io

Reimplementing a focused bookmark service (save/search/sync/archiving) is feasible for a small team, but the full Raindrop product (polished cross-platform apps, scale, AI assistant, and long-term web-archive) is costly to match — consider building a narrower replacement or self-host existing OSS pieces.

Visit website
Subscription$3/month
Initial build80 hours
Monthly upkeep8 hours + $50
Evidence3/3 runs agree

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.

What a replacement has to do

  • Save a URL with metadata, tag/organize it into collections, sync and search saved items, view an instant preview/web-archive of saved pages.

What it still won’t have

  • Polished official native apps for Windows/macOS/iOS/Android and polished browser extensions
  • Built-in full web-archive at scale and guaranteed long-term snapshot retention
  • AI Assistant and AI Suggestions tuning and hosted inference
  • Priority support and platform-level integrations listed on the vendor site
  • Desktop sync polish, multi-device account handling and platform QA

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying ischeaper in year one.

On cash alone, building overtakes the subscription at 20 seats.

Paid seatsseats

Money you would actually spend

Keep paying

Subscription price × seats × 12

Build it

AI build APIs + hosting

Time you would spend

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a minimal self-hosted bookmark manager (stack: Postgres, Node.js/Express API, React frontend, Redis queue, Meilisearch, S3-compatible storage). Core features in scope: user auth, save bookmark API, browser extension endpoint to POST saves, collections and tags, list/search UI (title, URL, tags, full-text via Meilisearch), background worker that fetches and stores an HTML snapshot and extracts text for indexing, import/export of bookmarks (HTML). Out of scope: native mobile/desktop apps, AI assistant, multi-tenant billing. Include error handling, retries for archive fetches, tests for API endpoints and search indexing, and Docker Compose for local dev plus deployment notes for one VPS.
How we checked4 sources · 3/3 runs agreed · evidence score 64

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 4 cited sources+3
  • 3/3 assessment runs agreed+4
  • Evidence score64

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.

How scoring works →

Cited sources · 4

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! Price not confirmed on the page — this pricing page renders its price in the browser✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded