1. Start in the live studio
Create music only through a configured provider. Lyrics, uploads, voices, Studio, Library, and Pricing each open their real workstation view.
OpenUSAGE GUIDE
How the BYOK music workstation works, and what you connect to it.
You buy a licence for the workstation software and run it on your own computer. Songs render locally through the included engine, so nothing you make is queued behind our servers. This site is the storefront and your licence account; generation happens on your machine.
Where it runsRuns on your PC
LicenseUSD 99
ExportsWAV / MP3 / STEMS
2. Create a complete song
Enter a prompt, choose language, genre, mood, BPM, key, duration, and vocal type, then generate through a configured provider.
Open3. Write or polish lyrics
Draft lyrics locally or connect your own lyric API. The software does not bundle model usage.
Open4. Split audio into stems
Confirm rights, upload MP3/WAV, analyze BPM and key, then split vocals, instrumental, drums, bass, and other.
Open5. Use an authorized voice
Upload authorized samples only. Voice training and conversion require a configured RVC or compatible provider.
Open6. Mix and export in Studio
Inspect waveforms, preview the mix, mute or solo stems, adjust volume, and export WAV or STEMS ZIP.
Open7. Buy the licence
USD 99, one time. Songs render locally at no per-track cost; only an optional lyrics API uses a key of your own, and its free tier covers normal use.
Open8. Keep work in the Library
Replay songs, send assets to Studio, download files, and keep songs, stems, voices, exports, and QA records visible.
Open9. Check live engine readiness
Use the main workspace provider panel to see which song engines and supporting services are genuinely configured. Blocked services stay blocked; the site never simulates results.
OpenAPI SETUP
Customers bring their own keys.
Add provider keys
Set API keys or local command paths in environment variables. Never paste production secrets into the browser UI.
Set API keys or local command paths in environment variables. Never paste production secrets into the browser UI.
Choose the song engine
Connect ACE-Step, MusicGen, Mureka, ElevenLabs Music, Google Lyria, or another compatible backend.
Connect ACE-Step, MusicGen, Mureka, ElevenLabs Music, Google Lyria, or another compatible backend.
What the APIs cost you
Songs render locally and cost nothing per track. Lyrics are optional and use your own key — the free tiers of GitHub Models, Gemini or Groq are enough for normal use. If you pick a paid music API instead of the local engine, that provider bills you directly.
Songs render locally and cost nothing per track. Lyrics are optional and use your own key — the free tiers of GitHub Models, Gemini or Groq are enough for normal use. If you pick a paid music API instead of the local engine, that provider bills you directly.
Configure four-leg auth
Configure GitHub OAuth, Google OAuth, email-code login, and email-plus-password registration.
Configure GitHub OAuth, Google OAuth, email-code login, and email-plus-password registration.
Your licence activates automatically
Once your payment clears, the licence is applied to your account automatically. No manual step, no waiting on support.
Once your payment clears, the licence is applied to your account automatically. No manual step, no waiting on support.
BEFORE YOU START
What you need on your own machine.
Landing page: /landing with EN / 中文 / UA switch
Pricing: BYOK entry and /pricing show the USD 99 software license
About 15 GB of free disk space for the song engine and its model weights
Real audio requires a configured engine; the app must never fake a completed song
An optional lyrics API key of your own (GitHub Models, Gemini, Groq or OpenRouter all work on their free tiers)
A Windows or Linux machine with an NVIDIA GPU (8 GB VRAM or more) for local song rendering; CPU-only works for lyrics and stems but is too slow for full songs