Bitfocus Companion
Companion solves a problem that shows up in real productions constantly: too many systems, too many clicks, not enough fast control. When it is built well, it saves serious time. When it is built badly, it becomes one more thing to babysit.
This page exists to help you understand how Companion fits into a real workflow, not just how it works.
What it is
Bitfocus Companion is control software that turns a Stream Deck or similar surface into a production control panel. It uses modules to connect to devices and software, then lets you trigger actions, feedback, presets, and macros from one place.
What problem it solves
It gives one operator a faster way to control several systems at once. That is the real value. It is not about having pretty buttons. It is about getting switching, playback, graphics, PTZ, audio, and automation into one workflow that is faster to operate under pressure.
When to use Companion
- When a Stream Deck needs to become more than hotkeys.
- When one operator needs to trigger ATEM, vMix, OBS, graphics, PTZ, or playback from one surface.
- When you want macro-style control across several systems without building a custom control stack.
- When a small team or volunteer team needs faster control than the default app interfaces give them.
When not to lean on it too hard
- When the base workflow is already fragile and you are trying to patch over it with buttons.
- When module support for your exact devices is weak or inconsistent.
- When the page design is becoming a logic maze instead of an operator aid.
- When the production should still be safe and understandable without Companion in the loop.
Common problems people run into
- Too many devices to control manually: This is exactly where Companion earns its place. If you need to know whether device support exists before you build anything, check the official Bitfocus connections list first.
- No unified control workflow: Companion helps when the problem is real operational friction, not just button envy. Use the Companion Quick Builder if the next problem is turning that idea into a cleaner operator page and you are comfortable testing an evolving workflow.
- Modules exist but workflows are messy: Module support is only step one. The hard part is building something an operator can read under pressure. That is where the Companion Quick Builder helps more than another page full of improvised buttons, but it now lives in Beta Builds because it is still evolving.
- Stream Deck setup takes too long: When setup time is the pain, check support with the official Bitfocus connections list first and then move into the Companion Quick Builder for testing instead of starting from a blank page.
These are the clearest Companion-related next steps still worth opening from this site.
Strengths
- Massive integration support is the whole point.
- One button can trigger several systems, which is exactly why people keep using it.
- It can make a modest setup feel much more capable without buying a real hardware panel for every job.
- In compact control rooms and live event setups, it removes a huge amount of interface friction.
Weaknesses
- Modules are not all equal. Some are excellent. Some are just good enough.
- Bad page design creates bad operation. Companion does not save you from poor workflow thinking, which is why the Companion Quick Builder only matters if it helps you get to a clearer page faster without pretending the workflow is fully solved.
- It is easy to build something that only makes sense to the person who made it.
- When the job gets complicated, maintenance and operator clarity matter more than button count. If you are still trying to figure out whether support exists for a device at all, use the official Bitfocus connections list first.
Real-world context
Companion is genuinely cool because it solves a real operational problem. It is at its best when it makes a system simpler. If it makes the system harder to understand, then the tool is not the real problem. The page design is.