Audio and podcasting decision

Call Recorder X+

A competent engineer can deliver a narrower self-hosted replacement (record→transcribe→sync→web UI), but reliable, background iOS call capture across VoIP apps and the polished, compliant product experience are operationally tricky and make a full replacement difficult.

Visit website

Built by hAcx, who ships 3 products in this index

You pay

$2.99/mo

$36/yr

Read off the official pricing page.

You’d pay instead

$100one-off120 h to build

$30/mo4 h/mo upkeep

On cash alone, building overtakes the subscription at 13 seats.

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • Record calls on iOS, transcribe audio to text, and sync recordings to cloud with searchable web UI

What it still won’t have

  • Polished App Store-level UX and installation flow (TrollStore packaging edge cases)
  • Ongoing device-compatibility work across iOS versions and VoIP apps
  • Legal/compliance assurances (HIPAA/SEC/industry certifications) and enterprise support
  • Reliability of low-level call-capture across third-party VoIP apps
  • Brand, reviews and built-in customer support

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 13 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 Call Recorder X+ replacement: create an iOS Swift app packaged for TrollStore that captures VoIP and cellular call audio and saves recordings to local files; implement Google Drive sync using the Google Drive REST API; implement a backend (Node.js + Express) with Postgres to index recordings and transcripts; add a transcription worker that calls a hosted speech-to-text API (e.g., Google Speech or OpenAI) and stores transcripts in Postgres; build a simple React web UI to list recordings, play audio, and view/search transcripts; include biometric locking in the iOS app, setup/install documentation, error handling and unit/integration tests. Out of scope: training custom speech models, App-Store distribution, enterprise compliance certifications, and support for non-iOS platforms.
How we checked2 sources · 3/3 runs agreed · evidence score 60

How the score was reached

  • Partly verdict base52
  • 2 cited sources+1
  • Price verified on pricing page+3
  • 3/3 assessment runs agreed+4
  • 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 · 2

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