The stuff every DJ, producer, and studio owner asks before reaching out.
Do I own the code when it's done?
Yes. At handover you get the full source code, not a license to use our platform. Built on standard web technologies (Web Audio API, Tone.js, plain JavaScript) — no proprietary lock-in.
What tech do you actually build with?
Mostly the Web Audio API and Tone.js, often bundled into a single self-contained HTML file so there's nothing to install or host separately. For heavier builds we'll discuss the right stack for your needs.
Does it need to be installed, or does it run in a browser?
Browser-based by default — open it and it works, on desktop or mobile, with no install step. If your project genuinely needs a native app or VST plugin, we'll flag that upfront rather than force-fit a browser build.
Can it handle live performance, not just studio use?
Yes — latency and buffer stability get engineered and tested specifically for live conditions, not just a clean demo. If a feature needs to work under real performance pressure, we test it under that pressure.
Can you integrate MIDI controllers or existing hardware?
Depends on the hardware and browser support (Web MIDI API), but in most cases yes. Tell us your controller setup during the brief and we'll confirm what's possible before quoting.
I already have a rough version built — can you take it from there?
Often, yes. We'll review what exists, tell you honestly whether it's worth building on or rebuilding clean, and quote accordingly — no obligation either way.
Do you offer payment plans?
Yes. Standard split is 50% upfront, 50% on delivery. Build work starts once the deposit clears. Larger builds can be split into three or four milestone payments. Direct EFT only — no card surcharges.
What happens after launch — is there support?
14 days of free post-launch support ships with every build — bug fixes, small tweaks, and questions. After that, the Care & Updates retainer covers ongoing changes, or you can pay hourly as needed.