Your stream's back end, running on your machine.

Five backends. Cascade and Cider are local apps talked to directly over loopback, Spotify and Jellyfin are their web APIs, and OS media keys drive the system transport: Apple Music and Spotify on macOS, the Windows media transport, playerctl on Linux. Switching mode repaints the settings, so a Cider user never sees a Jellyfin field, and only the modes whose app has been seen running appear at all.

A request resolves against your library and goes to the player as play next. Approved requests retire out of the Queue on their own once the player moves past them, into History, which is the record of who asked for what. A request that matches nothing in the library goes to the Download Wishlist instead of being dropped. Mods get their own approval page on its own port, reached by a link that carries its own token and can be regenerated.

Events, Chat, Now Playing, and a Combined source that layers events and chat for anyone who would rather add one browser source than two. Switching an overlay off does not just hide it in settings: its address serves a blank transparent page, so the browser source already sitting in OBS goes dark.

Accent color pulls itself from the album art each track, or pin it. Width, text size and corner radius are yours; album art, album name, progress bar, elapsed and remaining times each toggle off. It credits the requester when the track came in through song requests, and leaves the line out entirely when it did not. The settings panel previews the real overlay in an iframe, not a mockup of it, so what you see is what OBS renders.

Corner, animation, on screen duration and how many stack at once are all settings. Message templates take {user}, {bits}, {tier}, {months}, {count} and {message} depending on the event. Alerts can fire as a browser source, as a flash of a named OBS source, or both. Custom CSS overrides any of it, with the class names listed right there in the panel.

Side, max visible messages, message lifetime, font size, bubble color and opacity, badges on or off, timestamps on or off. Custom CSS here too, and the emotes are the real ones: 7TV, BetterTTV and native Twitch.

The editor lives on this site, not in the app, so it is one link away: open the overlay editor. It has tabs for the alert overlay and the chat overlay. The app has a Custom CSS field for each and lists the exact class names right beside the box, so the round trip is upload, style, paste. Alerts can also import a .css file directly.

Live scene list and per source toggles, streaming and recording status with elapsed timecode. An optional third column puts the OBS controls next to the chat and events feeds, so you are not switching tabs mid stream. !scene, !source and !record do the same from chat, moderator only by default.

Permission levels are everyone, subscribers and up, VIPs and up, moderators and up, and broadcaster only. Sources are chat, whisper, and channel point redemption input, set per command. Custom commands match three ways: !trigger, contains, or starts with, and take {user}. Built in responses also take {song}, {result} and {query} where they apply. !run and !killswitch ship disabled.

System voice and rate. Chat TTS has its own permission gate and a max length. Bits above a threshold get read, named channel point redemptions get read, and alerts can be read. Bots are ignored by default, including this app's own replies, which is the thing that makes TTS usable at all. Name aliases map a screen name to how it should be pronounced.

Redeems match on the exact reward name and do one of four things: run a script, play a sound, switch an OBS scene, toggle an OBS source. Event triggers are per event type and can send a chat message, play a sound and run a script, each with a Test button so you are not going live to find out. Scripts only run from domains on an allowlist you set.

Stream dials out to the relay, so there is no inbound port and nothing to forward on your router. The relay only carries an enumerated list of actions, it is not a general proxy. A defer switch decides which side answers, so you never get the same command answered twice. This will be the one part of the app that is not local: the relay authenticates you with your Twitch token, so switching it on means handing that token to whichever relay you point at. It stays off until you turn it on, and the relay address is a setting, so you can run your own instead of ours.

A plugin registers commands, subscribes to events, and can render live content into its own dashboard panel. External clients can also send commands over the dashboard's WebSocket, which is how a stream deck triggers something without going through Twitch chat at all.