Skip to main content

About

The story behind Aureo.

Why I Built This

In a past life, I studied music production at Berklee and SAE and I've been accumulating gear and plugins ever since. Like all of us, I never had any system for keeping track of any of it. Spreadsheets got abandoned. Mental notes got forgotten. And every time I needed to figure out how much renter's insurance to buy or figure out what version of a plugin I was running, it felt like I was starting from scratch.

So I built Aureo — the tool I always wanted. A way to catalog my plugins, map out my signal flow, and see where all my damn money was going.

It's still mostly a personal project, but as I started sharing it with friends and fellow creative people, I realized how many people were in the same boat. So here we are.

The Philosophy

Your studio data is personal. It's a record of creative decisions, investments, and workflows we build up over years. That data shouldn't live on someone else's server.

I wanted Aureo to be local-first. Your data stays on your machine — no cloud accounts, no subscriptions, no recurring fees. Buy once, own forever. It's the way software used to work. It has its limitations, but I was tired of never "owning" anything anymore -- like a lot of you.

The Catalog

Behind Aureo is a growing database of hardware and plugins — specs, images, I/O mappings, version history. I'm building it to be open and community-driven because this kind of data should belong to all of us, not locked inside some company's walled garden.

Aureo is just the first way to use the catalog. My hope is that it becomes a resource for other developers, researchers, and creators to build on.

Who's Behind This

I'm Jeff. All I ever wanted to do was tinker in a studio and make noises like Brian Eno. Building software ended up paying the bills, but the studio never stopped calling. Aureo is what happens when those two worlds finally collided for me.