Religious organisations

Services streamed to your own site, and an archive that lasts

A service happens at the same time every week and the recording becomes something people return to for years. Both halves matter, and the second is where most setups quietly fail — so this page is specific about what to confirm before the first broadcast.

Start free trialTalk to us

This week’s service, and the archive behind it

The problem

What usually goes wrong with a weekly broadcast

Streaming to a public platform is the easy start, and it works until you notice what surrounds it: advertising nobody chose, recommendations pointing at unrelated content, and a community sent off your own site every week to watch you.

The archive problem arrives later. Two years of services sit on a platform in an account somebody set up, unorganised and unsearchable, and the person who ran it has moved on. When a member asks for the service from a particular Sunday, nobody can find it.

The third problem is the one nobody plans for: the service happens whether or not the technology is ready. Anything that has to be confirmed — retention, scheduling, who watches — is worth confirming before a Sunday rather than during one.

The workflow

From a live service to a findable archive

  1. 01

    Confirm the retention answer first

    Get written confirmation of whether and how your plan retains a broadcast as on-demand video. Record that answer in the weekly runbook so the archive workflow is established before the first service.

  2. 02

    Set up ingest and rehearse it

    Point your encoder or mixer at the ingest URL and stream key, and run a private test at the same time of day and on the same connection you will use. Encoder and upload problems surface here, not in a specification.

  3. 03

    Embed the stream on your own page

    Put the embed on your site, on a page that exists before the service starts so people can find it early. Whether your CMS accepts the embed depends on its HTML and script rules — check it in advance.

  4. 04

    Organise the archive as you go

    Name and file each service when it happens, using projects to separate services from teaching series or community events. An archive is only useful if somebody can find the one they want.

  5. 05

    Decide who should reach what

    Most services are public and should be findable. Pastoral or members-only content is different: restrict the embed to your own domains and use signed, expiring links rather than an unlisted URL.

The mechanisms

What the platform provides

RTMP ingestYour encoder
An ingest URL and stream key that OBS, a hardware encoder or a mixer can point at. Nothing proprietary is required at your end.
HLS playback on your own pageViewers
Viewers watch through the same player and embed as your on-demand video, on your site rather than a public platform.
Adaptive deliveryEvery viewer
A quality ladder, which matters for an older congregation watching on tablets and variable home connections.
An organised on-demand archiveLibrary
Videos as records you can name, organise into projects, update and remove — the basis of an archive that survives a change of volunteer.
Access controls for restricted contentPer project
Origin-restricted playback and signed, expiring links where content should not be public.
Member-level viewing reportsPlus and larger plans
Supply your own member ID in the embed to connect accepted playback events to that identifier when individual viewing insight supports your community workflow.

Fit

Where this suits a congregation

  • Best for — weekly services on your own site

    A broadcast that keeps the community on your page, without advertising or unrelated recommendations at the end.

  • Best for — a sermon and teaching archive

    Years of recordings organised so a member can find the one they want, and so a volunteer handover does not lose them.

  • Best for — members-only material

    Pastoral or study content restricted to your own domains with expiring links rather than an unlisted URL.

  • Connect giving and member management

    Keep giving, membership records and ministry-management workflows in the systems that own them, then ask us in writing about any specific integration the viewing journey requires.

Rehearse a broadcast on a weekday

Stream a test at the same time and on the same connection you will use on Sunday, embed it on a private page, and confirm with us what happens to the recording afterwards.

Talk to usStart free trial