Church and Faith Streaming

Weekly services on your own website, and on social at once

A congregation watching on social platforms sees ads and suggested videos beside the service. CreekX puts the service on your own website, sends it to YouTube and Facebook at the same time, and plays past services around the clock.

01triggers

When the service is surrounded by ads

Most churches began streaming on a social platform because it was free and already there. The cost shows later: an advert before the sermon, a suggested video beside the prayer, a service muted or taken down by an automatic music match, and a congregation whose weekly habit lives on someone else’s site.

Ads and suggestions beside worship

Embed the player on your own site. The service plays on a page you control, beside your own notices and giving link, with no adverts and no suggested videos from creekX.

Members still use social

Restream to YouTube and Facebook at once. One feed from the sanctuary goes to your website and to the platforms together; creekX copies it without re-encoding, so a modest server is enough.

People watch at other times

Run a 24/7 channel of past services, so a member who opens the page on a Wednesday finds a service playing rather than an empty player. The schedule refills itself from the services you choose.

The nave of a stone cathedral with rows of red chairs facing the altar under a vaulted ceiling
The room is the same every week. What changes is how many people join from home, and whose website they join on.
02process

How it works

Send from the sanctuary

OBS and a camera, or a hardware encoder. Take sound from the mixing desk rather than the camera microphone; it matters more than picture quality. Steps: go live from OBS.

Publish everywhere

Your site plus social platforms. Add each platform once with its stream key, tick it on the stream, and it receives every service from then on. Steps: YouTube, Facebook and more at once.

Keep services playing

Recordings into a 24/7 channel. Turn on recording, and each service is in the library when it ends, ready to add to the channel. Steps: put a video library on air.

Diagram: a sanctuary camera and OBS send RTMP to a creekX server, which plays the service on the church website, copies it to YouTube and Facebook and runs a 24/7 channel of past services
The weekly service path. Delay figures: creekX 2026.10.13, 1080p source, measured on a local network. Conditions are on the benchmarks page.
03deliverables

What you get

  • The service live on your own website, with no adverts from creekX
  • YouTube and Facebook at the same time, up to 10 destinations on Pro
  • A 24/7 channel of past services
  • Recordings on your own disks
  • Private links for a funeral or a wedding that should not be public
  • One price per server, whatever the size of the congregation
04protocol fit

Which protocol for a weekly service

A service does not need sub-second delay. It needs to start on time and play without stalling on a phone in a kitchen. That points to the simplest path in and HLS out.

Protocol choices for a service. Delay figures are creekX’s own measurements on a local network.
LegProtocolMeasured delayWhy
OBS in the sanctuary to the serverRTMPNot measured separatelyOBS speaks it out of the box. Use SRT only if the line drops packets.
Server to members at homeLow-latency HLS1.23-1.28 s median, 1.40 s worstPlain HTTPS; plays in any current browser and on phones.
Server to smart TVs and older devicesHLS3.4-3.8 s median, 4.4 s worstThe widest device support.
Server to an overflow room in the buildingWebRTC0.49 s median, 0.68 s worstThe room can hear the sanctuary, so the picture must keep up.
Server to YouTube and FacebookRTMP restreamThe platform’s own delayReach, from the same single feed.
05sizing and cost

A sizing example: one service and 150 households

A weekly service is a small load for a streaming server. The figures below are worked from our own measurements on a 4 vCPU, 8 GB server.

  • Source: one 720p feed at 2.5 Mbit/s from OBS.
  • Viewers on your site: 150 households at 2.5 Mbit/s is 375 Mbit/s at the peak. The test server sustained about 890 Mbit/s, roughly 350 viewers at this bitrate (calculated).
  • Platforms: one extra 2.5 Mbit/s copy each for YouTube and Facebook.
  • Recording: about 1.7 GB for a 90-minute service at 2.5 Mbit/s (calculated), about 88 GB for a year of Sundays.
  • The weekday channel: 4 to 6% of a core.
  • Data: 375 Mbit/s for 90 minutes is about 250 GB a week. Check the server plan’s traffic allowance.

A 4 vCPU server is more than this needs. We have not measured a smaller server, so the trial is the place to find out what yours carries.

06First-party evidence

Measured delivery delay, with the test conditions

