Announcing Monakai Audio Open-Core
Why We Are Doing This
Audio development is hard enough without every team rebuilding the same CMake scripts, MIDI parsers, and knob components from scratch. We have spent years refining the tooling that powers Monakai Audio plugins, and we want to give that work back to the community.
Our open-core model means the infrastructure is shared while the premium DSP, preset banks, synthesis algorithms, and brand assets stay proprietary. You get the scaffolding. We keep the secret sauce.
What Is Available Today
- build-tools — CMake modules, JUCE project templates, cross-platform build configs, and a PowerShell build helper.
- midi-utils — Generic C++ MIDI handlers, CC mapping, and note event processing with no proprietary DSP.
- ui-kit — Style-agnostic JUCE knobs, sliders, meters, and waveform displays with no Monakai branding.
- docs — Build guides, JUCE setup tutorials, CMake troubleshooting flowcharts, and contribution guidelines.
Everything is released under the MIT License.
How to Get Involved
Whether you want to report a build issue, add a new platform config, or contribute a generic UI component, we would love your help. Start with the docs repository for contribution guidelines and code of conduct.
Have a question? Reach out through GitHub Discussions or email info@monakaiaudio.com.
What Is Not Open-Sourced
To be clear: DSP algorithms, premium preset banks, synthesis algorithms, and Kai/Monakai brand assets remain proprietary. The open-core repositories contain only generic tooling and documentation.
Frequently Asked Questions
What is included in Monakai Audio's open-core?
Four MIT-licensed repositories: CMake/JUCE build tools, MIDI utilities, reusable JUCE UI components, and documentation.
Can I use the open-core code in commercial projects?
Yes. The MIT License allows commercial use, modification, and distribution. Attribution is required.
Will Monakai Audio plugins become open source?
No. The plugins themselves — including their DSP, presets, synthesis code, and brand assets — remain proprietary.
How do I contribute?
Fork any repository, make your changes, and open a pull request. See the contribution guidelines for details.