Image and video decision

Kapwing

A single developer can implement a focused Kapwing substitute that handles uploads, ASR transcription, burned-in subtitles, and exports, but replicating Kapwing's full editor, generative features, collaboration, and enterprise tooling is impractical without a team and large infrastructure.

Visit website
Subscription$24/month ✓ verified
Initial build30 hours
Monthly upkeep8 hours + $50
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

  • Upload a video, run automatic speech-to-text, render burned-in subtitles, and export a finished MP4.

What it still won’t have

  • Browser-based drag-and-drop timeline editor and multi-track, frame-level editing
  • Integrated cloud workspace, real-time collaboration and comments
  • Wide suite of generative AI features (video/image generators, B-roll generator, character consistency)
  • Enterprise features: SSO, dedicated account manager, billing & support
  • Large stock asset library, templates, brand kit, and storage quotas at scale

What remains hard

  • Brand trust35M creators use Kapwing
  • Execution qualityKapwing is incredibly intuitive. Many of our marketers were able to get on the platform and use it right away with little to no instruction.
Read the build prompt

First-year cost

Keep paying

Paying ischeaper in year one.

On cash alone, building overtakes the subscription at 3 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-hosted video subtitle-and-export service using: React frontend, Node.js + Express backend, PostgreSQL for projects metadata, AWS S3 for storage, and a small ffmpeg worker (Docker). In scope: signed uploads, server-side ffmpeg transcode to web-friendly format, integration with a 3rd-party ASR API to produce timestamped transcripts, SRT/VTT generation, subtitle burning (ffmpeg overlay) and MP4 export, download links, simple project list UI, authentication (email/password), error handling, and unit/integration tests for upload, ASR integration, and export. Out of scope: WYSIWYG multi-track timeline editor, generative video/image models, collaborative real-time editing, enterprise SSO, and stock asset libraries.
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! 2 moats quoted from the page