Skip to content
LogosPilot
Request private preview

Tested, at named versions

Certified integrations

LogosPilot drives the production software your team already runs. We publish the exact versions we tested, what the testing covered, and what it did not.

What certified means here

Certified means we tested that vendor, at that version, end to end, and recorded the result. It is not a synonym for compatible, supported, or works with — those words imply a guarantee nobody verified.

If a version is not on the list below, we have not tested it. It may work. We are not going to claim it does.

Certified vendors and versions

Vendors and versions certified end to end
VendorVersion ProtocolTransport Edition tested
OBS Studio32.1.2 obs-websocket 5.7.3WebSocket 4455—
vMix29.0.0.48 —TCP 8099Trial
Certification result
Vendor certification, both vendors, simultaneously

21 of 21 cases passed

Certification host
Windows 11 Pro, build 26200
Cases passed
21 of 21
Cases not performed
5 — listed below

What was tested

Certification was performed against the real products, both running at the same time, on one machine. These are the results that matter most.

Certification results by area
AreaResultHow it was proven
RenderingPassed Scripture delivered end to end into a vMix Browser Input, confirmed on pixels by window capture rather than by an API reporting success
RecordingPassed A witnessed take produced a valid, finalized, playable file. Success was reported only after the vendor confirmed its own state
RecoveryPassed A controlled disconnect and reconnect, with the session continuing
Connection and healthPassed Connection, status reads and health reporting against both vendors

Why pixel confirmation matters

An integration can report success while nothing reaches the screen. The rendering case was confirmed by capturing the window and checking what was actually displayed, not by trusting the response.

What certification did not cover

Five cases were deliberately not performed. Publishing them is more useful than implying the certification was exhaustive.

Not performed during certification
Not testedWhy
Starting and stopping a live streamStreaming to a real platform was excluded by instruction. Status reads were certified
Instant-replay playbackThe certification preset had no replay input configured
Removing a browser input through the driverA known gap in the control contract
Operating both vendors across two machinesCertification ran on a single host
Sessions longer than one hourCertification runs were shorter than an hour

Edition and version scope

vMix was certified against the Trial edition. Behavior that differs on higher editions — including 4K-specific behavior — was not verified. Two smaller vendor-side quirks were also recorded during testing and are covered in the documentation.

Other production software

Only the two vendors above are certified. Other production software may work with LogosPilot. We have not tested it, so we do not list it and we do not claim it.

Deployment and security

Broadcast integrations work by one program controlling another over the network. That has a consequence worth understanding before you deploy.

If you use vMix, read this before you deploy

vMix exposes two control surfaces that are unauthenticated — a TCP interface on port 8099 and a web controller on port 8088. Anything that can reach the host can drive the switcher. This is how vMix works; it is not something LogosPilot introduces or can change.

Keep the host off untrusted networks, and do not port-forward 8099 or 8088. We found this during certification and we would rather you knew.

Keep production on a controlled network. The booth machine and your production software should sit on a network you manage, not a guest network and not the open internet.

Broadcast failure never stops the room. If a connection to your production software drops, the local presentation continues unaffected. The failure is reported to the operator, not to the congregation.

What LogosPilot does not do

LogosPilot drives your production software. It does not replace it.

LogosPilot sends what the congregation sees to OBS Studio and vMix, certified against exact versions. The encoding, switching and streaming stay where they belong — in the production software your team already runs.

LogosPilot records your service. Editing happens in your editor.

Recordings are captured with markers and a timeline so they are ready to work with, and finalized with a checksum. LogosPilot hands you the file; it does not edit it.

LogosPilot controls what is displayed, not what is filmed.

Camera movement and switching remain with your production team and their equipment.

Where to go next

Related

Test it against your own setup

Preview access includes both certified integrations. LogosPilot is in private preview; the licensing route reaches a person who can talk about your chain.

Request private preview Read documentation