Writing and content decision

Novelcrafter

A small team or capable solo developer can recreate the core Novelcrafter workflow (editor + Codex + planning + BYOK AI) in a few months using existing open-source building blocks; the hosted product's polish, community, and advanced visualizations are the main things you'd forgo.

Visit website
Subscription$4/month ✓ verified
Initial build80 hours
Monthly upkeep8 hours + $20
Evidence3/3 runs agree

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

  • Create and manage novels (manuscript + Codex entries), use AI prompts/chats to generate or revise scenes, plan story structure, and export finished work.

What it still won’t have

  • Polished, production-grade UI/UX and accessibility polish
  • Integrated community, courses, and newsletter ecosystem
  • Built-in live chat/priority support
  • Some advanced review visualizations (appearance heatmap, marker timeline) and planned advanced features

What remains hard

  • Product polish and ongoing maintenance
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 novel-writing web app using Django (backend), PostgreSQL, and React (frontend). Implement: 1) project/book management and a rich-text manuscript editor with revision history; 2) a Codex database for characters/locations with relations and mention-tracking across scenes; 3) planning interfaces (drag-and-drop grid and matrix) to reorder acts/chapters/scenes; 4) AI integration module that accepts a user-provided API key, supports templated prompts, scene-level requests, and displays AI responses; 5) import/export for Word/Markdown/HTML. Out of scope: multi-tenant billing, advanced analytics dashboards, native mobile apps. Include authentication, input validation, error handling, and unit/integration tests for core APIs and critical UI flows.
How we checked5 sources · 3/3 runs agreed · evidence score 67

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
  • 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 · 5

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