One platform, one workflow

LogosPilot is not a set of features that happen to ship together. Speech, Scripture, slides, displays, recording and broadcast are stages of a single workflow, and each one hands off to the next.

ASSET REQUIRED · E1-PRODUCT-01

Screenshot: LogosPilot operator view at rest, before a service, showing configured displays and the selected translation. Real shipped build.

The workflow

A service moves in one direction: someone speaks, something should appear on a screen, and a record of it should exist afterwards. LogosPilot is built along that line rather than across it.

How one stage hands off to the next
Stage	What happens	Hands off to
Speech	Room audio is transcribed as the message is delivered	Scripture detection
Scripture	A spoken reference is matched, and the passage retrieved from the licensed source	Slide preparation
Slides	A candidate slide is composed for the display it is going to	Display control
Displays	Content is delivered to each configured output independently	Recording and broadcast
Recording	Audio is captured with markers and a timeline, then finalized with a checksum	Your archive
Broadcast	Program content is sent to your production software	Your encoder

Not every stage is autonomous

Scripture detection and slide preparation can run without an operator. Recording, broadcast connection and display configuration are things you set up and start. LogosPilot does not decide on its own to begin recording or to change what your production software is doing.

Where control stays

Automation prepares. The operator decides. That division does not move, and it is not a setting.

Every automated action can be stopped, and stopping it does not require finding a menu. When automation is stopped it stays stopped until someone starts it again.

If LogosPilot is not confident, it does nothing. An uncertain match produces no slide and no display change. The operator is left with a working system and a manual path, not a guess on a screen.

See the four steps in detail

What it drives

LogosPilot addresses displays by the role they play in the room, not by which port they happen to be plugged into.

Display roles LogosPilot can address
Role	Typically shows
Congregation	What the room sees
Stage	Content for the person speaking
Confidence	A monitor for the platform
Lobby	An auxiliary display outside the auditorium
Nursery	An auxiliary display for another room
Overflow	A second room carrying the same service

Each output carries its own content. A stage display can show something the congregation display does not.

Read the full capability list

What it rests on

It runs locally. A Windows desktop application on the machine in your booth. A complete service can run with no internet.

It is supervised. A watchdog monitors the running system and restarts components rather than leaving a service without output.

It is certified against exact versions. Broadcast integration was tested end to end at named versions, and those versions are published.

Nothing commercial reaches the room. License state never appears on a display a congregation can see, and never interrupts an event in progress.

What LogosPilot does not do

Where to go next

Go deeper

Run it through a service

The 30-day trial is the full product. Install it on the booth machine and run a real service with it. No account, no payment details.

Start free trial View system requirements