Selected candidates will soon be able to give the suite a real world test run and provide their feedback and opinions!
CRESA // STREAM AUTOMATION
WHAT IS CRESA?
Your stream has a lot of moving parts. CRESA is being built to make them work together.
CRESA is an integrated control, automation and presentation system for OBS Studio. It brings alerts, capture, scenes, media, diagnostics and other broadcast tools together as parts of one coordinated suite.

WHY DOES CRESA EXIST?
Streaming gets complicated fast.
OBS handles the broadcast, but a modern stream can also depend on alerts, capture tools, music, browser sources, automation and diagnostics. Those pieces can all work, while knowing very little about what the others are doing.
A collection of useful tools, each largely doing its own thing.
Give the systems around the broadcast enough shared context to cooperate.
WHAT CAN IT DO?
One suite, built around the broadcast.
CRESA is still actively being developed. These are the areas the suite is being built to bring together, not a claim that every part is finished.
Control your broadcast
Bring common broadcast actions and feature controls into a central operator experience inside OBS.
Alerts & viewer events
Coordinate follows, subscriptions, bits, redeems and other viewer activity through a shared alert system.
Smarter game capture
Work with OBS capture systems, remember useful configurations and understand whether the expected game feed is healthy.
Stream presentation
Build intentional Starting Soon, BRB, idle and other presentation states around what is happening on stream.
Media & music
Coordinate media information, presentation and broadcast audio integration as part of the wider stream.
Health & recovery
Tell normal inactivity apart from something that needs attention, then provide useful diagnostics and recovery paths.
Safe testing
Simulation Lab provides controlled ways to exercise supported features without waiting for the real viewer event.
A little personality
Features such as Mini Me turn otherwise idle parts of the broadcast into something intentional and recognisably CRESA.
ONE STREAM · ONE CONNECTED SYSTEM
The important bit is how the pieces work together.
CRESA is not just about putting more buttons in front of a streamer. The goal is for different parts of the suite to understand what the broadcast is doing and respond appropriately.
You start a game
CRESA can work with the appropriate OBS capture configuration and understand what should be on screen.
Someone follows
The viewer event enters the alert system and the appropriate presentation is handled as part of the broadcast.
You step away
BRB and other presentation states can represent that change intentionally instead of leaving an unexplained feed.
Something goes wrong
Health systems can distinguish normal inactivity from a state that actually needs attention.
You change direction
The suite can respond to updated broadcast context instead of every feature operating in isolation.
BUILT AROUND OBS STUDIO
CRESA does not replace OBS.
It works with it.
OBS remains responsible for the core broadcast. CRESA integrates around it to add control, automation, presentation, testing and diagnostics.
The CRESA Control Centre is being developed as an operator experience inside OBS, so the suite does not have to feel like another unrelated application sitting beside your stream.
CRESA CONTROL CENTRE
One place to operate CRESA.
As the suite grows, operating every system separately stops making sense. Control Centre brings the operator-facing parts of CRESA together inside OBS.
AUTOMATION WITH BOUNDARIES
Useful automation should not mean giving up control.
CRESA can react to broadcast state and automate repetitive behaviour, while important actions still have clear authority and safety boundaries.
If CRESA cannot prove that a protected test or action is safe to perform, it can refuse rather than guess.
Supported systems can be exercised in a controlled way before you rely on them during a real stream.
BUILT TO FAIL SAFELY
Knowing when not to act matters too.
CRESA is being designed to treat uncertainty differently from a confirmed safe state. Recovery and diagnostics are being developed alongside features, so a problem can be explained and handled instead of simply becoming another dead source on screen.
DEVELOPMENT IS PUBLIC
You can watch it being built.
Rather than hiding behind a coming soon page, CRESA Development Live documents the journey as the suite is built, tested, broken, repaired and improved.