TL;DR
AudD is recognition infrastructure for developers: clip recognition, stream callbacks, and bring-your-own reference catalogs. What you do with the detections is up to you, and that flexibility is the point.
Sonovault treats the log as the product. Register a stream URL and you get a stored, deduplicated play history with an ISRC on every play, date-range airplay reports, webhooks and SSE, and a no-code dashboard, backed by a 90M+ track metadata catalog.
Pick by what you're building. Matching against your own uploaded audio, or want raw events only? AudD. Want the play log, the reports, and the identifiers without building that layer yourself? Sonovault.
Published August 10, 2026 · Sonovault is independent and not affiliated with AudD
Which one fits your project?
Both register arbitrary stream URLs and recognise what airs. The split is in how much of the layer after detection you want to own.
- You need to match against your own uploaded catalog (your releases, jingles, ads)
- You only want raw detection events and will build storage and reporting yourself
- Recognition of user-submitted clips at high volume is the main job
- You're comfortable being entirely API-driven, with no dashboard in the loop
- You want the play log stored, deduplicated, and queryable without building it
- You need airplay reports with an ISRC per play, for clients or royalty workflows
- Non-developers on your team need to add streams and pull reports
- You want detection and a full metadata API (ISRC, ISWC, links) from one vendor
AudD vs. Sonovault for stream monitoring
Based on each product's public documentation. Features change; verify anything load-bearing with the provider before you commit.
| Aspect | AudD | Sonovault |
|---|---|---|
| Register any stream URL | ✓ Yes, submit your own stream URLs | ✓ Yes, any Icecast/Shoutcast-style URL, via dashboard or one API call |
| Real-time recognition of what airs | ✓ Yes, results as songs are detected | ✓ Yes, now-playing typically updates under a minute after a track starts |
| Where results land | ~ Sent to your callback; storing them is your job | ✓ Stored play log with a history API, plus webhooks, SSE, and polling |
| Play counting | ~ Per-detection events; you decide what counts as one play | ✓ Deduplicated per airing: one spin counts once |
| Airplay reports | ~ You aggregate detections yourself | ✓ Date-range spin reports per stream, with CSV/XLSX export |
| ISRC per play | ~ Track metadata with streaming-service links | ✓ ISRC on every play; ISWC lookup one call away |
| Dashboard / no-code path | ~ API-first, built for developers | ✓ Full dashboard: add a stream, watch the log, export reports |
| Match against your own uploaded catalog | ✓ Yes, bring-your-own reference database | — Not offered; we match against our 90M+ track catalog |
| Clip recognition API | ✓ Yes, a core product | ✓ Yes, audio identification on paid plans |
| Royalty-reporting fit | ~ Not its focus | ✓ Airplay reports plus SoundExchange CSV tooling (verify before you file) |
Legend: ✓ strength · ~ trade-off or caveat · — not offered
The layer a raw recognition API leaves to you
Detection is where a monitoring project starts, not where it ends. Two jobs Sonovault takes off your plate.
Every recognised play lands in a history you can query by stream and time range, with repeated detections collapsed so one airing counts once. Now-playing, history with incremental polling, signed webhooks, and a live SSE feed are all included, and polling costs no API credits. Outage emails tell you when a stream goes silent.
Pull a date-range spin report per stream: play counts, first and last played, and a per-airing detail log, each row carrying its ISRC. Export CSV or XLSX from the dashboard, or fetch JSON from the API. Because every match resolves into a 90M+ track catalog, cross-platform links and ISWC lookups are one call away.
Flat per-stream pricing, with the after-layer included
Both products price stream monitoring as a flat per-stream rate. The difference is what that rate has to cover.
With a raw recognition API, the per-stream fee buys detections; the play-log store, deduplication logic, report generation, and any dashboard are engineering work on your side of the line. That's the right trade when the after-layer is genuinely custom.
Sonovault's stream monitoring is €29 per active stream per month, on top of any API plan including the free tier, billed only while the stream is monitored. The stored history, dedup, reports, webhooks, SSE, and dashboard are part of that price, and polling the log burns no credits. We deliberately don't quote AudD's prices here; check their site and ours, and price the layer you'd otherwise build yourself.
Frequently asked questions
Point it at a stream this afternoon
Create a free account, add a stream URL from the dashboard, and watch the log fill in real time. €29 per active stream per month, stop anytime.
Disclosure & methodology. This page is published by Sonovault and compares the two products' approaches to stream monitoring based on public documentation, current as of 2026-08-10. It does not quote AudD's prices or speak for AudD. “AudD” is the mark of its respective owner; Sonovault is independent and not affiliated with, endorsed by, or sponsored by AudD. Features change, so confirm current capabilities and pricing with each provider directly. Spot an inaccuracy? Email support@sonovault.now and we'll correct it. See also data sources & attribution · about Sonovault.