Replace Moises?
NOT REALLY · don't botherA 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.
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.
$ open in your agent (prompt prefilled, you press enter) or copy it raw · this prompt is generated from the build plan · improve it via PR
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
What does the Moises verdict mean?
The directory does not recommend replacing this one from a prompt. Recheck price before merge. Read the breakdown above.
What price does this directory record show for Moises?
The directory records $3.99/month for Premium, checked 2026-07-31. Verify the source before making a purchase decision. This reference stays outside retail Stack Math unless current matched evidence supports the comparison.
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?
The listed prior art includes Navidrome (Active open-source personal music server for legally owned libraries.). Inspect those projects before starting from a blank prompt.