Active SaaS
Clipify
Clipify is a hosted Twitch playback system for creators who want their existing clips to keep a stream active during breaks or unattended periods. A configured overlay runs as a browser source in streaming software, while the dashboard, playlists, channel-point integration, and remote controller manage what viewers see.
Status
active
Period
2025—Now
Context
Independent SaaS
The challenge
A clip player looks simple in isolation, but a live-streaming product has several states that must agree. Creator configuration, Twitch events, a remote control surface, the playback queue, and the browser-source overlay all need to stay synchronized without asking a streamer to install or operate another local application.
Operating constraints
- The playback surface must work as a browser source inside common streaming software.
- Dashboard and remote-control actions must reach an already-running overlay with little friction.
- Twitch authentication, clip data, chat commands, and channel-point events depend on external APIs and event delivery.
- Free and paid capabilities need explicit entitlement checks without splitting the product into separate experiences.
The approach
I separated the product into clear operating surfaces: a dashboard for durable configuration, a lightweight overlay for playback, and a live controller for moment-to-moment actions. Server-side resource boundaries connect overlays, playlists, queues, creators, and collaborators; real-time messages then carry only the state changes the active player needs.
System outline
01
Next.js application with typed server actions and a Drizzle-backed relational data model.
02
Dedicated overlay and controller routes connected through a real-time WebSocket channel.
03
Twitch authentication and EventSub-driven integrations for channel activity and rewards.
04
Permission and entitlement boundaries for owners, collaborators, and plan-specific resources.
Selected decisions
01
Separate setup from live operation
The dashboard owns configuration; the controller exposes immediate playback actions; the overlay remains focused on rendering. Each surface stays legible for its actual job.
02
Treat playback as shared state
Queues, mute and visibility changes, and manual clip actions are coordinated through server-side state and real-time messages instead of relying on one browser tab.
03
Model access at the resource boundary
Overlay and playlist operations check ownership, collaborator permissions, and retained plan access so team workflows do not require account sharing.
04
Keep the viewer-facing runtime lean
The browser source receives the information required to play and present clips while management, billing, and account concerns stay outside the broadcast surface.
The result
Clipify ships as a hosted, open-source product with plug-and-play browser-source overlays, reusable playlists, multiple playback strategies, a live remote controller, Twitch channel-point integration, and collaborator workflows. The result is one coherent system spanning creator setup, event handling, playback, and live operation rather than a collection of disconnected streaming utilities.