AI assistants and search decision

Fabric

A single developer can build a narrow, useful subset (searchable personal library, transcription, retrieval+LLM summaries, scheduled agents) over several weeks, but reproducing Fabric's full integration catalogue, Memory Engine, polished UI, and managed reliability is impractical without a team and ongoing ops.

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

$100/mo10 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 Fabric alternatives, with the arithmetic →

What a replacement has to do

  • Index user files and connected app content, run semantic search and summarization over that index, capture/transcribe meetings, provide a minimal UI for search and notes, and run simple scheduled agents that produce outputs into the workspace.

What it still won’t have

  • Fabric Memory Engine (the vendor's proprietary personal-graph and enrichment layer)
  • Polished infinite-canvas UI and multi-format viewer
  • Built-in 50+ third-party integrations catalog and maintained OAuth connectors
  • Prebuilt agent templates, scheduling UX, and multi-user collaboration polish
  • Enterprise-grade encryption/compliance claims and any managed hosting reliability

What remains hard

  • Brand trustTrusted by thinkers, creatives, researchers and students at
Read the build prompt

First-year cost

No published price

Fabric 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 Fabric-like personal AI workspace using Next.js + PostgreSQL + Supabase storage + Pinecone (or Milvus) for vectors and OpenAI embeddings/LLM calls. In scope: OAuth connectors for Google Drive and Gmail (import files and emails), local ingestion pipeline (PDF/docx/text/markdown/images) with text extraction and audio transcription (Whisper or a managed transcription API), embedding generation and a vector index, a retrieval+LLM summarization API, a simple web UI with a unified search box, document viewer, note editor, and a scheduler that runs simple agent jobs and writes outputs to the DB. Out of scope: polished infinite canvas UI, 50+ integrations, enterprise compliance certification, multi-tenant billing. Include error handling for failed connector syncs, retries for API calls, tests for ingestion/extraction, and end-to-end tests for the search->summarize flow.
How we checked4 sources · 2/3 runs agreed · evidence score 60

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 4 cited sources+3
  • Evidence score60

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.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat quoted from the page