Apps built onengines we wrote.
Native audio instruments, private networking, AI tooling and interactive installations — a growing family of software under one star.
- 10
- apps and instruments
- 4
- product lines
- 9
- platforms and formats
- 1
- shared audio core
Apps and instruments
Everything we ship, and everything we are still building.
We write the engine first
Products are the visible part. What makes them possible is underneath.
One audio core
A native JUCE/C++ engine with a lock-free control→audio queue sits under every audio product we make. Fix it once, and every instrument gets the fix.
Latency is the spec
We left the browser because 25 ms of latency and a garbage collector are not acceptable in an instrument. Every decision after that follows from the same rule.
Built, not assembled
Stem separation, AI-music detection, projection-immune tracking — the hard parts are ours, so they run locally and nothing has to leave your machine.
One tree, both desktops
macOS and Windows builds come out of the same source tree, so a feature does not arrive on one platform a season before the other.
Every platform we ship to
iOS & Android
1VST3 & AU
1Browser
2Engines & CLI
2
More is on the way
The catalogue grows as the engine does. Tell us what you are building with — it tends to end up on the roadmap.