What is Behringer up to? Open hardware, vibecoding and the $150 sampler

Behringer wants to sell you the hardware and let AI write the rest. A genuine shift in who controls music technology, or the fastest route yet to an expensive fish tank ornament?

If you follow Behringer on social media, you will have noticed a run of cryptic posts over the past few days. They carried all the clarity of a partner who says “I’ll have whatever for dinner, it’s up to you”, leaving you standing at the fridge wondering what on earth they are on about, and wishing they would just make up their mind.

Well, here we are. The answer has landed, and it is not a surprise. It has simply arrived sooner than most of us expected.

Behringer is going all in on open hardware, and by extension on vibecoding: the idea that anyone with a ChatGPT account can now describe the software they want and have an AI write it for them. As Pepper Brooks put it in Dodgeball, it’s a bold strategy, Cotton. Let’s see if it pays off.

The first product is KICK, which Behringer calls its first open-source hardware sampler, with a target retail price of around US$150. On paper it is a great deal of box for the money. The specification on Music Tribe’s GitHub lists a touchscreen, 16 RGB pads across eight banks, a sampler with sample editing, a step sequencer and looper, more than 300 built-in effects, four assignable knobs, a jog wheel, MIDI, USB and four CV/Gate jacks. There is also an “AI camera” for gesture control. Look at the renders and you will see a layout that owes a lot to Akai’s MPC One, which, given Behringer’s history, will raise very few eyebrows.

The launch post leans hard on the origin story, as reported by Behringer . As the story goes, a teenage Uli spent every spare minute in his local music shop playing synths he could not afford, until the owner threw him out for taking up space meant for paying customers. So he went home and built his own, the UB-1, at 16. Nearly 40 years later, the mission is to democratise music technology. The line that matters comes further down: “With AI, even people without programming experience can turn their ideas into new features and firmware.”

There is a bigger picture behind it. According to Synthtopia, Uli Behringer has written that he has transferred ownership of Music Tribe to the Uli Behringer Foundation and is pursuing nonprofit recognition, under the banner “The biggest threat to business isn’t AI. It’s abundance.” Whatever you make of that, this is clearly a strategy, not a one-off product.

Then came the DJ post. It promised professional DJ hardware for US$300 to US$400, open hardware, the freedom to create your own software and no proprietary lock-in, with the first prototypes being assembled in Behringer’s own factory. The headline read “The DJ industry is about to change forever”, and it closed by saying the future of DJ technology should not be controlled by a few companies. Nobody needs a map to work out which few companies they mean.

Behringer has not dreamt this up in isolation. Vibecoding, where you describe what you want in plain English and an AI writes the code, has moved from novelty to headline in under two years. Earlier this month a developer released free, open-source rebuilds of seven Adobe Creative Cloud apps, from Photoshop to Premiere, built largely with AI coding tools and reported widely by Gizmodo, PetaPixel and others. Free Photoshop. Sounds wonderful, doesn’t it?

Dig a little deeper and the story changes. The man behind it, Brandon Thomas, has 15 years of software engineering experience and has been at pains to point out he is not a casual vibe coder. Even then, VideoCardz notes that the Photoshop clone’s own roadmap puts real compatibility well below 50 per cent. AI did the heavy lifting, but a seasoned engineer steered it. That distinction matters enormously for what Behringer is promising.

The music hardware world has been heading the same way. Synthtopia has spent October reporting on an explosion of unofficial firmware for Elektron boxes, hacks for Sequential and Teenage Engineering gear, and M-Vave officially opening up the firmware of its FM-1 with a developer SDK. Behringer has read the room. The pitch is simple: we build the hardware, you build the software, and the price falls through the floor because nobody is paying a team of engineers to write the operating system.

To be clear, I am all for it in principle. It is a bit Elon-ish though in its delivery, all capital letters and revolution, but it is possible, and the idea of a DJ setup that is not chained to one company’s ecosystem is genuinely appealing. The question is what happens when it meets real people.

Here is the problem. Most DJs cannot get through a weekend without a Rekordbox headache. Corrupted libraries, cue points that vanish, a USB that will not read in the booth. That is software built and tested by a large company with paid engineers, and people still struggle with it. Now hand the average ChatGPT user a box, a GitHub link and the instruction to write their own firmware, and a fair few of these units will be bricked within the hour.

