Writing and content decision

Novlr

A narrow self-hosted writing workspace (editor, notes, versioning, sync) is feasible for a small technical team to build and maintain, but reproducing Novlr's community/ownership model, polished UX, and paid support/brand benefits is not practical in a short project.

Visit website
Subscription$8/month ✓ verified
Initial build80 hours
Monthly upkeep8 hours + $50
Evidence2/3 runs agree

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • A writer creates and edits projects (manuscripts), saves version history, and uses notes/world-building alongside offline sync and backups.

What it still won’t have

  • Writer-ownership and co-ownership community features
  • Priority customer support and polished UI/UX
  • Lifetime Studio membership perks and exclusive Discord channels
  • Any proprietary proofreading/grammar implementation used by the vendor

What remains hard

  • Brand trustNovlr is the only creative writing platform to be owned by the writers who use it.
Read the build prompt

First-year cost

Keep paying

Paying ischeaper in year one.

On cash alone, building overtakes the subscription at 8 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 self-hosted Novlr-like writing workspace using Next.js (React) + PostgreSQL + Node.js. Implement: user auth (email/password, sessions); project and chapter CRUD; a rich-text editor (TipTap/ProseMirror) with chapter reorder; per-project version snapshots with ability to restore; notes/world-building sidebar linked to projects; offline support (local IndexedDB) and server sync; scheduled backups to Google Drive and Dropbox via their APIs; simple analytics (word counts, streaks); a minimal admin UI. Exclude: payments, writer-ownership/co-op features, and a public community forum. Provide error handling, unit and integration tests for API endpoints, and Docker-based deployment instructions.
How we checked2 sources · 2/3 runs agreed · evidence score 56

How the score was reached

  • Partly verdict base52
  • 2 cited sources+1
  • Price verified on pricing page+3
  • Evidence score56

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

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 quoted from the page