Documents and notes decision

Paperpile

A technically competent developer can build a usable subset (capture, store, Drive sync, basic citation insertion) in a multi-week effort, but matching Paperpile's polish, full integrations, and enterprise features would be costly; consider self-hosting prior-art projects first.

Visit website
Subscription$4.15/month ✓ verified
Initial build80 hours
Monthly upkeep6 hours + $0
Evidence2/3 runs agree

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • Capture reference metadata + PDF from webpages, store and index references, sync/store PDFs in users' Google Drive, insert citations into Google Docs/Word, view/search and annotate PDFs in-browser.

What it still won’t have

  • Enterprise features (SSO, custom SLAs, HIPAA support, vendor security reviews)
  • Polish and cross-platform native apps (iOS/Android/Word/Google Docs official plugins)
  • Large-scale reliability, vendor-managed hosting, and formal support/SLAs
  • Advanced integrations and long tail publisher support

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 3 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 web-based reference manager using: React frontend, a Chrome extension, Node.js + Express backend, Postgres DB, and Elasticsearch (or Postgres full-text). Implement: Google OAuth sign-in; extension that captures metadata and downloads PDFs; backend endpoints to create/update/delete references and store annotation metadata; sync PDFs to the user's Google Drive via Google Drive API and store file IDs; a Google Docs add-on (or Docs API integration) to insert formatted citations and generate bibliographies (supporting at least one citation style); full-text search across metadata and PDF text; an in-browser PDF viewer with highlights saved to the backend. Out of scope: enterprise SSO/SAML, paid billing flows, HIPAA compliance, advanced publisher scraping, and mobile native apps. Include error handling, retry logic for Drive API calls, unit/integration tests for core API endpoints, and a README with deployment steps (Docker + managed Postgres).
How we checked3 sources · 2/3 runs agreed · evidence score 58

How the score was reached

  • Partly verdict base52
  • 3 cited sources+3
  • Price verified on pricing page+3
  • Evidence score58

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 · 3

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ Price read off the page! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded