Engineering,
as stance.
eramux is a studio for systems and application engineering, and for product development under our own brands. We build precision software: local-first by default, narrow in surface, engineered to last. Engineering excellence as house style.
A studio, not a factory.
Tools, not platforms.
We don't build suites. We build narrow, fast tools that do one thing exceptionally well, and we hold them to a higher engineering standard than the category usually bothers with. The product list is short on purpose.
Local-first, cloud-coordinated.
Your data, your machine, your latency. The cloud coordinates; it does not custody.
Engineering as the standard.
Strong types, end-to-end traces, every error path thought through. The half nobody demos, and the half that survives contact with real use.
Small, sharp, owned.
Each product is a single-purpose instrument. No suites, no rented infrastructure we don't understand. If a feature isn't load-bearing, it isn't shipped.
Two disciplines, one studio.
Engineering and product development. Different work, the same set of standards. Each product stands alone with its own brand.
One track.
Every catalogue.
One request.
The standard offer in this category is a desktop app that analyses your files brilliantly and ignores every platform you stream from. We rebuilt around the seam: trackmatch analyses your library locally, then resolves each reference across every catalogue at once, with confidence scores that are honest about the hard cases.
Hand it a file, a URL or a fingerprint: get back canonical IDs on Spotify, Apple Music, Beatport, Tidal, SoundCloud, Bandcamp and YouTube, each with its own calibrated confidence score. Built to handle the edits, remasters and live versions that trip up everything else.
A working environment for the modern music professional.
resonance is what trackmatch slots into: the working surface for DJs, producers and music supervisors who manage real libraries across real platforms. Crates, sets, watch folders, cross-platform sync; and the analysis underneath: beatgrids, cue points, key and tempo, kept where you can edit them.
Same architecture as trackmatch: library stays on disk, analysis runs on your machine, sync runs through the seam. Curate crates, edit beatgrids and cue points, own the data. The paid surface that funds the free standalone resolver beneath it. Closed alpha opens to a working circle of DJs once the core is ready.
The scaffolding crews skip
until it's too late.
Every collective hits the same wall: running the organisation starts to eat the time you'd rather spend running parties. kollektiv is the operations layer for the other side of that wall: legal structuring, finances, the gig pipeline, marketing, the roster. One surface, no spreadsheet sprawl.
Shaped with input from a working collective. Incorporation, fee splits, gig contracts, the marketing schedule, the member roster: the parts of being a collective that no one wants to do at 3 a.m. after the night ends.
More tools on the bench, outside music. Running quietly, well outside daylight. Write to us to be told when they surface.
Building in the same
neighbourhood?
We swap notes with a few people working on similar problems. Short messages preferred // long ones tolerated.