Documents and notes decision

Melo

A capable developer can build the core capture + semantic search + chat workflow reasonably (using existing open-source note apps and hosted embedding/LLM APIs), but reproducing Melo’s macOS-native polish, gesture features, and packaged integrations/UX would be costly to match.

Visit website

Built by Hamza, who ships 3 products in this index

You pay

$4.99/mo

$60/yr

Read off the official pricing page.

You’d pay instead

$100one-off120 h to build

$20/mo6 h/mo upkeep

On cash alone, building overtakes the subscription at 6 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 Melo alternatives, with the arithmetic →

What a replacement has to do

  • Capture a thought (hotkey or clipper) → store locally → index text with embeddings → semantic search / chat over saved items to recall with source links.

What it still won’t have

  • macOS native polish and OS-level window tiling/gesture integration (hand-tracking, clap-to-summon)
  • desktop pets, themes & fonts variety and other UI polish
  • prebuilt integrations and the vendor’s bundled lifetime license experience
  • offline local model hosting and any proprietary model optimizations

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 6 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 Mac-focused local-first note workspace as an Electron (or Tauri) app with a React UI, SQLite for local storage, and a small vector index using FAISS or an SQLite extension. Core features in scope: global hotkey quick-capture, local note/file storage with metadata, web clipper (browser extension or clip API), embedding pipeline using OpenAI embeddings, vector search for semantic recall, a chat UI that retrieves top-k contexts and sends them to OpenAI/another LLM, and an integrations module that can pull Notion pages and Calendar events read-only. Out of scope: advanced gesture/hand-tracking, desktop pets, multi-user sync, and training proprietary models. Include error handling, retry/backoff for API calls, background worker for indexing, unit and integration tests for capture, indexing, and search workflows, and startup/run documentation.
How we checked4 sources · 3/3 runs agreed · evidence score 67

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 4 cited sources+3
  • Price verified on pricing page+3
  • 3/3 assessment runs agreed+4
  • Evidence score67

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 read off the page✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded