Most synth manufacturers treat their firmware like a vault. Bastl Instruments handed the keys to its Kastle 2 and Citadel over, and the result is a small pocket modular that now runs code its own engineers never wrote.
What actually changed in firmware 1.7?
The update, live since September 2, adds Humanize and Swing to the onboard sequencer: a knob twist shifts every trigger off the grid to loosen up a pattern, with MIDI CC32 exposing both parameters for external control. Bastl also opened up assignable LFO modulation destinations for more animated patches, and added MIDI velocity and sustain support to the Alchemist hybrid-synthesis engine, alongside a batch of smaller fixes. It is a solid, free update on its own, the kind Bastl has shipped for the Kastle 2 line since launch.
Why does the open-source part matter more than the update?
Bastl open-sourced the Kastle 2's firmware in early 2026, publishing the full codebase on GitHub instead of keeping the sound engine proprietary. That single decision is why a device this small now has a growing library of engines Bastl itself didn't design, something almost no other hardware synth maker allows. Owners aren't limited to whatever ships in the box; they can flash an entirely different instrument onto the same circuit board whenever a developer publishes one.
Who's actually building these engines?
Knoscillator turns the Kastle 2 into a stereo oscillator driven by 3D parametric curves, with its own built-in sequencer and delay baked in. Developer Oliver Torr has released Glazmo_Kastle2_Skrub, which continuously records into an audio buffer and plays it back through harmonic or chaotic modes, and has a companion 808-style kick engine, Glazmo_Kick, in the works. Separately, a developer going by sxilence6 published Kastle Chan v1.0, a patchable vocal synthesis engine, as version 1.0, meaning it is already a stable, documented release rather than a rough proof of concept.
The Kastle 2 shipped as one instrument. A year into being open source, it's several.
None of this requires special tools. Flashing a community engine uses the same USB process Bastl documents for its own firmware, which is exactly the point: the barrier between "official Bastl instrument" and "community-built instrument" is now just a file.
