about KERN

from stages to spectral processing.

KERN is one person and a growing community building five audio plugins in copenhagen, denmark. this is the story of how it started.

the story

i used to be a touring artist. playing shows, writing music, living inside the cycle of create-perform-repeat that every musician knows. it was everything i wanted.

somewhere along the way, i discovered Cycling '74 and Max for Live. the idea that you could build your own instruments, not just play them, changed how i thought about music entirely. i started patching instead of practicing. building tools instead of just using them. the line between making music and making the things that make music got beautifully blurred.

then i got sick. a life-threatening illness that took touring off the table. the stages went away. the travel stopped. the identity i'd built around performing had to be rebuilt from scratch.

music didn't stop. it just changed shape. what had been a career became a hobby again. and honestly, i love it more now than when it was a job. there's something liberating about making music because you want to, not because you have to fill a setlist or meet a release schedule.

but that itch, the Max for Live itch, the "i want to build my own tools" itch, never went away. it grew. from Max patches to C++. from simple effects to spectral processing. from prototypes to something i believed could actually ship.

KERN came from a specific frustration. i needed a resonance suppressor. the good ones cost $199 and required iLok. the cheap ones were cheap for a reason. i wanted something in between: genuinely good DSP, no DRM nonsense, $29, done. so i started reading papers. ERB filterbanks. spectral reassignment. zero-delay feedback smoothing. weeks of research before writing a single line of code.

that became SMOOTH. and the process of building it, the research-first approach, the constraint of five knobs, the blind testing against established tools, felt like something worth repeating four more times.

the approach

why "we" means something specific here.

KERN is a solo project. one developer, one designer, one decision-maker. but when i say "we," i mean it. none of this happens in isolation.

the community around KERN shapes what gets built and how. beta testers who find edge cases i'd never think of. producers who explain their actual workflow instead of the workflow i imagine. people on reddit and elektronauts who tell you honestly when something isn't working. that feedback is the difference between a plugin that's technically correct and one that actually helps people make music.

every plugin after SMOOTH is community-funded. not because i need permission to build them. all five will ship regardless. but building in public, with people who care about the outcome, makes better tools. backers don't just pay $19 for early access. they join the build. they hear progress. they push back when something feels wrong.

"we" is me and everyone who makes this better than i could alone.

philosophy

five constraints that shape everything.

most plugins try to do too much. they ship with 47 parameters, need a manual to understand, and eat your CPU for breakfast. the result is a toolbox full of things you open once and never touch again.

KERN plugins do one thing each. every algorithm starts with weeks of research. reading papers, studying existing implementations, understanding the psychoacoustics. then building. then blind testing against the best tools on the market. if it doesn't pass, it doesn't ship.

the four laws

one thing, done right.

every plugin solves one problem at world-class level. the moment it tries to do two things, it has failed.

no iLok. ever.

your license is yours. works offline. works forever. no accounts, no activation servers, no dongles.

cpu is respect.

under 3% at 44.1kHz, single instance. producers run 20-30 plugins in a session. KERN should never be the bottleneck.

if it needs a tooltip, it failed.

five knobs maximum. every label immediately comprehensible. complexity belongs in the algorithm, not the interface.

timeline

how we got here.

the early years

touring artist. writing and performing music. the whole cycle.

the discovery

fell in love with Cycling '74 and Max for Live. started building instruments instead of just playing them.

the shift

a life-threatening illness ended touring. music became a hobby again. and honestly, better for it.

the itch

from Max patches to C++. from simple effects to spectral processing. the tool-building instinct kept growing.

2026

KERN launches. SMOOTH ships. four more plugins to go, built with a community that cares about the outcome.

we're building five plugins.

want to know when the next one drops?

no spam. just release announcements. unsubscribe anytime.