Skip to content
LogosPilot
Request private preview

Presentation platform

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.

6

stages in one workflow, each handing off to the next

2

production applications certified end to end, at named versions

0

words of Scripture LogosPilot writes, ever

Product preview in preparation

The authenticated product view for this section is being captured from the current build. We do not substitute a mock interface, so the workflow is described in full below instead.

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
StageWhat happensHands off to
SpeechRoom audio is transcribed as the message is deliveredScripture detection
ScriptureA spoken reference is matched, and the passage retrieved from the licensed sourceSlide preparation
SlidesA candidate slide is composed for the display it is going toDisplay control
DisplaysContent is delivered to each configured output independentlyRecording and broadcast
RecordingAudio is captured with markers and a timeline, then finalized with a checksumYour archive
BroadcastProgram content is sent to your production softwareYour 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 LogosPilot does when it is not confident A message node on the left. Two routes leave it. The upper route completes and reaches a node reading Passage on screen. The lower route is cut partway along, beside the words not confident, and reaches a dimmed node reading Nothing displayed. Message Passage on screen not confident Nothing displayed
Conceptual illustration. The lower route is what happens when a match is uncertain: nothing reaches a display, and the operator keeps a working system.

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
RoleTypically shows
CongregationWhat the room sees
StageContent for the person speaking
ConfidenceA monitor for the platform
LobbyAn auxiliary display outside the auditorium
NurseryAn auxiliary display for another room
OverflowA 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 desktop application on the machine in your booth. Prepared Scripture, the displays and recording keep working without a connection; speech recognition needs one.

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.

How much of this has been tested

Everything above is present in the product. Some of it has also been independently demonstrated, and the difference is worth stating rather than blurring.

Confirmed on pixels, not on a response

An integration can report success while nothing reaches the screen. Our rendering case was confirmed by capturing the window and checking what was actually displayed — not by trusting the API that said it worked.

Certification covered four areas end to end: rendering, recording, recovery, and connection health. Five cases were deliberately not performed, and five of the ten shipped capabilities have not been through certification at all. Which is which is published in full on what has been validated, and the certification record itself — including everything it did not cover — is on Certified integrations.

What LogosPilot does not do

Three boundaries that matter when deciding whether this is the right product. All are deliberate.

LogosPilot displays Scripture. It never writes it.

Passage text is retrieved from the licensed translation you selected and displayed exactly as published. LogosPilot does not generate, paraphrase or reconstruct Scripture text under any circumstance.

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

Encoding, switching and streaming stay where they belong — in the production software your team already runs.

LogosPilot runs the room, not the office.

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

Read all ten boundaries

Where to go next

Go deeper

Run it through a service

LogosPilot is in private preview. If you run services on a schedule and want to evaluate it against your own room, the licensing route reaches a person.

Request private preview View system requirements