I run Buchert Audio alone. I write the DSP, design the interfaces, answer the emails, and use the plugins in my own sessions. That means I also decide how the tools behind the scenes work. This page explains that.
All signal processing in Buchert Audio plugins is written by hand in C++. There is no AI-generated DSP, no machine-learned parameter tuning, and no algorithmic "optimization" that I have not personally listened to and approved.
Every filter curve, every saturation response, every parameter range is tuned by ear. If it does not sound right in a session, it does not ship.
Your plugins run entirely offline. They do not phone home, do not collect data, and do not depend on any external service to function. The only network connection is the one-time license activation.
Behind the scenes, I use AI-assisted tools to help with things like organizing email, drafting internal notes, classifying support requests, and preparing operational summaries. These are internal workflows — they help me work faster on routine tasks so I can spend more time on DSP and production.
Some specifics:
Sensitive data, including customer correspondence and personal information, is processed locally on my own hardware. It is not sent to external AI services.
I am responsible for everything Buchert Audio releases, publishes, and communicates. When AI tools assist with preparation, the final judgment is mine. If something is wrong, that is on me — not on a tool.
If you have questions about how any of this works, write me at hello@buchertaudio.com.