Can Soundtrap be vibe coded?
Record and arrange a simple multitrack song in a browser and export stems
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Soundtrap, record and arrange a simple multitrack song in a browser and export stems. The hard boundary is realtime collaboration, loops, instruments, education workflow, and hosted rendering, plus licensed content, rights, and distribution network.
Jump to the build brief ↓Checked Jul 2026
What you pay today, before any DIY hosting
medium editorial confidence
Buildability by layer
Screens, forms, and focused interactions
The repeatable job the product performs
Availability and legality of required data
Uptime, queues, support, and maintenance
Security, compliance, and user confidence
The achievable core
- Record and arrange a simple multitrack song in a browser, organize and analyze user-created audio locally, and export stems.
- Build a focused single-user workflow with real persistence, search, and export.
- A responsive interface with real empty, loading, success, and error states.
The parts a prompt cannot buy
- realtime collaboration, loops, instruments, education workflow, and hosted rendering
- licensed music catalog
- royalty and distribution relationships
- global streaming infrastructure
- Licensed content and distribution rights are not reproducible with an LLM.
- Permissions, presence, and shared workflows are difficult to simplify.
Why people still pay
People still pay for Soundtrap 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.
Licensed content and distribution rights are not reproducible with an LLM.
Permissions, presence, and shared workflows are difficult to simplify.
The brief
Context, requirements, acceptance criteria, non-goals, and the full production standard — as Markdown, ready for any coding agent.
Build brief — a focused alternative to Soundtrap
Context
**Soundtrap** — Record and arrange a simple multitrack song in a browser and export stems. It currently costs $13.99/mo.
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Soundtrap, record and arrange a simple multitrack song in a browser and export stems. The hard boundary is realtime collaboration, loops, instruments, education workflow, and hosted rendering, plus licensed content, rights, and distribution network.
This brief describes a focused, single-operator replacement for the part of Soundtrap that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.
What you are building
Record and arrange a simple multitrack song in a browser, organize and analyze user-created audio locally, and export stems.
Build a focused single-user workflow with real persistence, search, and export.
A responsive interface with real empty, loading, success, and error states.
Requirements
Functional
Legally owned local audio files.
Ffmpeg.
Local storage.
Optional audio-analysis models.
Non-functional
Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
Security: server-side secrets, validated input, and no credentials in the client bundle.
Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
Portability: the operator can export their data and leave without losing it.
Implementation brief
Build a personal replacement for Soundtrap 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: record and arrange a simple multitrack song in a browser, organize and analyze user-created audio locally, and export stems.
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.
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.
Delivery standard
Inspect the repository first, then write a short implementation plan before writing code.
Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
Add structured logs around every external call and return actionable errors without leaking sensitive details.
Write unit tests for the core logic and one automated test of the main user journey.
Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.
Acceptance criteria
A clean install starts the app using only the README and .env.example.
The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
Tests, type checking, linting, and a production build all pass with no ignored failures.
No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.
Non-goals
Do not build these, and do not claim to have replaced them:
Realtime collaboration, loops, instruments, education workflow, and hosted rendering.
Licensed music catalog.
Royalty and distribution relationships.
Global streaming infrastructure.
Licensed content and distribution rights are not reproducible with an LLM.
Permissions, presence, and shared workflows are difficult to simplify.
What you still own after launch
Run migrations, backups, restores, and dependency updates.
Test the critical journey after every model, API, or hosting change.
Monitor failures and fix the edge cases a first prompt will miss.
Risk
**Manageable.** A personal version is realistic if you test the critical journey and keep reliable backups.
Editorial confidence in this assessment: medium. No independent one-shot implementation is linked yet.
Prior art
Working open-source software you can read, fork, or borrow from before starting:
[Navidrome](https://github.com/navidrome/navidrome) — Active open-source personal music server for legally owned libraries
Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/soundtrap
You still own the product
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
Open-source prior art
Before you start
Can Soundtrap be vibe coded?
Partly, if you narrow it. The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Soundtrap, record and arrange a simple multitrack song in a browser and export stems. The hard boundary is realtime collaboration, loops, instruments, education workflow, and hosted rendering, plus licensed content, rights, and distribution network.
What can an AI coding agent reproduce from Soundtrap?
Record and arrange a simple multitrack song in a browser, organize and analyze user-created audio locally, and export stems. Build a focused single-user workflow with real persistence, search, and export. A responsive interface with real empty, loading, success, and error states.
What will a DIY Soundtrap replacement still be missing?
realtime collaboration, loops, instruments, education workflow, and hosted rendering; licensed music catalog; royalty and distribution relationships; global streaming infrastructure; Licensed content and distribution rights are not reproducible with an LLM.; Permissions, presence, and shared workflows are difficult to simplify.
What do I still own after building a Soundtrap alternative?
Run migrations, backups, restores, and dependency updates. Test the critical journey after every model, API, or hosting change. Monitor failures and fix the edge cases a first prompt will miss.