Church Production OS · A D2 Labs Product

Who's on. What they're on. Where they stand.

Everything the booth and the band need to run a service — mics, ears, patch, personal mixers, gear, crew, stage positions — live on every screen in the building, fed by the files your team already makes.

Join early access See the wall ↓
$80runs on a Pi you own
1 fileyour data · SQLite
2 files/wkPCO report + input list in
Every TVwalls · dashboards · Rokus
The wall

The backstage display your singers walk up to and your backstage manager watches all service. This one is live markup, not a screenshot — the countdown is really counting.

YOUR CHURCH SUNDAY · 9:00 & 11:00
01
LEADER
JR
Jamie R.
Acoustic & Vocals
Mic01 Red HH
MixVox 1
IEMPack 1
02
SK
Sam K.
Vocals
Mic02 Wht HH
MixVox 2
IEMPack 2
11
DG
Dana G.
Drums
MixDrums
InKit Mics
IEMWedge
05
Empty
 
Mic
Mix
IEM

Empties stay visible on the rack display so screen slot 05 is always charger 5. Every tile updates within 2 seconds of any change. At 1 PM Sunday the board clears itself.

The pitch

Planning Center runs the service. TechBooth runs the booth — and the stage.

Planning Center schedules the people and the songs. TechBooth runs everything they touch on a Sunday: assignments on backstage walls, the patch on the tech dashboard, QR-tagged gear, crew seats, and build-your-own dashboards for every TV in the building.

It replaces the whiteboard and gaff-tape labels, the spreadsheet on a TV, and the Planning Center notes fields doing a job they were never built for. It does not replace Planning Center, your console, or your people.

How it works

Three steps, one of which is automatic.

01

Drop the week's files

The Planning Center report and the input-list workbook — the files your team already makes. One upload, one preview, one apply. Unknown people are added automatically; probable typos are flagged instead.

02

Every screen updates

Backstage walls, the rack display, the tech dashboard, your custom dashboards, the Rokus. Singers see their mic, pack, and position; the booth sees the patch, phantom, mute groups, and routing.

03

Sunday clears itself

At 1 PM the board wipes for the next week — unless you've already loaded it. Inventory, people, and photos are never touched.

What it runs

Six pillars. One product. The whole booth.

Displays

Every TV in the building

Backstage walls, the pinned rack display with charger-aligned columns, and a WYSIWYG builder: set your TV's exact dimensions and lay out widgets on a live render of the real page.

Wireless & ears

The mic map

Handhelds, packs, IEMs — who has what, which charger slot, which channel. Color-coded the way your rack actually is.

Patch & mixes

The input list, alive

Snake and FOH channels, phantom flags, mute groups, monitor routing, and every personal-mixer channel — on the tech dashboard, not in a binder.

Assets

Every piece of gear, tagged

QR labels sized for Avery sheets. Scan a label with any phone and get the gear's card: status, serial, location, notes. Seed the whole wireless rack in one click.

People

Booth crew and band

Who's behind the controls and who's on the risers, seat by seat, week by week — with photos, so new volunteers learn names fast.

Prep

The week loads itself

Weekly imports, automatic Sunday clear, and a stage plot drawn from the week's data — print it or don't, it redraws itself either way.

Two rooms, one product

Built for both ends of the snake.

The booth team

Sound, lights, graphics, stream. You get the tech dashboard — patch, phantom, mute groups, IEM RF paths — plus assets, crew seats, and the dashboard builder for every screen you own.

The band

Vocalists and players. You get the wall: which mic is yours, which pack, which mix channel, where you stand — answered before anyone has to ask the booth on comms.

The build standard

Designed for Sunday, not the spec sheet.

Hardware
An $80 Raspberry Pi you own
Or any box that runs Docker. It can drive your main TV directly and serve every other screen on the LAN.
Your data
One SQLite file
Export everything as JSON any time. Nightly backups are a cron line. No cloud account required to run your booth.
Displays
Any browser · Rokus included
TVs bookmark a URL once. Rokus get a native channel fed by live snapshots. Screens survive server hiccups gracefully.
Internet
Not required on Sunday
Everything runs on your LAN. The internet is for updates and optional remote admin, not for the service.
Fail-safe
The sheet is the truth
Imports preview before they apply. Typo-looking names warn instead of creating duplicates. The wall never shows stale weeks — Sunday 1 PM clears it.
Pricing

The FedUp rule applies to the whole family: flat price, plain sight, no subscription.

Early access · free while we harden it
Join early access
Questions
Does it replace Planning Center?

No — it feeds on it. PCO schedules people and songs; TechBooth turns that plus your input list into walls, dashboards, and assignments. Direct PCO API sync is on the roadmap; today it reads the report you already print.

We're not a big church. Is this overkill?

It runs on one $80 Pi and one TV. If you've ever taped a name to a mic, you're the target audience.

What about our brand on the screens?

The wall always wears your church's face — your name, your logo, your colors. TechBooth brands the admin, never the displays.

What happens when the internet dies mid-service?

Nothing. It's all on your LAN. The screens keep polling the Pi; the Pi doesn't know the internet exists.