Akai Promised to Open the MPC. What It Shipped Is the Part the Law Already Required.

What did Akai actually publish?

On 9 November 2026, Akai Professional's parent company inMusic put a repository called az0x-open-source live on GitHub, under the org handle inmusic-software (github.com/inmusic-software/az0x-open-source). It covers 14 separate MPC devices across three firmware releases: MPC G1 v3.10 (MPC X, X Special Edition, Live, Live II, One, One+, Key 37, Key 61 and Force), MPC G2 v3.10 (XL, Live III, One G2 and Key 37 G2) and MPC Sample v1.3.0. The same repo also covers inMusic's Engine OS hardware, the Denon DJ Prime and SC decks, Numark's Mixstream Pro line and the Rane System One, which tells you this is a brand-wide compliance drop, not something built specifically around the MPC teaser.

Inside is the Linux environment that runs underneath MPC firmware: the kernel, glibc, busybox, alsa-lib, bluez5, systemd and a long list of other upstream packages, published, per the repo's own description, with "very few changes from upstream projects." The maintainers say they aim to "submit all relevant patches back up to the mainstream projects."

Does this prove Akai's October tease was real?

Time To House covered Akai's SampleKey teaser on 29 October, one day after it landed on Instagram, and the whole piece turned on one unanswered question: would Akai publish the actual firmware source code, or just talk about "open source" without showing a license. One day before that, Behringer had previewed open firmware for its own $150 Kick, an MPC One clone, and the timing on Akai's side read like a reply.

Two weeks on, the GitHub drop answers that question, just not the way the tease implied. What's published is not the MPC operating system, not the application layer, and not the AIR audio engines that actually make an MPC sound and feel like an MPC. Those stay closed. What's published is the GPL and LGPL-licensed Linux plumbing that any manufacturer shipping Linux-based consumer hardware is legally required to make available. Akai didn't volunteer a gift, it filed paperwork it owed.

"We aim to submit all relevant patches back up to the mainstream projects." From the az0x-open-source repository's own description

What's still locked down, and what might open later?

The proprietary layer, the part modders actually want, the MPC OS, the sequencer, the sample engine, the AIR synths, is untouched by this release. Akai does say the MPC Sample and the still-unannounced SampleKey are separately headed toward what it calls a more real "vibe-coding" open model, with early modder access already granted to some developers, according to Midnight Rebels. That's the thread worth watching, not this repo. A compliance dump proves Akai follows the GPL. It says nothing about whether the firmware that actually runs an MPC will ever ship with source attached.