Learning and careers decision

Speak Silq

A technically competent developer can build a useful, self-hosted practice tool (record/transcribe/review) using open-source players and ASR, but reproducing curated content, polished mobile experience, and full commercial product features would be substantial work—keep paying if you need the complete product.

Visit website
SubscriptionCustom pricing
Initial build80 hours
Monthly upkeep4 hours + $50
Evidence2/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. All Speak Silq alternatives, with the arithmetic →

What a replacement has to do

  • Record spoken practice → automatic transcription/feedback → store example phrases and scores → replay native audio and review with spaced repetition.

What it still won’t have

  • Proprietary lesson content and curated curricula
  • Polished mobile apps and design polish
  • Any paid community, marketplace, or instructor network
  • Turnkey analytics, onboarding, and commercial support

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Speak Silq 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 minimal self-hosted Silq-like web app using Next.js (React) frontend, Node.js/Express backend, Postgres DB, and deploy on Vercel (frontend) + a small VPS (backend) or Render. Integrate Whisper or a cloud ASR for transcription and an off-the-shelf TTS for playback. Core features in scope: user signup, lesson list, client-side audio recording and upload, transcription and simple pronunciation scoring, store phrases and SRS review queue, play native audio or TTS, basic analytics (per-user review history). Out of scope: instructor marketplace, paid subscriptions, multi-tenant enterprise features, advanced curriculum authoring. Include error handling, input validation, unit tests for backend endpoints, and end-to-end tests for the review flow.
How we checked3 sources · 2/3 runs agreed · evidence score 60

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 3 cited sources+3
  • 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 · 3

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded