Documents and notes decision
Drafts Pro
A capable developer can build a useful Drafts replacement for their own use in about a week, but reproducing Drafts' native platform integrations, App Store presence, curated action directory, and polish is impractical for a solo developer.
Visit website↗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
- Capture short text quickly, store it searchable, organize with tags/flags/archival, and execute actions that send text to other services.
What it still won’t have
- Native iOS/macOS polish and App Store distribution benefits
- Deep platform integrations like Siri, system dictation, and share extensions
- Community Directory of ready-made actions and curated ecosystem
- Mature UX refinements and long-term product polish
What remains hard
- Brand trust
App of the Day | Editor‘s Choice
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 15 seats.
Money you would actually spend
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
Build a minimal Drafts-like web app using React (frontend), Node.js + Express (API), and PostgreSQL (storage). In scope: immediate capture UI that autosaves drafts, basic editor, tag/flag/archive fields, list and search with full-text search, an actions system that lets users configure HTTP webhooks or server-side JS snippets to send a draft to external services, user sign-up/auth (email+password), and a simple REST sync endpoint for another device. Out of scope: native iOS/macOS apps, Siri integration, App Store packaging, and a public community directory. Include input validation, rate-limiting on actions, error handling, and automated tests (unit tests for API and integration tests for capture-to-action flow). Provide Docker compose for local dev and a production deployment script for a single small VPS.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 3 cited sources+3
- 3/3 assessment runs agreed+4
- Evidence score64
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.
- official productDrafts | Where Text Starts
- open sourceusememos/memos
- open sourcelaurent22/joplin
Integrity checks
What held up, and what did not.
