Certified integrations

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
Vendor	Version	Protocol	Transport	Edition tested
OBS Studio	32.1.2	obs-websocket 5.7.3	WebSocket 4455	—
vMix	29.0.0.48	—	TCP 8099	Trial

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
Area	Result	How it was proven
Rendering	Passed	Scripture delivered end to end into a vMix Browser Input, confirmed on pixels by window capture rather than by an API reporting success
Recording	Passed	A witnessed take produced a valid, finalized, playable file. Success was reported only after the vendor confirmed its own state
Recovery	Passed	A controlled disconnect and reconnect, with the session continuing
Connection and health	Passed	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 tested	Why
Starting and stopping a live stream	Streaming to a real platform was excluded by instruction. Status reads were certified
Instant-replay playback	The certification preset had no replay input configured
Removing a browser input through the driver	A known gap in the control contract
Operating both vendors across two machines	Certification ran on a single host
Sessions longer than one hour	Certification 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

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.