Look at what sits in the KICK repository. Alongside the application and the audio engine there is a hardware communication protocol and a Buildroot Linux image: an entire embedded operating system that has to be compiled for the device before any of your changes will run. That is not a job you finish by typing “make me a better sampler” into a chat window. It is the sort of work the Adobe clone needed a 15-year veteran for.

Then there is the question of who carries the can. If a community build crashes your KICK, who fixes it? Does flashing your own firmware void the warranty? Is there a guaranteed recovery mode that restores the factory software (if there is one), whatever you have done to it? Elektron, which has watched unofficial firmware spread across its gear this year, has been grappling with exactly this. No manufacturer can reasonably be expected to support code it did not write, which leaves the owner on their own.

And DJing raises the stakes further. A producer whose sampler crashes at home loses an afternoon. A DJ whose software freezes mid-set loses a dancefloor, and possibly the booking. The CDJ became the club standard not because it was exciting, but because it was predictable. Every booth has one, every DJ knows it, and it does not fall over. A US$300 controller running whatever someone compiled a C U next Tuesday is a very different proposition, however open and well-meaning it is.

Then comes the question none of the launch posts has answered: what will it actually talk to? Can a bedroom coder get a US$300 Behringer unit to sit happily alongside an AlphaTheta DJM mixer and a pair of CDJs? The network that links a club booth together, Pro DJ Link, is AlphaTheta’s own proprietary system, and there is no sign of it being opened up. Will it run Traktor or Serato? Traktor has long let DJs map their own controllers, but Serato is far less forgiving. Serato’s own support pages state that its virtual decks cannot be mapped to MIDI jog wheels at all, and that you need natively supported hardware for that. Native support comes from partnerships between companies, not from a clever prompt.

It is a big gamble. It is almost like being sold a car with wheels and seats, and told you will work out the engine yourself.

So what has Behringer actually put on the table? The Music Tribe Open Source page on GitHub sets out the deal plainly. Behringer makes the hardware and publishes schematics, bootloaders, board-support layers and documentation. You build the firmware and apps on top, and what you write stays yours. The community will even vote on what hardware gets built next. The Discord welcome message goes further, promising “the cheapest honest hardware in the world” while the community “makes it do everything”.

There is a pleasing irony in a company famous for recreating other people’s classics asking its community, in bold type, to publish only what is theirs to publish. But let’s leave that there.

The reality today is modest. At the time of writing the KICK repository had 14 commits, around ten stars, two forks and no published release. There is a second repository for IGNITE, a 64-channel multi-track sequencer, and when I checked it, its own readme said the source code, build instructions and hardware files had not been uploaded and there was no buildable firmware. The DJ hardware that headlined the “change forever” post has no repository at all. KICK itself is still a prototype, with no confirmed release date or final price.

So, will you be left with an extravagant fish tank ornament? Honestly, nobody knows yet, and that includes Behringer. I’m not saying they can’t do it, I am merely skeptical. I’m sure in time, I will be made to eat my words, because a stable system will emerge as an industry standard.

There is a version of this that works. It looks like the FM-1, where a small, cheap box picked up a genuine community and M-Vave had the sense to back it with proper developer tools. For that to happen here, KICK and the DJ hardware need to ship with factory software that is stable and complete on day one, plus a recovery mode that can bring any unit back from the dead. The community should be the bonus, not the operating system. As others have already pointed out, open source must not become an excuse to sell unfinished software and let the customers finish it.

If Behringer gets that right, the effect on DJing could be real. A properly open US$300 to US$400 controller that plays nicely with the libraries DJs already have would force the big names to rethink their pricing and their walled gardens. That would benefit every DJ, including the ones who will never write a line of code.

If it gets it wrong, we will see a wave of cheap boxes bought on impulse, bricked by a half-understood prompt and listed on Marketplace a month later. My advice for now is simple. Buy any of this for what it does out of the box, not for what someone on Discord says it might do one day.

For all the noise, I would love to see what Behringer actually delivers. Until then it is still “whatever you like for dinner”, and we are waiting to see what lands on the plate. Decoded would welcome a response from Behringer. What software will KICK and the DJ hardware ship with, will there be a guaranteed factory reset, does custom firmware affect the warranty, and when will we see those DJ prototypes? We will happily publish the answers in full.

Disclaimer, this is just an opinion from the editor based on current social media posting from Behringer

Related