The beta opens in a few days
A live event shouldn't depend oneverything going right the first time
StagePaz puts words, text and video on your room's screens, and it's built for the moment when whoever is running it is doing it for the first time and is alone in the booth.
The day of the event
The problem is rarely the software. It's everything around it.
The person who knew how to run it didn't come this week. What someone asked for last night isn't ready. Whoever is speaking goes off script and asks for something else halfway through. The projector went off, and when it came back the screens were rearranged.
And all of it happens in front of a full room, with the sound running, with no way to say "hold on, I'm restarting".
The worst case isn't that it looks bad. It's that people notice.
A blue screen while the room waits. A slide stuck on a moment that has already passed. Software that decides to update itself right before you start and asks to restart.
Nobody remembers the forty times it went fine. Everybody remembers the minute people stopped looking at the front and started looking at the screen.
Why this is different
Written by someone who knows what a failed live event costs.
We don't just say it — it shows in the decisions, and each one is written down with why.
- The phone remote ships turned off.Opening a port on someone else's network has to be somebody's decision, not something that happens on install.
- Updates don't install while anything is running.With something projected, NDI sending or a phone connected, StagePaz doesn't check, doesn't download and doesn't nag. And if the new version won't open, it rolls back by itself.
- Saving can't lose your work.If the file fails to write, a rescue copy is made and you're told where it is, instead of closing as if nothing happened.
- 1,304 automated tests run before every release, performance ones included: moving between slides with a warm cache does zero drawing work, and a still frame of the stage monitor went from 4.93 ms to 0.90 ms.
The solution
A console built for the booth, not for a boardroom.
IT ALL COMES FROM ONE COMPUTER
One laptop in the booth.
Five destinations.
One application. Your whole church connected.
StagePaz runs on one laptop, sending independent feeds to audience and stage over HDMI, streaming over NDI and browser screens on the local network. The PIN-protected mobile remote controls every output.
StagePazAudience
HDMIStage
HDMIStreaming
NDI · NETWORKBrowser screens
BROWSER · LANMobile remote
BROWSER · LAN · PIN- 🖥️Two outputs, each on its own terms
The room sees the content. Whoever leads also sees what's next and their notes.
- 📖Bible built in
Type "John 3:16-18" and project it. 1,294 versions across 1,024 languages.
- 📥Import what you already have
ProPresenter, OpenLP, OpenSong, Holyrics, ChordPro, Word and plain text.
- 🔎Search by content
Ask for a line you half remember and it comes up. Accents ignored, any order.
- 📋The running order, as a list
Songs, text, images and video. Arrow keys chain through it and it saves itself.
- 📱Remote through a browser
A server on your local network with a PIN. Nothing to install, never leaves the LAN.
- 📹Cameras and NDI output
Camera boxes inside your themes and several outputs at once, each with its own.
- ⏱️Countdowns and notices
Projectable timers, including "until a set time", so you start on time.
Room and stage
Two screens that don't show the same thing — that's the whole point.
Almost everyone starts with one: the projector. The second one is what changes how a live event is run.
Audience
What the room sees: text, words, background video, camera. Its own theme — typeface, margins, shadow — and its own group of screens, because the hall may have two projectors and a TV at the back.
Stage
What the person running it sees, with their back to the projector: the current slide,the next one, the notes the team left, and the clock or countdown. Nobody has to turn around and read the big screen to know what's coming.
And both clear together: going to black is one key, and it never leaves one screen dark and the other stuck on the previous verse.
How it works
Half an hour on a quiet day, and it's set up.
- Bring your material. File → Import folder, and point it at whatever you used before. It works the format out on its own.
- Say which monitor is which. Which one is the projector and which is the stage display. With only one, leave stage unassigned.
- Build the running order by dragging in what's going out, in order.
- On the day, arrow keys. And the phone from the lectern if you need it.
Where it's used
If there's a screen and people in front of it, it fits.
It was written for the most demanding case there is on the smallest budget: volunteer teams that rotate every week and can't afford a rehearsal. What holds up there holds up anywhere.
- Churches and communities
- Schools and universities
- Conferences and congresses
- Theatres and assembly halls
- Broadcast and streaming
- Corporate events
The next step is leaving an email.
We'll tell you the day the beta is downloadable. For that only: no newsletter, nothing to anyone else.
Compared with how it's done today
| Today | With StagePaz |
|---|---|
| Slides made by hand the night before, one deck per item. | A song is written once and projected forever. |
| Someone asks for something last minute and you look it up and retype it. | Type the reference and it appears, in your version and your typography. |
| Whoever runs it can't see what's coming next. | The stage monitor shows the next slide and the notes. |
| Software in English only, licensed yearly and per machine. | Spanish and English, and your data in a folder of yours. |
| Moving to another computer means setting it all up again. | A backup is one file, and restoring never overwrites. |
What we guarantee
- Your work is yours. Everything lives in
Documents/StagePaz, on your computer. No accounts, no mandatory cloud. - It works offline. The event doesn't depend on the venue's wifi. It only goes out to the network to fetch a Bible version or an update, and always because you asked.
- Leaving is easy. A backup is a single file, and if one day it isn't for you, delete the folder and nothing is left behind.
- If something breaks, we answer. During the beta you write to hola@stagepaz.com and the person who writes the code answers — not a form.
Proof
Nobody is using it yet. That's what the beta is for.
This is where others would put three testimonials. We don't have them and we're not going to invent them: you'd be trusting a live event to this, and you deserve to know exactly where it stands.
What we can show is the work:
When teams are using it, this gap will be filled with their words, not ours.
From here
If you do nothing
The next event gets put together like the last one. And the team still depends on the one person who knows how being able to show up.
If you leave your email
You get a note when the beta opens, you install it in half an hour on a quiet day, and you try it on a real event before deciding anything.
And if you think it through
Joining costs an email. The beta costs nothing. Bringing your material is pointing at a folder. And if it doesn't convince you, delete it. The risk is zero and what you gain is not improvising.
An honest note: the beta opens in a few days and invitations go out by email, in order. There are no limited seats and no countdown; it's just that whoever isn't on the list hears later — and whoever comes in first is the one who can ask for something to work differently while it's still being decided.
Leave your email and we'll tell you.
One email, one note, nothing else.