Audio and podcasting decision

Neume

A competent developer can reproduce a useful subset (generate songs from prompt, synthesize vocals, mix and store files) using existing APIs and open tools, but matching Neume's end-to-end polish, mobile apps, low-latency guarantees, integrated video features, and any proprietary model quality would be difficult to fully replicate.

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-off140 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 Neume alternatives, with the arithmetic →

What a replacement has to do

  • User enters a text prompt -> backend composes melody & arrangement -> synthesize vocals -> mixdown + produce final audio file -> store and serve song to user (download/share) with an option to remix a selected section

What it still won’t have

  • Proprietary trained end-to-end model optimised for full song generation and quality polish
  • Mobile apps and cross-device syncing (iOS/Android clients)
  • Integrated AI video editor / lip-synced music-video exports
  • Priority support and product UX polish (fast iteration, low-latency <3min guarantee)
  • Any proprietary voices or commercial-grade voice models bundled by Neume

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Neume 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 web service (Next.js + Node/Express backend, Postgres, AWS S3, Redis job queue) that accepts a song prompt and optional lyrics and returns a downloadable mixed audio track. Integrate: (1) an LLM API for lyric generation, (2) a music/arrangement API or open music model to produce instrument stems (or MIDI), and (3) a vocal synthesis API/model (e.g., open-source TTS/voice models or hosted vocal-synthesis APIs). Core features in scope: prompt UI, job queue, orchestration to call the three model APIs, basic audio mixing pipeline to combine stems and vocals into mp3/wav, persistent storage of assets, user library with ability to select a time range and re-synthesize (remix) only that segment, and a download/share endpoint. Out of scope: native iOS/Android clients, full-featured AI video editor, proprietary voice training. Require error handling, retries for API failures, background job monitoring, and unit/integration tests for API flows.
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