Skip to content
LogosPilot
Request private preview

LogosPilot for churches

A weekly service, run by volunteers, in a room where a mistake is visible to everyone present. That is the situation LogosPilot was built for.

The environment

Most churches run the same service shape every week, with a rotating group of volunteers at the desk. The person operating today may not have operated last month.

What matters is not how much the software can do. It is how little has to be remembered, and how quickly someone can take control when something is wrong.

LogosPilot assumes the operator is new. Automation prepares, the operator decides, and stopping automation is always one action in the same place.

It also assumes the network will fail at some point. A complete service can run with no internet at all.

Relevant workflows

Three of the five supported workflows carry most weekly services.

Workflows that matter most here
WorkflowWhat it does here
Autonomous ScriptureA spoken reference is matched and the passage appears on the congregation display. Low confidence shows nothing rather than guessing
Service with recordingAudio is captured with markers and a timeline, then finalized with a checksum so the file can be verified later
Offline servicePrepared Scripture is available locally and licensing runs on a signed offline lease. Nothing about the service changes

Applicable capabilities

These are the same capabilities every LogosPilot install has. Nothing below is specific to this environment — only the emphasis is. The capability list is defined here.

  • Multi-display output. Congregation, stage, confidence, lobby, nursery and overflow are addressed as roles, each carrying independent content.
  • Multi-campus. Each campus operates independently. A synchronization problem at one does not stop another running its own service.
  • Tablet companions. A paired tablet extends the operator’s reach into the room. The desktop host stays authoritative.
  • Supervised runtime. A watchdog restarts components rather than leaving a service without output.
  • Nothing commercial reaches the room. A license condition never appears on a display a congregation can see, and never interrupts a service in progress.

Certified integrations

If you stream your services, LogosPilot sends program content to the production software your team already runs.

Certified vendors and versions
VendorVersionProtocolTransport
OBS Studio32.1.2obs-websocket 5.7.3WebSocket 4455
vMix29.0.0.48—TCP 8099

21 of 21 certification cases passed

See what certification covered, and what it did not

What LogosPilot does not do

Churches already run software for most of these. LogosPilot is not trying to replace any of it, and knowing that up front saves a wasted evaluation.

LogosPilot is built around the spoken message.

It does not maintain a song library, manage lyrics, or handle CCLI reporting. Those belong to your worship software, and LogosPilot works alongside it rather than duplicating it.

LogosPilot runs the room, not the office.

It does not plan services, schedule volunteers, track attendance, manage membership, handle giving or do accounting. Your church management system does that. LogosPilot starts when the service does.

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

It is not a streaming platform and it does not host your video. Program content goes to OBS Studio or vMix, and the encoding and streaming stay there.

LogosPilot is a Windows application.

It runs on the machine in your booth, not in a browser, and it keeps running when the network does not.

Read all ten boundaries

Where to go next

Related

Run it through a Sunday

The 30-day trial is the full product. Install it on the booth machine and use it for a real service before deciding anything.

Request private preview View system requirements