Documents and notes decision

Sofie Wiki

A capable technical user can build the core single-user AI wiki replacement; the vendor adds managed hosting, team/SSO, and compliance features you would forgo.

Visit website

Built by Matteo Ricupero, who ships 4 products in this index

You pay

$4.99/mo

$60/yr

Read off the official pricing page.

You’d pay instead

$100one-off48 h to build

$20/mo6 h/mo upkeep

On cash alone, building overtakes the subscription at 6 seats.

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

What a replacement has to do

  • User chat -> LLM generates/edits markdown wiki pages and cross-links them -> pages indexed for semantic search -> user queries via chat or search to get answers or open pages.

What it still won’t have

  • Hosted AI service (built-in usage limits)
  • SSO and custom domain in team plan
  • SOC 2 / GDPR attestation (listed as ‘soon’)
  • Priority support and managed team features

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 6 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 minimal AI-driven wiki: Stack: Next.js (React) frontend, Node/Express backend, Postgres for pages and revisions, Redis for caching, Milvus or Pinecone for vector storage, OpenAI (or configurable LLM) for embeddings and completions. In-scope features: upload/parse documents, Notion import connector, embed and index text, semantic search API, chat endpoint that generates edits and new markdown pages, automatic simple cross-linking (detect and create links between titles), page view/browse UI with TOC and history, public read-only share links, user account auth (single-user). Out of scope: multi-user permissions/SSO, SOC2 compliance, hosted AI service. Require: error handling, input validation, retries for LLM calls, unit and integration tests for ingestion, search, chat-to-edit flow, and deployment scripts (Docker + basic Helm or Vercel instructions).
How we checked4 sources · 3/3 runs agreed · evidence score 67

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 4 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 · 4

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