Self-hosted · Docker · Linux & Windows · OBS 28+

One dashboard for everything that used to take five tools and a walkie-talkie

Production-grade visibility and control for church media teams. Monitor your stream, control your presentation, catch problems before your audience does.

STANDBY
Sunday Service
Stream
0.0 Mbps
Audio
0 LUFS
L
R
Systems
OBS
—
Encoder
—
YouTube
—
Network
—
01 / During the service

See everything that matters, in real time

Stream health, audio levels, encoder load, network status, scene state. The dashboard answers "is everything okay?" at a glance — no tab-switching, no guessing.

[Real dashboard screenshot — Phase 3 Week 14 complete]

02 / Works with what you run

Connects to your existing stack

Opsis is the operational layer around the tools you already use — not a replacement. Honest integration tiers, no surprises after install.

OBS Studio

CONTROL

Full control + real-time monitoring via obs-websocket 5.x

FreeShow

CONTROL

Scripture and presentation control — Opsis drives the cues

BibleShow

PASSIVE

Passive monitor only — read current slide, no control

YouTube

PUBLISH

Publish clips + poll viewer comments via Data API v3

Facebook

PUBLISH

Page video uploads + comment polling via Graph API

NDI

MONITOR

mDNS discovery — see sources on the network, no SDK

WhatsApp

ALERT

Critical alerts only — reaches operators away from the booth

03 / When it goes wrong

Alerts that tell you what to do, not just what's red

Something will break mid-service. When it does, Opsis names the fault, explains why, and tells you the fix — so a first-time volunteer can act on it without the tech director in the room.

Warning10:42:15

Bitrate has dropped below the expected range

Current: 4.2 Mbps · Expected: 6-8 Mbps · Check encoder settings or network connection

Healthy

Everything running within expected parameters

Warning

Degraded — not critical yet, but needs attention

Critical

Service interrupted — immediate action required

Degrade, don't crash: A failed integration never takes down the monitoring core. If BibleShow disconnects, you still see your stream health.

04 / After the service

From recording to published clips, with you in control

AI proposes clips from the transcript. You approve. It publishes to YouTube and Facebook. Viewer comments come back correlated against your telemetry — so you know if "audio cut out" happened at 10:42 and what your systems saw at 10:42.

Recording ends
AI proposes clips
Human approves
Publish to platforms

AI is a layer on top of a fully functional non-AI core — never a dependency. The production monitoring works without it.

05 / What you run

One machine, one command, minimal footprint

Self-hosted on Docker. Runs on the same machine as OBS or on a dedicated mini-PC. No cloud dependency — your data stays on your network.

Measured footprint

Memory at idle<200 MB
CPU at idle<5%

Verified by scripts/measure-footprint.sh in the repo

Requirements

  • Docker (or Podman)
  • Linux, Windows, or macOS
  • OBS Studio 28+ with WebSocket enabled
  • 2GB RAM minimum

Current status

Phase 3 complete. Monitoring, control, clips, publishing, and viewer feedback are all shipping. Not yet publicly released — request access below to join the early install program.

06 / Get started

Ready to try it?

Opsis is in early access. Request access to join the install program — or watch a full Sunday run to see it in action first.

Self-hosted · Docker · Linux & Windows · OBS 28+

[CTA form pending — awaiting decision on request-access vs. public repo vs. hosted demo]