Documents and notes decision

Evernote

A useful core replacement (notes + search + basic semantic AI) is realistic for a single experienced engineer to build and run; enterprise features, native apps, and clipper integrations are the harder parts to match.

Visit website
Subscription$14.99/month
Initial build30 hours
Monthly upkeep8 hours + $50
Evidence2/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

  • Create, edit, tag, and search notes; sync notes across devices; run semantic search over your note corpus.

What it still won’t have

  • Enterprise admin, SSO, and detailed user activity logs
  • Official Web Clipper browser extensions and deep browser integration
  • Built-in AI Meeting Notes (recording/transcription) and AI Diagrams
  • Offline-first native apps and polished multi-platform installers
  • PDF editor/converter and advanced document scanning features

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 4 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 Evernote-like web service using Next.js (React + API routes), TypeScript, Postgres (managed), and Prisma. Implement: user auth (email/password), CRUD rich-text notes (TipTap), notebooks/tags, attachments (object storage like S3), REST API endpoints, a sync model for multi-device updates (operation log + conflict resolution), full-text search (Postgres full-text) plus semantic search using OpenAI embeddings and a simple vector index (e.g., pgvector or a hosted vector DB), and a basic web UI for writing, tagging, searching, and viewing notes. Out of scope: browser extensions/web clipper, mobile native apps, enterprise SSO, audio transcription, and PDF editor. Include error handling, input validation, sensible rate limits, unit and integration tests for API routes, and deployment scripts (Docker + managed Postgres).
How we checked5 sources · 2/3 runs agreed · evidence score 86

How the score was reached

  • Build verdict base78
  • An open-source build was found+5
  • 5 cited sources+3
  • Evidence score86

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

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! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded