For the person who has to approve it
LogosPilot for church IT
What installs, what connects, what stays on the machine, and what your network has to allow. Where something has not been decided or tested, this page says so rather than guessing.
What it is
| Question | Answer |
|---|---|
| What kind of application? | A desktop application. It runs on the machine at the desk, not in a browser and not on our servers |
| Where does it run? | On one machine in the room — the desktop host |
| Does it need our server to operate? | No server of yours. Speech recognition and commercial translations need an outbound internet connection |
| Supported platforms | Windows is in private preview. macOS is planned and not yet certified. See system requirements |
| Is there an installer today? | No. No signed release has been published on any platform yet |
Nothing is downloadable yet
This page describes how LogosPilot is built to behave, so you can assess it before a release exists. There is no installer to evaluate today, and nothing on this site offers one. Access is arranged by private preview request.
What stays on the machine
The design point most relevant to a review: the work happens on the desktop host, not somewhere else.
| Function | Where it runs |
|---|---|
| Speech recognition | Off the machine. Room audio is sent over an encrypted connection while recognition is running |
| Scripture display | Locally. Passages you have prepared are available with no connection |
| Display output and routing | Locally, driven by the graphics hardware in the desktop host |
| Recording | Locally. The finished file and its checksum are written on the machine |
| License validation | In the background, on a signed lease. It never blocks the start of a service |
Scripture is retrieved and displayed, never generated
Passage text is presented exactly as published. LogosPilot does not compose, paraphrase or generate Scripture, and no plan or agreement changes that.
What it connects to
| Vendor | Version certified | Transport |
|---|---|---|
| OBS Studio | 32.1.2, obs-websocket 5.7.3 | WebSocket 4455 |
| vMix | 29.0.0.48 | TCP 8099 |
Both connections are to production software you already run, normally on the same machine or the same local network. LogosPilot drives your production software; it does not replace it, and it does not encode or host video. What certification covered, and what it did not, is published on Integrations.
What your network must allow
| Activity | Connection needed |
|---|---|
| Running a service | For speech recognition and commercial translations. Prepared Scripture, the displays and recording continue without one |
| Activating a license | An outbound internet connection is required |
| License validation during a service | None. Licensing does not need to reach us during an event |
| Driving OBS or vMix | Local network or loopback, on the transports above |
Offline is the design, not a degraded mode
LogosPilot operates on a signed lease. A license that cannot reach our servers does not stop your event — it reconciles afterwards. A license condition that becomes true mid-service is recorded and applied when the service ends, and never appears on a display a congregation can see.
Licensing and activation
| Action | What happens |
|---|---|
| Unit | The desktop host — a machine running LogosPilot and holding an activation. Not per person |
| Activation | Binds the license to one machine and counts against your allowance |
| Replacing hardware | Deactivate the old machine, activate the new one. No limit on how often |
| Deactivation | Frees the allowance immediately |
| Renewal | Extends the license without a reinstall. Content and settings are untouched |
| If a license lapses | Existing recordings stay available to view and export. What stops is starting new production |
The licensing model is documented in full on Licensing help, which is the authoritative description. Commercial terms are being finalized and no plan figures are published yet.
No payment details are handled by LogosPilot
When commercial purchase opens it will run entirely through a single external payment provider. LogosPilot will not collect, process or store payment information, and this website contains no payment form of any kind.
Updates and verification
No release has been published yet, so there is no update history to show. What every release will carry when it exists is already defined and published.
| Item | Purpose |
|---|---|
| Checksum | So you can confirm the file you have is the file we published |
| File size | A second, independent check on the same file |
| Digital signature status | So you can confirm who published it |
| Release notes | What changed, and any behavior that differs from the previous release |
The verification procedure is written out on Verify your download, and the release record will appear on Release history.
Deployment
| Question | Answer |
|---|---|
| How many machines? | One desktop host per room running a service. Tablets can pair as companions; the desktop host stays authoritative |
| Multiple sites | Each site runs its own desktop host. Multi-campus broadcast still runs through your production software at each site |
| Central license administration | Available under an Enterprise agreement. See Enterprise |
| Deployment planning | Offered as part of an Enterprise agreement |
If something goes wrong
| Situation | What happens |
|---|---|
| Internet connection is lost | The service continues. Licensing does not need to reach us during an event |
| Audio source is lost | Transcription depends on it. Manual presentation remains available |
| Production software disconnects | Connection health is reported and reconnection is attempted. Behavior per vendor is on Integrations |
| License condition becomes true mid-service | Recorded and applied afterwards. Never shown on a congregation display |
| Hardware fails | Deactivate the failed machine and activate a replacement |
Not documented yet
These are questions a reviewer will reasonably ask that we cannot answer accurately today. They are listed rather than omitted, because an unanswered question you can see is more useful than one you discover later.
| Question | Status |
|---|---|
| Silent or unattended installation | Not documented. No installer exists yet, so no installation switches can be described honestly |
| Managed deployment tooling | Not documented |
| Exact outbound endpoints for activation | Not published. We will not describe a firewall rule we have not verified |
| Telemetry or usage reporting | Not documented. Treat as unanswered until we publish it |
| Where recordings are written by default | Documented in the product; not yet published on this site |
| Audio input specification | An audio source is required for transcription. No specific device requirement is published |
| Camera | No published capability requires one |
| Recovery time objectives | Not set. No recovery commitment is published, so none should be assumed |
| Support response times | Not published. No response commitment exists yet |
Ask, and you will get the real answer
If your review needs one of these before you can proceed, write to support@logospilot.com and say which. You will get either a verified answer or a plain statement that it has not been determined — not a plausible one.
What it will never do
These are boundaries, not gaps in a plan. They do not change with plan, scale or agreement.
| Not included | What owns it instead |
|---|---|
| Service planning, volunteer scheduling, attendance, membership, giving, accounting | Your church management system |
| Song library, lyrics management, CCLI reporting | Your worship software |
| Encoding, switching, streaming, video hosting | Your production software and encoder |
| Writing or generating Scripture text | Nothing. Passage text is retrieved and displayed exactly as published |
The full list, and the reasoning behind it, is on About. How this software is verified before it reaches you is on How we build.