ARADAR is the tool I kept wanting and couldn’t find.
It started as a way to organize a growing collection of reference tracks. Over time, it became a workspace for analyzing music, studying labels, and managing demo submissions.
Today, ARADAR brings those workflows together in a single application for electronic music producers, mixing engineers, and mastering engineers.
Where it came from
Like many producers, I spent years collecting references.
Tracks saved for a bassline, a mixdown, a groove, a breakdown, or simply a feeling.
The collection kept growing, but finding the right track when I needed it became harder and harder. References ended up scattered across folders, playlists, notes, and DAW projects.
ARADAR began as an attempt to solve that problem.
Once the library was organized, new questions naturally followed.
- How does this track compare to my references?
- What makes one label sound different from another?
- Where does this track belong?
The answers to those questions became the rest of the product.
How it’s built
ARADAR is local-first by design.
No subscriptions. No cloud dependency. No analytics. No training models on your library.
Your music, references, and data stay on your machine.
The app is macOS-only on purpose. I’d rather build one platform exceptionally well than spread myself thin.
Where it’s made
Built in Sydney, Australia, between studio sessions and work on other software products.
ARADAR is intentionally small. When you send an email, it reaches the person building the software.
Stay in touch
Have an idea, found a bug, or want to suggest a feature?
Reach out at hello@aradar.app.
Every major feature in ARADAR started as a real workflow problem. The next one might start with yours.