Everything you need to know about ModCockpit – from setup to security.
ModCockpit is a platform that allows your Twitch moderators to securely remote-control your OBS Studio from their browser. You install an OBS plugin, your mod opens our web cockpit — and can then switch scenes, mix audio, toggle sources and much more in real time. You decide exactly what your mod is allowed to do. No access to your PC, no port forwarding, no complicated setups.
ModCockpit offers two connection methods:
Method 1: Session Code (for spontaneous help)
You know this from other remote support tools — you share a code, your counterpart enters it:
Perfect for one-time help or when someone needs to jump in spontaneously. Your mod doesn't need an account for this (guest session, 15 minutes).
Method 2: Permanent Pairing via Portal (for regular mods)
For mods who help regularly:
You'll still be notified when a paired mod joins and can kick them at any time. If you prefer, you can also require paired mods to be confirmed each time.
Everything runs over an encrypted connection. Your mod doesn't need access to your PC, no port forwarding, no complicated setups.
What exactly your mod is allowed to do is controlled by the permission system. You can completely lock or partially restrict individual areas.
Absolutely! You don't need a mod for this. Just enter your own session code on a second device (tablet, phone, laptop) and control your OBS from there. The cockpit is responsive and works on all screen sizes.
Typical use cases:
ModCockpit requires OBS Studio 30 or newer. Older versions are not supported because the plugin uses newer OBS APIs.
No, currently only with the original OBS Studio. Streamlabs Desktop (formerly SLOBS) and other OBS forks don't support native OBS plugins.
However: If you use the "Streamlabs Plugin for OBS Studio" (i.e. OBS Studio with the Streamlabs plugin), you're automatically compatible — because it's regular OBS Studio under the hood.
We generally recommend OBS Studio — it's free, open source and has all the features you need.
ModCockpit is currently in closed beta. During the beta, usage is free.
Three tiers are planned:
Exact pricing will be announced before the official launch. Beta testers will be notified in advance.
No! For mods who help regularly, there are permanent pairings. You invite your mod once via the portal (using an invitation link or invite code, valid for 24 hours). After that you're permanently connected.
When you start OBS, your paired mod immediately sees "Streamer is online" in the portal and can connect with one click — no code, no confirmation. Permissions are automatically applied as you configured them once.
Session codes are still available — for spontaneous help or when a new mod needs to jump in quickly.
ModCockpit works fundamentally differently from traditional remote access software. Your mod does NOT connect to your PC, but to our server. The OBS plugin also connects to our server. The server only forwards OBS commands that the mod is allowed to send.
You can set exactly what each mod is allowed to do. Not just "all or nothing", but 4 categories with graduated levels:
For example, if you set "Scenes: Current scene only", the mod will only see sources and audio from the LIVE scene — no other scenes, no screenshots of them, nothing. This automatically restricts everything else.
There are also preset profiles you can quickly assign ("Basic Help", "Audio Mod", "Trusted Mod", etc.) or you can create your own.
When are permissions assigned?
When you kick a mod, only the mod is removed — your session stays active with your code. You can immediately invite another mod or the same mod can reconnect (needs to be confirmed again). You always keep full control.
Only if you have sources that show your desktop (e.g. "Display Capture" or "Window Capture") and the mod has permission to see those sources. With the permission system you can restrict what's visible. If you set "Scenes: Current scene only", the mod only sees the live scene — no previews of other scenes that might contain desktop captures.
Generally: ModCockpit shows the mod thumbnails of your OBS scenes and sources. If a source shows a window or display, it's visible in the thumbnail. Plan your scenes accordingly if privacy is important to you.
Data privacy at ModCockpit is not a marketing promise, but a core principle. The founder is an IT and data privacy expert himself.
You can find the complete privacy policy on our Privacy Policy page.
ModCockpit only stores the minimum:
OBS data is only transmitted in real time and NOT stored on our servers:
ModCockpit has automatic reconnection. If your connection briefly drops (under 2 minutes), the plugin automatically reconnects and your mod stays connected. If the outage lasts longer than 2 minutes, the session ends and you get a new code on restart.
During a brief outage, your mod sees a notice "Streamer temporarily offline — reconnecting automatically".
That's what the permission system is for. You can set exactly what each mod is allowed to do. If you don't fully trust a new mod, give them restricted permissions — e.g. only mute audio and toggle sources, but no scene switching or stream stopping.
There are also preset profiles ("Basic Help", "Audio Mod", "Trusted Mod") you can assign with one click. And if something goes wrong: one click on "Kick" in the OBS dock and the mod is out immediately.
Important: All actions are validated server-side against the permission profile. Even if someone tries to send commands they're not allowed to — the server blocks them.
No. ModCockpit does not store any stream content — neither video nor audio.
The scene previews in the cockpit are small JPEG thumbnails (maximum 960×540 pixels), not full HD video. They are only transmitted in real time to connected mods and are never stored on our servers. Once the session ends, all data is gone.
Audio levels are also only streamed live — no recording, no replay, no archive.
There are two ways:
Via Session Code (spontaneous):
This works without an account too — as a guest session (15 minutes, restricted permissions).
Via the Portal (for paired mods):
Prerequisite: The streamer has previously invited you via the portal and you're permanently paired.
It depends on how you want to use ModCockpit:
Tip: You can also register DURING a guest session. The timer disappears immediately and the session continues normally.
Yes! The cockpit is responsive and works on smartphones and tablets. All features are usable on small screens too — audio mixer, scene switching, source control. Perfect when you need to jump in for your streamer on the go.
It depends on what permissions the streamer has given you. You can see your permissions in the cockpit. Typical scenarios:
If you send a command you don't have permission for, you'll get an error message. The streamer can adjust your permissions at any time.
Yes! You can start a Guest Session — just enter the session code without registering. You're connected in seconds.
Guest session limitations:
Tip: You can register at any time during a guest session (email or Twitch). The timer disappears immediately and the session continues normally — no interruption.
Yes! In the cockpit you can send a message to the streamer. It appears as a toast notification directly in the streamer's OBS dock — they don't need to check chat or open Discord.
Perfect for quick notes like "Mic is off" or "Switch scene?" when you're not sure whether to act yourself.
Linux (experimental, not officially supported): Copy the .so file to ~/.config/obs-studio/plugins/modcockpit/bin/64bit/.
No! ModCockpit uses outgoing WebSocket connections (like a normal website). No incoming ports are opened and no firewall rules are needed. The plugin connects outbound to our server — just like your browser.
You can connect up to 16 mods simultaneously in a session. Each mod gets their own permissions via the permission profile system.
Latency is minimal — typically under 100ms. Scene switches, mute commands and other actions execute almost instantly.
Previews also update in real time — using a 4-tier system that intelligently distributes bandwidth:
A macOS version of the plugin is planned but not yet available. Currently only Windows is officially supported. An experimental Linux build exists but is not officially supported.
The web cockpit works on all operating systems of course — only the OBS plugin needs to run on the system where OBS is installed.
The plugin has automatic reconnection. If OBS crashes or you restart it, the plugin automatically reconnects to the server. If this happens within 2 minutes, the existing session is preserved — your mod only notices a brief interruption and is then reconnected.
If the restart takes longer than 2 minutes, the session ends and you get a new code on next startup. For permanently paired mods this isn't a problem — they simply reconnect via the portal.
Audio Intelligence is a feature set that automatically monitors and optimizes your stream's audio quality. The analysis already runs in the OBS plugin — dashboard controls are coming in Phase 2:
Audio analysis and detection is already implemented in the OBS plugin. Control via the mod dashboard (configuration, alerts, panic button) will be available in Phase 2.
Yes! ModCockpit supports two popular hardware audio mixers:
The mixers appear as dedicated panels in the mod cockpit. Your mod can adjust mic gain or change the monitor mix — without switching to the Focusrite or GoXLR software.
Requirement: The respective control software (Focusrite Control / goxlr-utility) must be running on the streamer's PC.
Yes! ModCockpit offers two ways for Stream Deck integration:
This lets your mod put frequently used actions on a single button press — switch scenes, mute mic, activate BRB screen.
Most likely not. The most common cause of crashes when closing OBS is obs-websocket (an OBS built-in plugin for remote control).
ModCockpit does not use obs-websocket — it uses its own native connection directly through the OBS plugin API. The two systems are completely independent.
Fix: If you don't need obs-websocket for other tools (e.g. Touch Portal, Bitfocus Companion), you can disable it: OBS → Tools → obs-websocket Settings → uncheck "Enable WebSocket server".
Yes! If the streamer has the Streamer.bot plugin installed, a bot dashboard appears in the mod cockpit with:
65 commands total — from simple bot actions to Twitch moderation (polls, predictions, raids, channel points).
Because software, hosting and development cost money. In return you get a product without ads, without tracking and without data sales.
You are the customer — not the product.
Many "free" tools finance themselves through your data. We don't. ModCockpit is funded through subscriptions — transparent and honest.
The free tier is permanently free and includes:
For most streamers who occasionally need help, the free tier is sufficient.
Mod slots determine how many mods you can permanently pair with. A pairing is a permanent connection between you and a mod with predefined permissions. Paired mods can connect anytime via the portal when you're online — no session code and no confirmation needed each time.
Spontaneous connections via session code (guest sessions) don't count against your slots — they always work regardless of your plan.
Yes, you can cancel your subscription at any time. It will then expire at the end of the current billing period. Your account remains active and is downgraded to the free tier. Your pairings are preserved, but only the first slot remains active.
ModCockpit will offer three tiers:
During the closed beta, usage is completely free. Beta testers will be notified well in advance before paid tiers are introduced.
Still have questions? Email us at kontakt@modcockpit.tv or join our Discord community.
Get beta access