Audio and podcasting decision
Soundtrap
Build a focused lightweight web DAW yourself for basic recording, arranging, and exports, but keep paying for Soundtrap if you need its large sample library, pro effects, AI vocal tools, and polished collaboration at scale.
Visit website↗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
- A lightweight web DAW: record audio from mic, arrange clips & MIDI on a multitrack timeline, play back mixed output, save/load projects to server, and import a small sample library.
What it still won’t have
- Extensive commercial sample library (40,000+ loops) and biweekly sound pack drops
- Polished, platform-grade desktop app performance and low-latency engine
- Mature real-time collaboration at scale (video/chat inside studio, comments, autosave history)
- Pro effects suite (50+ effects, advanced vocal tuning, AI cleanup) and ongoing content updates
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 10 seats.
Money you would actually spend
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
Build a minimal web DAW using React for the UI, Node.js + Express for the API, PostgreSQL for metadata, S3-compatible object storage for audio blobs, and WebSockets for real-time presence. In scope: browser mic recording (MediaRecorder/WebAudio), multitrack timeline with basic cut/trim, mute/solo, per-track gain/pan, project save/load, stereo export, and a small bundled sample library (hundreds of loops). Out of scope: advanced audio effects/plugins, large commercial sample catalogs, desktop native app, AI-powered vocal tuning, and a marketplace. Include server-side validation, resumable uploads for audio, basic auth, automated tests for API endpoints, and end-to-end tests for recording/playback flows.
How we checked
How the score was reached
- Partly verdict base52
- 2 cited sources+1
- Evidence score53
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.
- official productMusic Makers — Soundtrap
- official docsSoundtrap Features
Integrity checks
What held up, and what did not.
