Writing and content decision

Scrivener

A competent developer can build a useful, smaller Scrivener replacement for personal use (editor + binder + export) but reproducing the full, polished multi-platform product and advanced compile/export features is time-consuming and not realistic as a one-person short project.

Visit website
You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off80 h to build

$0/mo8 h/mo upkeep

No published price to break even against.

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 Scrivener alternatives, with the arithmetic →

What a replacement has to do

  • Create and organize long-form writing projects (documents in a project binder), edit text, save versions, and export/compile into common formats

What it still won’t have

  • Platform polish and extensive UX refinements
  • Mature compile/export presets and formatting controls
  • Official multi-platform native apps and installers
  • Brand recognition, community resources, and paid support
  • Advanced project templates, corkboard/scapple-style visual tools

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Scrivener does not publish a price we could read, so there is nothing to compare against. What building costs is below.

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 minimal Scrivener-like web app using React (frontend), TipTap (rich-text), Node.js + Express (API), and SQLite (project files). Implement: 1) project binder UI with create/read/update/delete for nested documents, 2) a document editor with formatting and document-level metadata, 3) search across project text, 4) per-document snapshots and undo, 5) export endpoints for plain text, PDF, and RTF, 6) project file export/import as a single ZIP containing SQLite/JSON and assets. Out of scope: real-time collaboration, native desktop installers, advanced compile presets, and a visual corkboard. Include error handling, input validation, and automated tests covering API routes and editor-save flows.
How we checked2 sources · 3/3 runs agreed · evidence score 62

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 2 cited sources+1
  • 3/3 assessment runs agreed+4
  • Evidence score62

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.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded