Documents and notes decision
Anytype
A capable developer can build a useful self-hosted collaborative notes app that replaces core workflows, but reproducing the full commercial product (polish, native apps, support, and any vendor services) would be larger and likely multi-week work.
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. All Anytype alternatives, with the arithmetic →
What a replacement has to do
- Create and collaboratively edit structured notes/records and store them in a shared database with real-time sync
What it still won’t have
- Polished cross-platform native apps and installers
- Proprietary UI/UX polish and continuous product polish
- Commercial-grade support and SLAs
- Any closed-source integrations or proprietary services the vendor may provide
- Brand trust and aggregated user-base features
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 5 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 self-hosted collaborative notes web app using React for the frontend, Node.js + Express for the backend, and Postgres for storage. Scope: user signup/login, create/edit/delete rich-text or markdown notes, per-note sharing/permissions, real-time collaborative editing via WebSockets, server-side search using Postgres full-text, and a Docker-based deployment (single VPS). Out of scope: native mobile apps, AI features, enterprise SSO, and third-party paid integrations. Include input validation, authentication error handling, optimistic-concurrency handling for edits, basic automated tests (unit and API integration), and a README with deployment steps and a backup/restore procedure.
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 productAnytype — official product page
- open sourceether/etherpad
- open sourcezmister2016/MrDoc
Integrity checks
What held up, and what did not.
