Side-by-side comparison of WolfWave against every other Apple Music streaming tool: Jam Deck, Cider + cider4obs, Now Playing Pro, MusicRPC, NextFire, Nyan, Moobot.

Apple Music streamers shouldn't need five apps. Here's how WolfWave stacks up.

The Big Picture

Every other tool does one piece. WolfWave does all of them, natively, from the real Music.app.

Tool	Reads real Music.app	OBS overlay	Twitch chat bot	Song requests into Music.app	Discord Rich Presence	Native macOS	Price
WolfWave	✅	✅	✅	✅	✅	✅	Free, open source
Jam Deck	✅	✅	❌	❌	❌	🟡 Python	Free, open source
Cider + cider4obs	❌ replaces Music.app	✅	❌	❌	✅	🟡 Electron	Paid
SpotchBot (Spotify)	❌ Spotify only	❌	✅	🟡 Spotify queue	❌	❌ cloud	Free + paid
Now Playing Pro	🟡 DJ-software first	✅	✅	❌	✅	❌ Win+Mac	Paid
MusicRPC	✅	❌	❌	❌	✅	✅	Paid
NextFire RPC	✅	❌	❌	❌	✅	✅ Deno	Free, open source
Nyan / Streamling / Zyphen	❌ Cider or Last.fm	✅	❌	❌	❌	❌ web	Free
Moobot / StreamElements	❌ YouTube/Spotify	❌	✅	🟡 YouTube only	❌	❌ cloud	Free + paid

Legend: ✅ first-class · 🟡 partial · ❌ not supported

Why is the Apple Music side so empty? Spotify ships a public Web API, so streamers have plenty of tools: SpotchBot, Nowify, discord-music-presence, and more. Apple Music has no such API. Every Apple Music tool has to hack Music.app through ScriptingBridge, which is why the field is nearly empty and each tool does one thing. WolfWave does that hard part once, then bundles the whole stack.

vs. Jam Deck

Jam Deck is a Python menu bar app that reads Apple Music via AppleScript and serves a browser source on localhost. Same source-of-truth idea as WolfWave (real Music.app, no Cider), but the scope stops at the overlay.

No Twitch chat bot. No !song, no !last.
No song requests. Viewers can't queue tracks.
No Discord Rich Presence.
No notarized installer. Clone the repo, run py2app.

If you only need a now-playing overlay and nothing else, Jam Deck works. If you want chat, Discord, and requests in the same app, that's WolfWave.

vs. Cider + cider4obs

Cider is a third-party Apple Music client built on Vue + Electron. It runs on Mac, Windows, and Linux, integrates Discord / Last.fm / Spotify, and exposes a Socket.io WebSocket that cider4obs reads as a browser source. It's a polished, paid app with a real community.

The catch hasn't changed: you stop using Music.app and run Cider instead. That means giving up the native Music app's library sync, Handoff, AirPlay routing, lossless/spatial pipeline, and everything else Apple ships, all to gain a now-playing feed.

WolfWave reads Music.app directly via ScriptingBridge. No client swap, no second player. You keep the app you already use.
WolfWave's overlay WebSocket is token-authenticated; Cider's Socket.io WS is open on localhost by default, so any page on your machine can read your now-playing. Details in WebSocket security.
Cider has no Twitch bot and no song requests. cider4obs is overlay-only; the chat bot, !sr queue, Channel Points, and Bits boost all live in WolfWave.
Cider is paid and cross-platform; WolfWave is free, open source, and macOS-native. Different trade: Cider buys you Windows/Linux, WolfWave buys you the real Music.app plus the full stream bundle.

Cider is a great alternative Apple Music client. WolfWave is a streaming bridge for the real one. If you switched to Cider only to get a stream overlay, WolfWave gives you that overlay without leaving Music.app.

vs. Now Playing Pro

Now Playing ships a Twitch bot and a "live playlist" Discord bot. The closest competitor in feature breadth. But:

Aimed at DJ software: Serato, rekordbox, Traktor, Virtual DJ. Apple Music from Music.app isn't the headline source.
Paid. WolfWave is free + open source.
Not a native SwiftUI app. Runs cross-platform via a different stack.
No song-request queue feeding directly into Apple Music via MusicKit.

