Documents and notes decision

Grape

A technical user can reproduce the core local note-taking, transcription and semantic-search + LLM query features using existing OSS pieces (Joplin/memos and API services), but reproducing Grape's bundled cross-device AI experience, polished multi-platform UX and included AI keys is non-trivial—so building a minimal replacement is realistic, a full parity product is not.

Visit website

Built by Ozgur Ozer, who ships 12 products in this index

You pay

$19/mo

$228/yr

Read off the official pricing page.

You’d pay instead

$100one-off72 h to build

$20/mo6 h/mo upkeep

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

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. All Grape alternatives, with the arithmetic →

What a replacement has to do

  • Write or record notes -> index them with embeddings -> semantic search and ask an LLM over your local notes -> show summaries, flashcards, and simple tidying actions (tagging, moving).

What it still won’t have

  • Bundled "Grape AI included" across devices (you must supply API keys and pay for LLM/transcription usage)
  • Polished cross-device sync implementation and priority support
  • Refined, polished desktop+mobile UX and QA that a paid app provides

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 2 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 local-first cross-platform note app using Electron + React for desktop (and React Native or Capacitor for mobile optionally), SQLite for local storage, and a small local vector index (SQLite + FAISS/annoy) for embeddings. Core features in scope: rich-text markdown editor, create/read/update/delete notes, attach audio files and run transcription via OpenAI Whisper API, generate embeddings (OpenAI embeddings) and implement semantic search, implement an "AI agent" endpoint that composes relevant note context and calls an LLM (OpenAI GPT) to produce summaries, checklists and simple tag/move actions, and export/import notes as Markdown. Out of scope: a proprietary bundled LLM key, a production-grade multi-user sync server, and advanced mobile polishing. Require: error handling for network/IO failures, unit tests for storage/indexing/agent flows, and a README with setup and instructions to run locally.
How we checked5 sources · 2/3 runs agreed · evidence score 63

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 5 cited sources+3
  • Price verified on pricing page+3
  • Evidence score63

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