Vibecode Raindrop.io
track this build5 steps, step by step0%YES · one-shottable
A personal bookmark saver with tags, full-text search, and screenshots is a very tractable small app.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Raindrop.io. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Raindrop.io indie build ## Goal Build the smallest trustworthy replacement for the core Raindrop.io workflow for one developer or a tiny team. ## Scope Build a browser extension/bookmarklet, save URL metadata to SQLite/Postgres, tag it, optionally archive page text, and provide search. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - mobile apps - browser-extension polish - permanent archiving - visual previews - team collections - import/export polish If those capabilities are essential, use linkwarden instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build me a personal bookmark manager to replace Raindrop.io. Requirements: - A local web app: Node + Express + better-sqlite3 on localhost:4040, server-rendered, minimal JS. - Save via a bookmarklet that POSTs the current URL to /save; the server fetches the page, pulls title/description/og:image with metascraper, and stores the readable article text (@mozilla/readability) for search. - Bookmarks take free-form tags (comma entry, autocomplete from existing tags) and an optional note. - Full-text search across title, note, and archived page text with SQLite FTS5; filter by tag, newest first. - List view: favicon, title, domain, tags, saved date. A weekly node-cron job re-checks links and flags 404s. - Import from a Netscape bookmarks HTML export; export everything as JSON and CSV from an /export route. - Binds to localhost only; no accounts, no telemetry, the whole archive is one SQLite file I can back up. - Out of scope: mobile apps and full page-snapshot archiving, the stored text is the archive. No team collections. - README: how to install the bookmarklet and where the DB file lives. ## Required capabilities - browser extension or bookmarklet - small hosted backend or local database - page metadata/extraction library ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of Raindrop.io. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Raindrop.io indie build ## Goal Build the smallest trustworthy replacement for the core Raindrop.io workflow for one developer or a tiny team. ## Scope Build a browser extension/bookmarklet, save URL metadata to SQLite/Postgres, tag it, optionally archive page text, and provide search. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - mobile apps - browser-extension polish - permanent archiving - visual previews - team collections - import/export polish If those capabilities are essential, use linkwarden instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build me a personal bookmark manager to replace Raindrop.io. Requirements: - A local web app: Node + Express + better-sqlite3 on localhost:4040, server-rendered, minimal JS. - Save via a bookmarklet that POSTs the current URL to /save; the server fetches the page, pulls title/description/og:image with metascraper, and stores the readable article text (@mozilla/readability) for search. - Bookmarks take free-form tags (comma entry, autocomplete from existing tags) and an optional note. - Full-text search across title, note, and archived page text with SQLite FTS5; filter by tag, newest first. - List view: favicon, title, domain, tags, saved date. A weekly node-cron job re-checks links and flags 404s. - Import from a Netscape bookmarks HTML export; export everything as JSON and CSV from an /export route. - Binds to localhost only; no accounts, no telemetry, the whole archive is one SQLite file I can back up. - Out of scope: mobile apps and full page-snapshot archiving, the stored text is the archive. No team collections. - README: how to install the bookmarklet and where the DB file lives. ## Required capabilities - browser extension or bookmarklet - small hosted backend or local database - page metadata/extraction library ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of Raindrop.io. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # Raindrop.io product brief ## Problem A personal bookmark saver with tags, full-text search, and screenshots is a very tractable small app. ## Product outcome Build a browser extension/bookmarklet, save URL metadata to SQLite/Postgres, tag it, optionally archive page text, and provide search. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - browser extension or bookmarklet - small hosted backend or local database - page metadata/extraction library ## Explicit non-goals for v1 - mobile apps - browser-extension polish - permanent archiving - visual previews - team collections - import/export polish ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief Build me a personal bookmark manager to replace Raindrop.io. Requirements: - A local web app: Node + Express + better-sqlite3 on localhost:4040, server-rendered, minimal JS. - Save via a bookmarklet that POSTs the current URL to /save; the server fetches the page, pulls title/description/og:image with metascraper, and stores the readable article text (@mozilla/readability) for search. - Bookmarks take free-form tags (comma entry, autocomplete from existing tags) and an optional note. - Full-text search across title, note, and archived page text with SQLite FTS5; filter by tag, newest first. - List view: favicon, title, domain, tags, saved date. A weekly node-cron job re-checks links and flags 404s. - Import from a Netscape bookmarks HTML export; export everything as JSON and CSV from an /export route. - Binds to localhost only; no accounts, no telemetry, the whole archive is one SQLite file I can back up. - Out of scope: mobile apps and full page-snapshot archiving, the stored text is the archive. No team collections. - README: how to install the bookmarklet and where the DB file lives. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Raindrop.io capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Raindrop.io indie build ## Goal Build the smallest trustworthy replacement for the core Raindrop.io workflow for one developer or a tiny team. ## Scope Build a browser extension/bookmarklet, save URL metadata to SQLite/Postgres, tag it, optionally archive page text, and provide search. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - mobile apps - browser-extension polish - permanent archiving - visual previews - team collections - import/export polish If those capabilities are essential, use linkwarden instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief Build me a personal bookmark manager to replace Raindrop.io. Requirements: - A local web app: Node + Express + better-sqlite3 on localhost:4040, server-rendered, minimal JS. - Save via a bookmarklet that POSTs the current URL to /save; the server fetches the page, pulls title/description/og:image with metascraper, and stores the readable article text (@mozilla/readability) for search. - Bookmarks take free-form tags (comma entry, autocomplete from existing tags) and an optional note. - Full-text search across title, note, and archived page text with SQLite FTS5; filter by tag, newest first. - List view: favicon, title, domain, tags, saved date. A weekly node-cron job re-checks links and flags 404s. - Import from a Netscape bookmarks HTML export; export everything as JSON and CSV from an /export route. - Binds to localhost only; no accounts, no telemetry, the whole archive is one SQLite file I can back up. - Out of scope: mobile apps and full page-snapshot archiving, the stored text is the archive. No team collections. - README: how to install the bookmarklet and where the DB file lives. ## Required capabilities - browser extension or bookmarklet - small hosted backend or local database - page metadata/extraction library ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# Raindrop.io product brief ## Problem A personal bookmark saver with tags, full-text search, and screenshots is a very tractable small app. ## Product outcome Build a browser extension/bookmarklet, save URL metadata to SQLite/Postgres, tag it, optionally archive page text, and provide search. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - browser extension or bookmarklet - small hosted backend or local database - page metadata/extraction library ## Explicit non-goals for v1 - mobile apps - browser-extension polish - permanent archiving - visual previews - team collections - import/export polish ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief Build me a personal bookmark manager to replace Raindrop.io. Requirements: - A local web app: Node + Express + better-sqlite3 on localhost:4040, server-rendered, minimal JS. - Save via a bookmarklet that POSTs the current URL to /save; the server fetches the page, pulls title/description/og:image with metascraper, and stores the readable article text (@mozilla/readability) for search. - Bookmarks take free-form tags (comma entry, autocomplete from existing tags) and an optional note. - Full-text search across title, note, and archived page text with SQLite FTS5; filter by tag, newest first. - List view: favicon, title, domain, tags, saved date. A weekly node-cron job re-checks links and flags 404s. - Import from a Netscape bookmarks HTML export; export everything as JSON and CSV from an /export route. - Binds to localhost only; no accounts, no telemetry, the whole archive is one SQLite file I can back up. - Out of scope: mobile apps and full page-snapshot archiving, the stored text is the archive. No team collections. - README: how to install the bookmarklet and where the DB file lives. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Raindrop.io capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent · this prompt is generated from the build plan · improve it via PR
They pay because bookmarks are boring until import/export, search, mobile, and extension reliability matter.
xmobile apps
xbrowser-extension polish
xpermanent archiving
xvisual previews
xteam collections
ximport/export polish
share on X ↗"I just replaced Raindrop.io ($3/mo) with one prompt"
Don't feel like building it? These folks already made it free.
KarakeepA bookmark junk drawer that labels itself and keeps the contents.open source↗
LinkwardenRaindrop with a filing cabinet and a copy of every page.open source↗
linkdingPinboard with a nicer face and no annual invoice.open source↗all 4 free alternatives to Raindrop.io →· no votes, no pay-to-list · just what's real
Raindrop.io pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| free | $0 | $0 | Unlimited bookmarks, collections, highlights, devices and collaborators; 100 MB file uploads/month |
| pro | $3 | $2.30 | Unlimited bookmarks; 10 GB file uploads/month; full-text search, permanent archive, AI assistant, reminders and daily backups |
free tierUnlimited bookmarks, collections, highlights, devices and collaborators; 100 MB file uploads/month
billingmonthly + annual (yearly usually about 20% cheaper); Paddle billing; 30-day money-back guarantee
hidden costsVAT may be added. Failed payments can be retried up to 4 times in the next week before downgrade to Free.
verified 2026-08-13 · source ↗
Vibecode Raindrop.io
Yes. A competent AI coding agent (Claude Code, Codex, Cursor) can build a usable personal Raindrop.io replacement in one session with the prompt on this page. It runs on your own machine or server with no subscription.
How much does Raindrop.io cost?
Raindrop.io costs about $3/month (Pro, checked 2026-07-30), which is $36 per year. That's what you save by replacing it with one prompt.
What do I lose by replacing Raindrop.io?
Honestly: mobile apps; browser-extension polish; permanent archiving; visual previews; team collections; import/export polish. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Raindrop.io?
Yes: Karakeep (A bookmark junk drawer that labels itself and keeps the contents.) Linkwarden (Raindrop with a filing cabinet and a copy of every page.) linkding (Pinboard with a nicer face and no annual invoice.) All 4 curated free alternatives are at vibecodeit.com/raindrop-io/alternatives. The prompt is for when you want it exactly your way.