Livestreaming and the media library.
One workspace. The whole video life cycle.
Camera or RTMP — both broadcast-grade. Real-time chat, in-stream giving, and prayer requests during the service. Every stream auto-archives to your sermon library. Series, podcast feeds, simulated-live, and embed-anywhere widgets included. The live moment and everything that follows, in one place.
Sunday morning is the start, not the end
Most churches treat streaming and the library
as two different problems.
The live broadcast is one product subscription. The sermon archive is a different subscription — usually a video host that the church uploads to manually. The podcast feed is a third tool. The embed code for the church website comes from somewhere else again. Every Sunday, the staff choreographs a hand-off across four systems: end the stream, download the recording, re-upload to the archive, tag the series, generate the podcast episode, refresh the embed. By Wednesday, the hand-off either happened or it didn't, and the back catalog reflects which is which.
On TrueConnect+, the broadcast and the library are one workspace. Every livestream becomes a video-on-demand asset the moment it ends, tagged into its series, pushed to the podcast feed, and available to embed on your existing website. No upload step. No re-encoding job to babysit. No subscription stack. The live moment and the long tail are the same record, just in different states.
And every viewer is a person in your CRM. The donor who gave during the stream is the same record your bookkeeper sees Monday. The prayer request submitted at minute 28 belongs to a real human your pastoral team can follow up with on Tuesday. Watching from home becomes participation, not observation.
Camera in a tab. Or production booth through RTMP. Both shipped.
Some churches stream from a tablet at the back of the sanctuary. Others run a full production booth with multiple cameras, scenes, and switchers through professional encoding software.
We support both, with the same admin UI. Browser camera mode launches in seconds — point your laptop or phone at the stage and click Go Live. RTMP mode gives you a stream key your production software dials in to. Switch between the two between services. The downstream pipeline — chat, giving, VOD, embed — is identical regardless of how you broadcast.
- Browser camera + screen-share with one click
- RTMP for production-grade workflows with any standard encoder
- Stream key rotation when you need it
- Force End from any device if something goes wrong
Watching online doesn't have to mean watching alone.
Real-time chat. In-stream giving with one tap. Prayer requests submitted during the service that the prayer team sees in real time. The people watching from home are participating, not just observing.
And every interaction is tied to your CRM. The donor watching from their couch is the same person in your member directory. The prayer request submitted at minute 28 belongs to a real human you can follow up with on Tuesday.
- Real-time chat with moderation
- In-stream giving (one tap, saved payment methods)
- Prayer requests submitted during the service
- Live audience count visible to the host
Recent sermons stay close. The deep catalog stays accessible.
Recordings that finished in the last three months stay in the active library — instant playback, embed-ready, indexed for search. After three months they migrate to a deep archive at a fraction of the storage cost, but they don't disappear — they're still searchable and still playable. If a recording surges in viewership (a clip resonates, a series gets shared), the system promotes it back to the active library automatically.
That's what lets a five-year-old sermon library not crush a church's storage budget. The recent stuff lives hot; the older stuff lives cold; the demand-following promotion happens automatically. The pastor doesn't archive anything by hand. The bookkeeper doesn't see the bill blow out as the catalog grows.
- Three months hot, then automatic migration to deep archive
- Cold sermons are still searchable and playable on demand
- Demand-driven auto-promotion when a sermon surges in viewership
- No manual archive step, no surprise storage bills as the library grows
Plus everything around the stream
The whole video life cycle, on one platform.
Auto-VOD
Every stream is automatically archived as a video-on-demand asset the moment it ends. Members replay during the week. New visitors browse the back catalog. No manual upload, no encoding job to babysit.
Sermon series
Group VODs into named series with cover art and episode numbers. “Rooted: A Study Through Colossians” lives as a unit, not a list of unrelated videos. Members follow the series; the next episode shows up automatically.
Podcast distribution
Auto-generated RSS feed for your sermon library. Submit once to the major podcast directories, then forget it — every Sunday's sermon flows through automatically as podcast audio.
Simulated-live
For Easter, Christmas Eve, or any pre-recorded major service: schedule a VOD to play as if it's live, at the exact time you choose. The chat is live. The audience experience is identical. The pre-recorded sermon plays on cue.
Embed widget
Drop the livestream player and the sermon library into your existing church website with a one-line embed. Your origin allowlist controls who can embed. Visitors watch without being redirected.
Per-stream paid access
Optional ticket gate per stream — a paid access flow for church conferences, special events, or guest speakers. Stripe-powered checkout, automatic access provisioning.
One Sunday, three audiences served by the same record.
At 10am Sunday, 320 people are watching the service live — some in the sanctuary, some at home, some on their phones during a commute. The chat is moderated. Twenty-seven of them give during the in-stream offering. Four submit prayer requests, which the prayer team picks up before the benediction.
At 11:32am the stream ends. By 11:33, the VOD is published, tagged into the current series, and live in the sermon library. The podcast feed picked it up automatically. The embed on the church website now plays this morning's service. The members who couldn't watch live get a push notification that this week's sermon is available.
Three months later, the sermon migrates quietly to deep archive. Six months after that, a new visitor finds it via a search and watches — and the system promotes it back to the active library for the duration of its second life. None of this required a staff person to do anything.