In a first-party test on 13 October 2026, CreekX 2026.10.13 measured a median delay of 0.49 seconds for WebRTC, with a worst result of 0.68 seconds. Low-latency HLS measured 1.23-1.28 seconds at the median and 1.40 seconds at worst. Standard HLS measured 3.4-3.8 seconds at the median and 4.4 seconds at worst. The test used the standard one-line installer on an Ubuntu 24.04 cloud server with 4 vCPU, 8 GB memory, a 100 GB NVMe disk and about 890 Mbit/s upload bandwidth. The source was a real 1080p, 25 fps H.264 clip at 5 Mbit/s, sent from OBS and viewed on a laptop over the local network. Each step ran for 60 seconds. These are product measurements under the stated conditions, not results from a customer deployment or a promise for each viewer.

07honest limits

What creekX does not do for a church

  • It does not run itself: somebody must look after an Ubuntu server, or you pay for help.
  • No music licensing, and no control over what a platform does to the copy it receives.
  • No online giving, member directory or church management features.
  • No television or phone apps; viewing is in a browser or the Android kiosk player.
  • No camera switching or lyrics overlay. Those are done in OBS.
08Scope & limitations

Know where the security and data boundary sits

CreekX has no telemetry and can run with an offline licence and offline installation package supplied through sales. Video and the installed product’s operational account data remain on the customer-controlled server during local operation. Website and sales enquiries are separate. Enabling an off-site backup, external storage, restream destination or another outbound integration creates a corresponding outbound data path. Recorded video and library files are not encrypted by CreekX on the customer’s disks; use server-level disk encryption when encryption at rest is required. Viewer-security features have been checked through CreekX automated tests, but no formal third-party security certification or assessment has been completed.

09buyer fit

Start with a trial or speak to CreekX first

Start the trial yourself

The 14-day Media Server trial is available without a credit card. It includes the Media Server feature set with trial limits of five 24/7 channels, five restream destinations per stream and 500 library videos. Installation requires an internet connection. Your content is kept when the trial ends. Add a paid licence to continue using licensed features and creating channels after the trial and any applicable licence grace period.

Speak to CreekX before installing

Contact CreekX first if the deployment must be fully offline or air-gapped, will use several servers or more than 50 concurrent live streams, expects thousands of viewers, forms part of a tender, or needs installation, training or Enterprise support. CreekX currently operates one server per installation, so the team should check hardware, network capacity and product fit for a large audience before the trial.

10faq

Questions from churches and charities

Do we need a technical team?

Someone comfortable installing software on an Ubuntu server, or ask CreekX for help. Installation is one command, and the weekly work is pressing Start Streaming in OBS. A server needs occasional care: updates, and an eye on disk space. Done-for-you installation and training are paid services.

Can we still stream on Facebook?

Yes, at the same time as your own site. The platforms apply their own rules, including automatic music matching, to the copy they receive; your own website’s copy is not affected by them.

What upload speed do we need?

About twice your stream’s bitrate per camera, tested for the length of a service: 5 Mbit/s of steady upload for a 720p stream at 2.5 Mbit/s. Use a wired connection for the streaming computer, not the building’s Wi-Fi. More: how much upload speed live streaming needs.

What does it cost each year?

Media Server Pro is USD 999 per server a year, or USD 99 a month, with no charge per viewer or per service. On top you rent or own a server and its internet connection. The 14-day trial is free and needs no card.

Can a funeral or wedding be private?

Yes. Leave the public watch link off and send the family a private link that expires. Nobody without the link can watch, and it is not listed anywhere.

Are our songs and hymns covered?

creekX does not check, license or mute music. Streaming copyrighted music needs the appropriate licence from your own licensing body, on your own website as much as on a platform.

Can people watch on a television?

On a smart TV’s browser or by casting from a phone, through HLS. creekX has no television apps of its own. For a screen in the church hall, the Android kiosk player locks a screen to one stream.

What if the internet fails during the service?

The stream stops until it returns, and OBS reconnects by itself. Record in OBS as well as on the server, so the full service can be uploaded afterwards. The live stream recovery drill covers what to practise.

11Your next step

Try it on a Sunday rehearsal

Run the trial during a rehearsal, then go live the following week.

Follow the build