MousePlugins

About MousePlugins

Why “MousePlugins”?

The name goes back to drinks with a few musician friends.

At the time, I was making music mostly by drawing and editing notes directly in the piano roll with a mouse. One of them looked at what I was doing and said:

“You’re not making house music. You’re making mouse music.”

The name stuck.

Years later, when MousePlugins was created, the name felt like the obvious choice.

A background in music

We have experience across music production and live events in Europe.

Over the years, we have worked with producers whose credits include artists and records such as Carrapicho – “Tic, Tic Tac,” Domingo – “Baila Conmigo,” and Coumba Gawlo – “Pata Pata.”

Our experience also includes live music and events, from festivals such as the Paléo Festival to concerts and rave parties.

That background still shapes how MousePlugins are built today.

These aren't plugins designed from a feature checklist. They're tools shaped by real experience around producers, musicians, studios, PA systems and dancefloors, and by people who still make music themselves.

How the plugins are built

MousePlugins combines traditional audio engineering with modern development tools.

That includes measurements, reference hardware and software, automated testing, listening tests, real DAW testing, and, where useful, AI-assisted development.

AI is used as an engineering tool: to help analyze code, test implementations, find problems and accelerate repetitive development work.

It doesn't decide what a compressor should sound like, whether an EQ feels right, or whether a plugin is finished.

Those decisions are still made by ears.

Every MousePlugins release ultimately has to pass the same test:

Would we actually use this in our own music?

A note on AI

AI is an engineering assistant, not a creative director. Humans define the products, sound, behaviour, design, reference targets and final approval. AI helps us write, inspect, test and document software more efficiently.

We use AI like a producer uses a DAW, not like someone uses Suno: it helps us build what we designed; it does not decide what to create.

Beta program

Break our plugins for fun

Test pre-release builds and help shape what ships next.

Join the beta →
What testers get
  • Private pre-release builds when a beta is active.
  • A direct path to report DAW, install, licensing, and sound issues.
  • Early influence on compatibility priorities and release readiness.
  • Provide suggestions on future development and roadmap.
  • Request specific plugins.
Cart
Cart empty
Browse Plugins