Audio and podcasting decision

Voxdub

A capable technical user can build a useful, narrower replacement covering timeline editing, recording, STT, and exports, but reproducing Voxdub's polish, studio-grade export QA, proprietary voice models, and mature collaboration at scale would be difficult without more time or team resources.

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-off104 h to build

$50/mo6 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 Voxdub alternatives, with the arithmetic →

What a replacement has to do

  • Load a video -> generate or import subtitles -> create and edit a high-frequency timeline ('bande rythmo') -> record and overdub audio with real-time monitoring -> export studio-ready audio/video and subtitle files.

What it still won’t have

  • Polish and UX refinements (proprietary UI interactions and keyboard workflow)
  • Proprietary integrations and studio export compatibility QA across DAWs
  • Mature collaboration features and scale-tested concurrent editing
  • Any proprietary voice‑model 'maquette de voix avec IA' optimised by vendor
  • Commercial support, SLAs, and ongoing product improvements

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Voxdub 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 browser-first dubbing web app (React + Typescript front-end, Node.js + Express backend, Postgres for projects, AWS S3 for storage). Core features in scope: high-frequency timeline renderer (canvas or WebGL) with frame-accurate scrubbing; in-browser audio recording with low-latency monitoring and simple denoise; subtitle/STT ingestion (use Whisper or similar via an external API) with alignment and export to SRT/ASS/DETX; video/audio import and client-side conversion tools (ffmpeg-wasm); project CRUD, cloud storage, and batch export to BWF/MP4; simple collaboration (project sharing, presence, role-based access). Out of scope: training custom voice models, advanced DAW integrations, enterprise SSO, mobile native apps beyond responsive web UI. Include error handling, input validation, unit and integration tests for recording, STT, export, and storage flows, and a README with deployment steps (Docker + Terraform for infra).
How we checked5 sources · 3/3 runs agreed · evidence score 64

How the score was reached

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

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.

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