Should you build your own Moises?
Run a local stem-separation model and build practice controls for user-owned songs
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Moises, run a local stem-separation model and build practice controls for user-owned songs. The hard boundary is proprietary separation models, mobile polish, chord detection, cloud compute, and speed, plus licensed content, rights, and distribution network.
ENOriginal research content in English. Original prompt preserved in English.
Build a closest honest personal substitute for Moises in an empty repository.
Use Python 3.12, FastAPI, SQLite, ffmpeg, and a local web interface; do not offer alternative stacks.
The core loop is: run a local stem-separation model on legally owned or user-created tracks, then provide private practice controls and playback for each song.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Index only user-selected folders and preserve source audio without modification.
Read tags and artwork, calculate loudness and waveform data, and detect exact duplicates by hash.
Provide albums, artists, playlists, search, queue, favorites, and resumable local playback.
Add optional creator tools for trim, normalize, split stems through a local model, and export new files.
Keep all rights and source information attached to imported tracks and display it during export.
Document that the application does not provide music, licensing, distribution, or royalty collection.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure.
Deliberately leave out copyrighted catalog acquisition or sharing.
Deliberately leave out streaming-service circumvention.
Deliberately leave out royalty accounting, label distribution, and global content delivery.
Finish by running the tests and listing the exact commands used.The prompt opens pre-filled in your agent. Review it before running. · this prompt is generated from the build plan · improve it via PR
What would building your own look like?
Run a local stem-separation model on legally owned or user-created tracks, then provide private practice controls and playback for each song.
What you will need
- legally owned local audio files
- ffmpeg
- local storage
- optional audio-analysis models
People still pay for Moises because the product is the catalog, rights chain, and distribution network; a player or processing tool is only the visible edge. The recurring cost buys catalog licensing, royalties, identity, content delivery, moderation, recommendations, payouts, codecs, and rights disputes, not just the visible interface.
xproprietary separation models, mobile polish, chord detection, cloud compute, and speed
xlicensed music catalog
xroyalty and distribution relationships
xglobal streaming infrastructure
xartist network and recommendations
Prefer something ready-made?
StemDeckLocal six-stem separation plus loops and a mixer; chords and pitch-shifting remain someone else’s problem.Open source↗License, setup, and limitations for each alternative.
How much does Moises cost?
- Monthly billing
- $5.99/mo$5.99/mo · per person
- Per year
- $71.88/yr$71.88/yr
- Annual billing
- $39.96/yr44% cheaper than paying monthly
- On a Brazilian card, with 3.5% IOF
- R$31.30/moR$209/yr
Saved to My list. You will see a notice on this site when the price changes.
You complete the purchase on Moises’s site. Vibe Radar does not handle payments.
| Plan | Monthly | Annual (per month) | What is included |
|---|---|---|---|
| free | $0/user | $0/user | 5 uploads/month; maximum 5 minutes/file; 10 AI Studio credits/month; chords/metronome limited to the first 1 minute. |
| premium | $5.99/user≈ $5.99 | $3.33/user≈ $3.33 | Unlimited uploads under fair use; maximum 20 minutes/file; up to 5 stems; 200 AI Studio credits/month. |
| pro | $29.99/user≈ $29.99 | - | Maximum 180 minutes/file; Pro separation models; unlimited AI Studio credits. |
Free tier5 uploads/month; maximum 5 minutes/file; 10 AI Studio credits/month; chords/metronome limited to the first 1 minute.
Billing termsMonthly + annual where offered; prices vary by storefront and region. The U.S. Apple App Store figures are used where public.
Additional costsFree AI credits expire at the monthly reset; projects processed with paid-only features can become inaccessible after cancellation; app-store taxes and regional pricing can differ.
verified 2026-10-20 · source ↗
Is it cheaper to build or buy Moises?
Adjust the numbers: hours to build, your hourly rate, running costs and the subscription price.
Over 24 months, subscribing is cheaper.
Starting hours estimated from the analysis (closest consolation build: one sitting). Does not price what you give up (support, integrations, security).
Can I rebuild Moises?
Not really. Moises’s value is not the code: Recheck price before merge. See the honest breakdown above.
How much does Moises cost?
Moises costs about $5.99/mo (Premium, checked 10/20/2026), which is $39.96 per year.
What do I lose by replacing Moises?
Honestly: proprietary separation models, mobile polish, chord detection, cloud compute, and speed; licensed music catalog; royalty and distribution relationships; global streaming infrastructure; artist network and recommendations. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Moises?
Yes: StemDeck (Local six-stem separation plus loops and a mixer; chords and pitch-shifting remain someone else’s problem.) The prompt is for when you want it exactly your way.