What we build
Plugins, DSP engines and device firmware: one discipline, from C++23 down to the metal.
- 01Audio Plugin Development
- 02Real-time DSP Engines
- 03Custom Plugin UI
- 04Embedded Firmware
- 05Sensor Integration & Correction
- 06Hard Real-time Systems
- Stack
- C++23JUCEVST3/AU/CLAPFFmpegESP32Raspberry PiSocketCAN
- How we work
- 01
DISCOVER
We define requirements, scope, and technical approach.
- 02
DESIGN
Architecture planning and solution design.
- 03
DEVELOP
Iterative development with regular deliverables.
- 04
DELIVER
Testing, deployment, and ongoing support.
- 01
Clients
Questions
Can we hire a JUCE developer from KRAD Labs?
Yes. The team writes JUCE and C++23 every day, on new VST3, AU, AAX and CLAP plugins or inside an existing codebase. Send the formats, platforms and a short description of the processor or instrument, and you get a reply within one business day.
Which plugin formats do you ship?
VST3, AU, AAX and CLAP from one JUCE codebase, with a custom UI when the stock components don't fit. Standalone builds and code signing for macOS and Windows are part of the delivery.
Can you take over an existing DSP codebase?
Yes. A typical engagement starts with profiling and a written assessment of the current engine, then targeted work on stability, CPU load or new features, without a rewrite unless one is justified.
Do you build hardware firmware as well as plugins?
Yes. Firmware for ESP32 and Raspberry Pi class devices, sensor integration and correction, CAN bus (SocketCAN) and hard real-time loops are part of the same discipline as the DSP work.