If you DJ in Serato and stream to Twitch, Now Playing fits. If you just play Apple Music and want chat to request tracks, WolfWave fits.

vs. SpotchBot

SpotchBot is the go-to Spotify song-request bot for Twitch. It's cloud-hosted (nothing to run on your machine), viewers request tracks with chat commands (!sr, !queue, !nowplaying) or Channel Point redemptions, and approved songs drop into your Spotify queue. If you stream on Spotify, it's the tool to reach for.

It's also the closest functional cousin to WolfWave's signature feature: chat-driven song requests that land in the player you actually play. The difference is the ecosystem and the scope:

Spotify, not Apple Music. SpotchBot queues into Spotify via Spotify's Web API. WolfWave resolves !sr through MusicKit and queues into the real Music.app. Apple Music has no public Web API, so nothing like SpotchBot existed for it. That gap is exactly what WolfWave's song requests fill.
Song requests are all SpotchBot does. No OBS overlay, no Discord Rich Presence, no !song now-playing bot. On Spotify you'd add Nowify for the overlay and discord-music-presence for Discord. WolfWave is all of it in one app.
Cloud vs native. SpotchBot runs on someone else's server and needs your Spotify OAuth. WolfWave runs locally, reads Music.app on-device, and its overlay WebSocket is token-authenticated.
Bits Boost. WolfWave lets a Bits cheer jump a viewer's queued track to the front. SpotchBot has Channel Points but no Bits-to-boost.

If you're on Spotify, use SpotchBot. It's good at its one job. If you play Apple Music, WolfWave is the SpotchBot-equivalent request flow plus the rest of the stream stack.

Other categories

Discord-only tools. MusicRPC, NextFire's apple-music-discord-rpc, and discord-music-presence do Rich Presence and nothing else. They're good at it. WolfWave's Discord RPC does the same job (album art, play/pause state, timestamps), then adds the overlay and Twitch side a standalone RPC tool never will.
Multi-source web overlays. Nyan's Music Overlay and friends list Apple Music support, but the fine print reads "via Cider" or "via Last.fm scrobbles." WolfWave reads Music.app directly: track changes hit the overlay in under a second, no scrobble lag, no Cider.
Cloud chat bots. Moobot and StreamElements take song requests, but the player is YouTube embedded in a dashboard. They can't reach into Music.app on your Mac. WolfWave's !sr queues into the real player, so the audio your viewers requested is the audio you actually play.

What Only WolfWave Does

Real Music.app reads. ScriptingBridge with tolerant FourCharCode parsing. No Cider, no Last.fm.
Song requests into Apple Music. !sr <query> resolves via MusicKit and queues in Music.app. No competitor does this. See song requests.
Channel Points + Bits Boost. WolfWave manages a "Request a Song" reward through Helix and dispatches Bits cheers to boost a viewer's queued track.
Token-authenticated overlay WebSocket. OBS clients must present the per-install token; see WebSocket security. Cider's WS is open.
Listening History + Monthly Wrap. On-device, opt-in play log with charts and an exportable share card. See Listening History. Streamer tools don't ship this; only generic scrobblers do.
Streamer Mode masking. Sensitive values masked on screen for on-camera safety. See Streamer Mode.
Sparkle EdDSA auto-update + Homebrew + DMG. Proper distribution. Jam Deck is git clone, NextFire is deno.

Honest Gaps

macOS only, and modern macOS at that. WolfWave needs macOS 26 (Tahoe) on Apple Silicon. Cross-platform tools (Cider, Nyan, Now Playing Pro) cover Windows and older Macs. WolfWave doesn't.
Apple Music only. Spotify, YouTube Music, and Tidal are out of scope on purpose.
Young third-party ecosystem. The overlay's message contract and the Stream Deck protocol are documented, but the third-party widget scene around WolfWave is still small next to Cider's.

Consistent with the brand: native macOS, Apple Music, streamers. Pick the tool that matches your stack.

WolfWave vs. Jam Deck, Cider, Now Playing & More