We publish when our engineering team has something specific to say — usually a methodology post, a benchmark, or a long-form explainer that pairs with one of the platform products. No newsletter cadence, no trend-chasing. Each post is written by whoever did the work.
Most audio fingerprinting was built to detect exact copies. Modern leakage looks nothing like that. The multi-scale matching architecture behind Nomad Listen and the rights economics it unlocks.
Music royalty data is famously broken. The structural reasons, the categories of money typically lost, and the reconciliation pipeline behind Nomad Rights.
Sub-genre embeddings that find the next artist instead of the next chart. The methodology behind Nomad A&R, calibrated against twelve working A&R teams.
We don't publish on a schedule. We publish when an engineer or a rights analyst at Nomad has done a specific piece of work and has a defensible thing to say about it. If a post would need to invent a thesis to fill a slot, we don't write it.
The byline on each Sound Post is the person who built or operated the thing being written about. Not the comms team. Not a ghost writer. If you have a question about the post, it lands in the inbox of the person who wrote it.
We don't write about what the platform might do next year, or what AI in music could become. We write about what we have built and what it does and where it doesn't work. The aspirational posts are not interesting; the operational posts are.
If you want to know when a new Sound Post lands, subscribe to the RSS feed or write to us. We don't run a marketing newsletter and we're not planning to start.