Audio and podcasting decision

VoiceType.com

If you only need in-browser dictation, a single developer can build and maintain a useful replacement; replicating VoiceType's claimed system-wide, polished native integration and product experience is harder and likely worth paying for unless you use an open-source MacOS tool like mow.

Visit website
Subscription$19.5/month ✓ verified
Initial build30 hours
Monthly upkeep4 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

  • Capture microphone audio, transcribe to text, auto-format/clean text, insert typed text into user's active input, store user preferences and transcripts.

What it still won’t have

  • System-wide, OS-level keyboard replacement / global hotkey for all native apps
  • Any proprietary backend optimizations or tuning specific to VoiceType (not documented)
  • Polished product UX, analytics, growth/marketing the vendor provides

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 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 narrowly scoped VoiceType replacement: a Chrome/Firefox extension + lightweight Node.js backend. Stack: extension (TypeScript), backend (Node.js + Express), PostgreSQL for user settings, Redis for realtime sessions. In-scope features: microphone capture in-extension, stream audio to backend, use OpenAI/Whisper-style STT for transcripts, basic filler-word removal and auto-formatting rules, ability to paste/transmit text into focused page input via content script, user signup/login, settings (language, tone), transcript history. Out of scope: native OS-wide keyboard injection helper for non-browser apps, multi-language model training, mobile apps, paid billing integration. Include error handling for audio permissions and network failures, unit tests for backend logic, and end-to-end tests for the extension content-script paste flow.
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