Puke Highlights
Puke is an open-source programming language for creating audio effects, synthesis, and more. Patch node-based components together then puke that code onto standalone hardware.Proudly Open Source
Build in the open with a transparent codebase and a community-driven roadmap.
Node-Based Workflow
Create audio logic by connecting nodes instead of writing line-by-line code.
Real-Time Audio Processing
Design effects that respond instantly and behave like real instruments.
Custom Effects Chains
Build your own distortion, delay, modulation, and more with modular building blocks.
Deploy to Hardware
Push your patches (as C/C++ code) to standalone targets like pedals and embedded boards so it runs on stage without a laptop.
VST3/AU Plugin Builds
Make your own VST3 and AU plugins that run in your Digital Audio Workstation (DAW).
Microcontroller Targets
Easily compile and flash audio code to compact embedded devices.
Shareable Patches
Save, version, and share patches with collaborators including our online community forum.
Extensible Modules
Add new nodes and DSP blocks to fit your sound and workflow.
Licensing
Puke is free for personal and commercial use under AGPLv3 with additional permissions noted in LICENSE, provided that corresponding source code and associated Puke project files remain available to recipients under the terms of the license. If you wish to create closed-source or proprietary products using Puke Studio, or if your business exceeds the commercial eligibility thresholds described below, a commercial license is required.Puke supports three kinds of exports: hardware firmware, generated C++ projects, and audio plug-ins. Firmware and generated C++ exports remain subject to the AGPLv3 and its reciprocal source-availability requirements. Audio plug-in exports include a limited exception permitting distribution within the plug-in ecosystem. Please note that exported firmware, generated code, and runtime systems are distinct from creative works produced using Puke Studio, which remain the property of their creators.*
Puke Standard License
Free with AGPL reciprocal source-availability- Eligibility
- -Annual gross revenue under $100,000 USD, or
- -Non-commercial or educational use, or
- -Open-source projects complying with AGPLv3
- Requires
- -Corresponding source code and associated Puke project files must be made available to recipients in accordance with the AGPLv3 with additional permissions noted in LICENSE
- Rights
- -Use Puke under AGPLv3 at no cost
- -Share presets, tools, extensions openly
- -Build, distribute, and sell firmware, generated C++ projects, plugins, and other products created using Puke Studio, provided all applicable AGPLv3 obligations are satisfied*
For example, a pedal company may use Puke under the AGPLv3 license to develop firmware for a pedal without purchasing a Puke Commercial License, provided that they comply with the terms of the AGPLv3 with additional permissions noted in LICENSE.
In practice, this means that if the pedal firmware is distributed, the company must make the complete corresponding Puke project source code for that firmware available to recipients under the AGPLv3, including any modifications required to build and run it. Users of the pedal must be able to access this source code under the same license terms.
If a person or company wishes to distribute firmware, generated C++ projects, or related exported systems without complying with the reciprocal source-availability requirements of the AGPLv3, then a Puke Commercial License is required. - -No commercial license required
Puke Commercial License
for closed-source proprietary products- Eligibility
- -Annual gross revenue under $1,000,000 USD, or
- -Organizations requiring proprietary or closed-source distribution, or
- -Closed-source distribution of products created using Puke
- Requires
- -Puke Commercial License
- -Valid JUCE commercial license (if applicable*Users are responsible for obtaining any required JUCE licenses when distributing JUCE-linked plug-ins, and appropriate Puke licenses when distributing proprietary firmware, generated runtime systems, or embedded products created using Puke.
For example, a pedal company that uses Puke to generate code for pedals must obtain a Puke Commercial License in order to distribute that firmware as a proprietary or closed-source product. Firmware targets built by Puke Studio and Puke’s generated C++ exports do not link against JUCE. As a result, a JUCE commercial license is not required for typical firmware or generated C++ projects exported from Puke Studio. A JUCE commercial license is required only when the distributed firmware or product links against JUCE components, such as exported audio plug-in projects.) - Rights
- -Proprietary and closed-source distribution of products created using Puke Studio
- -Commercial distribution without AGPL reciprocal source-availability obligations
A commercial license permits use of Puke Studio under our Tier 2 License Agreement instead of the AGPLv3.
Puke Enterprise License
Custom agreement- Eligibility
- -Revenue above $1,000,000 USD, or
- -OEM embedding, or
- -White-label products, or
- -Large-scale deployment
- Requires
- -Custom commercial agreement
- Cost
- -Enterprise licenses start at $5,000/year
- -Contact us for a tailored quote
Support & Services
Puke Studio user support is available through our online community forum, and commercial support is available for:
- Commercial Licenses
- Custom Features and Hardware Targets
- Technical Support
- Product Design
- Project Porting