Image and video decision

VidNotes

VidNotes is open-source and self-hostable (repo available), so a technical user can stand up a useful replacement by running the upstream project or implementing a minimal stack; keep paying only for convenience and hosted integrations.

Visit website
Subscription$4.17/month ✓ verified
Initial build6 hours
Monthly upkeep8 hours + $20
Evidence2/2 runs agree

What a replacement has to do

  • Given a video URL or file, download/extract audio, run speech-to-text, generate timestamped transcript, run an LLM to produce summaries/key points/flashcards, and expose results via a simple web UI and API.

What it still won’t have

  • Official iOS / Android apps and App Store / Play Store distribution
  • Chrome extension and browser integration shipped by VidNotes
  • Polished UX, analytics, and priority support
  • Built-in MCP/Claude/Codex integrations and one-account-scoped managed API key system
  • Any proprietary operational scaling, monitoring, and background-job infrastructure provided by VidNotes

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 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 self-hostable VidNotes-like service using Node.js (Express) backend, React frontend, Postgres, Redis for job queue, Docker, and GitHub Actions for CI. In scope: accept a public video URL (YouTube), download/extract audio, transcribe audio with OpenAI Whisper (or local Whisper backend), generate summaries/flashcards/QA with an LLM (OpenAI/GPT-compatible), store transcripts and derived artifacts in Postgres, provide REST endpoints /v1/analyze and /v1/transcripts/:id, a minimal React UI to paste a URL and view transcript with timestamps, and a small CLI that calls the API and outputs JSON. Explicitly out of scope: mobile apps, Chrome extension, MCP server, multi-account billing, and rendered clips/thumbails. Include proper error handling (network/timeouts/transcode failures), background job retries, basic auth for the API (API key), Docker compose and deployment instructions, and automated tests for transcription, summary generation, and key endpoints.
How we checked4 sources · 2/2 runs agreed · evidence score 99

How the score was reached

  • Self-host verdict base92
  • An open-source build was found+5
  • 4 cited sources+3
  • Price verified on pricing page+3
  • 2/2 assessment runs agreed+4
  • Evidence score99

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✓ 2 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded