Plugins, engines, desktop apps, services, tools.
Most of our work is audio, and none of it is limited to audio. We build plugins in the usual formats, standalone desktop applications, backend services, command line tools, and the internal software that keeps a product line moving.
The constraint we take seriously is the system you already have. New code that ignores your build, your formats, your deployment and your team is a second problem rather than a solution.
VST3, AU, AUv3 and AAX, built on JUCE or on our own engine where that is a better fit. Signed, notarised, and installable on macOS and Windows.
Native desktop apps in C++, Rust, or Swift. Backend services where a product needs accounts, licensing, or telemetry. Web front ends where a browser is the right place for the interface.
The unglamorous software around a product: batch processors, test rigs, listening harnesses, asset pipelines, release automation. This is often where the time is actually going.
Short cycles with something runnable at the end of each one. Code in your repository from the first week, so you can read it as it appears rather than receive it at the end.
You do, unless we agree otherwise in writing. Third-party libraries keep their own licences and we list them.
Yes. We start with a read and a written assessment before touching anything, so you find out what state it is in first.
Mostly C++, Rust, TypeScript, Python and Swift. The choice follows the constraints of the target rather than a preference.