Live streaming a real estate open house or virtual tour means pushing video from a phone, gimbal, or camera over RTMP or SRT to a VPS running a streaming engine (Ant Media, Wowza, or NGINX-RTMP), which transcodes it into HLS or WebRTC for remote buyers to watch on any browser or device. A single property tour runs comfortably on a 2 vCPU / 4 GB VPS; brokerages streaming several open houses in parallel, or running interactive WebRTC Q&A, need 4-8 vCPU and more RAM headroom for transcoding. The setup takes under an hour once the VPS and app are provisioned.
Key Takeaways
- A single agent streaming one open house needs only a 2 vCPU / 4 GB VPS with an engine like Ant Media Server or NGINX-RTMP pre-installed — no dedicated hardware beyond a phone or camera and a stable uplink.
- RTMP into HLS is the simplest, most compatible path for one-way open house broadcasts; WebRTC adds sub-second latency for live buyer Q&A but costs more CPU per viewer on the transcoding side.
- Plan for roughly 4-6 Mbps of upload bandwidth per 1080p tour and 1.35 GB of viewer download data per hour at a 3 Mbps HLS rendition.
- Brokerages running 3-5 simultaneous property streams should size up to 4-8 vCPU / 8-16 GB to leave transcoding headroom and avoid dropped frames during peak Saturday open-house windows.
- Token-authenticated stream URLs are worth the extra setup step for pre-listing or VIP walkthroughs where the seller doesn’t want the link circulating publicly.
Why Real Estate Agents Are Turning to Live Streaming
Matterport scans and drone photography solved the “show the property” problem for asynchronous browsing, but they don’t solve the “I’m relocating from another city and can’t fly in this weekend” problem. A live stream does: a buyer’s agent or the listing agent walks the property with a phone or a small gimbal rig, remote buyers watch from wherever they are, and questions get answered on the spot instead of over a follow-up email three days later. We’ve watched this shift accelerate with brokerages serving NRI buyers and relocation clients in particular, where the buyer is frequently in a different time zone and a scheduled 20-minute live walkthrough beats waiting for a professionally edited video.
The infrastructure requirement is modest compared to sports or esports streaming — one camera, one presenter, predictable duration — which is exactly why a lot of agents try to get away with a Zoom call and end up frustrated by low resolution, no recording, and no branded viewing page. A proper RTMP or SRT stream into a VPS-hosted engine fixes all three.
How Do You Set Up a Live Stream for an Open House?
- Provision the VPS and engine. Spin up a VPS with your streaming engine pre-installed — Ant Media Server listens for RTMP on port 1935 and serves HLS/WebRTC over 5080 (HTTP) or 5443 (HTTPS) by default; NGINX-RTMP typically listens on 1935 for ingest and serves HLS over your configured HTTP port (commonly 8080).
- Create a stream application and key. In Ant Media’s dashboard, create an application (e.g.
openhouse) and generate a stream ID; for NGINX-RTMP, add anapplicationblock tonginx.confwith a uniquestream_keyyou control. - Configure the encoder. In OBS or an equivalent mobile app (Larix Broadcaster is what we recommend for iOS/Android field use), set the RTMP URL to
rtmp://your-vps-ip/openhouse/streamkey, resolution to 1920×1080, and bitrate to 4500 kbps for a solid connection or 3000 kbps if you’re on a spotty 4G uplink. - Test the ingest before the buyer joins. Walk one room, confirm the stream shows up in your engine dashboard and that the HLS or WebRTC playback URL renders in a browser with under 10 seconds of delay.
- Share a branded viewing page, not a raw URL. Embed the HLS.js or WebRTC player on a page under your own domain or the brokerage’s site rather than sending buyers a bare
.m3u8link — it looks more professional and lets you add a chat widget or lead-capture form next to the video. - Record simultaneously. Most engines can write the incoming stream to disk (MP4 or FLV) at the same time they’re serving it live, so you walk away with an on-demand replay for buyers who couldn’t make the live slot — no separate recording step needed.
What Equipment Do You Need for Real Estate Live Streaming?
You don’t need broadcast gear. The equipment question is really “how much do you want to spend to reduce shake and dropped frames,” and the honest answer scales with how often you’re doing this.
| Setup tier | Gear | Typical cost (one-time) | Best for |
|---|---|---|---|
| Minimum viable | Phone + 3-axis gimbal (DJI Osmo Mobile or similar) + Larix Broadcaster app | $120-160 | Occasional open houses, single agent |
| Solid weekly use | Phone or mirrorless camera + gimbal + external mic + phone mount tripod | $300-500 | Agents running 2-4 tours a week |
| Brokerage-grade | Mirrorless camera with clean HDMI out + UVC capture card + laptop running OBS + wireless lapel mic | $800-1,500 | Multi-agent brokerages, premium listings |
| Interactive WebRTC tours | Same as brokerage-grade + a VPS engine configured for WebRTC ingest (Ant Media, or NGINX with WebRTC module) for sub-second buyer Q&A | $800-1,500 + WebRTC-capable VPS plan | Luxury listings, relocation/NRI buyers who need to ask questions live |
A stabilized phone stream at 1080p/30fps over a good 4G or WiFi uplink is genuinely fine for 90% of open houses — don’t over-invest in gear before you’ve done a handful of streams and know what actually breaks (usually it’s the network, not the camera).
RTMP vs WebRTC for Virtual Tours: Which Should You Use?
This is the real architectural decision, and it comes down to whether buyers need to talk back in real time.
| Factor | RTMP → HLS delivery | WebRTC delivery |
|---|---|---|
| Glass-to-glass latency | 6-15 seconds typical | Under 1 second typical |
| Best for | One-way broadcast, large or unknown viewer counts | Live buyer Q&A, small VIP walkthroughs |
| Browser support | Universal via HLS.js / Video.js, no plugins | Native in all modern browsers, no plugin needed |
| CPU load on VPS | Lower per viewer (HLS segments are cached and reused) | Higher per viewer (each WebRTC session is a live media path) |
| Typical viewer ceiling on a 4 vCPU VPS | 300-500+ concurrent HLS viewers | 30-60 concurrent WebRTC viewers before CPU becomes the bottleneck |
| Recording | Trivial — write the incoming RTMP stream to MP4 | Supported but adds extra processing load |
If you’re broadcasting to an open list of interested buyers who just want to watch, RTMP-to-HLS is the right default — it scales further per dollar of VPS and every browser plays it natively. If you’re doing a scheduled one-on-one or small-group walkthrough where a serious buyer wants to say “go back, open that cabinet again,” WebRTC’s sub-second delay is worth the extra CPU cost. Ant Media Server supports both from the same ingest with minimal extra config, which is why we default most real estate customers to it.
How Much VPS Power Do You Need for Multiple Simultaneous Open Houses?
Saturday mornings are the real load test — every brokerage wants to stream at 11am. Sizing depends on concurrent property streams, not total viewers per stream, since each incoming RTMP source needs its own transcode pipeline if you’re generating multiple output renditions.
| Concurrent property streams | Recommended VPS | Notes |
|---|---|---|
| 1 property | 2 vCPU / 4 GB | Single rendition (1080p passthrough), no ABR ladder needed |
| 2-3 properties | 4 vCPU / 8 GB | Light 2-rung ABR ladder (1080p + 480p) per stream recommended |
| 4-6 properties | 8 vCPU / 16 GB | Consider splitting across two VPS instances behind a shared player page for redundancy |
| Brokerage-wide (10+ properties/week, staggered) | 4-8 vCPU / 8-16 GB with hourly billing | Scale the VPS up only during Thursday-Sunday peak windows, back down midweek |
In our own testing, a 4 vCPU / 8 GB VPS running Ant Media Server held three concurrent 1080p RTMP inputs, each transcoded to a 1080p + 480p ABR ladder, before CPU utilization crossed 75% — that’s the point where we’d recommend adding a second instance rather than pushing a fourth stream onto the same box.
Common Problems When Live Streaming Real Estate Tours
The most frequent issue isn’t the VPS — it’s the property itself. Homes are bandwidth dead zones: thick walls, no WiFi in the garage, and a 4G signal that drops to one bar in a finished basement. A few fixes that consistently help:
- Use cellular, not the property’s WiFi, unless you’ve tested it in advance — a vacant house’s WiFi (if any) is unreliable and you don’t control it.
- Set your encoder’s bitrate below your actual measured uplink, not your carrier’s advertised speed — if a speed test shows 8 Mbps up, encode at 4-5 Mbps, not 8, to leave headroom for network variance.
- Enable auto-reconnect in your encoder app (Larix Broadcaster and OBS both support this) so a 2-second cellular hiccup doesn’t kill the whole stream.
- Open the correct firewall ports on the VPS in advance — RTMP ingest on 1935/tcp, and your engine’s HTTP/HTTPS playback ports — and confirm with a local test stream the day before, not the morning of.
- Keep a wired backup (a hotspot with an external antenna, or a second phone on a different carrier) for listings you know have poor coverage.
Frequently Asked Questions
Do I need a dedicated streaming server for a single open house?
No. A 2 vCPU / 4 GB VPS running a pre-installed engine like Ant Media or NGINX-RTMP comfortably handles one property stream to a few hundred viewers.
Can I stream a virtual tour directly to Instagram or YouTube instead of my own site?
Yes. Your VPS can restream the same RTMP source to Instagram, YouTube, and Facebook simultaneously using OBS’s multi-output feature or an engine’s push-publish target.
What’s the difference between a live open house stream and a recorded virtual tour video?
A live stream is real-time RTMP or WebRTC where buyers can watch and ask questions as the agent walks through, while a recorded virtual tour is pre-shot or scanned footage uploaded as on-demand video with no live interaction.
How much bandwidth does a real estate live stream use?
A 1080p walkthrough at 4-6 Mbps uses roughly 1.8-2.7 GB of upload data per hour, and each viewer watching a 3 Mbps HLS rendition uses about 1.35 GB per hour on download.
Is WebRTC or RTMP better for interactive open houses where buyers ask questions live?
WebRTC is better for live back-and-forth thanks to sub-second latency, while RTMP-to-HLS is fine for one-way viewing but carries 6-15 seconds of delay that makes live Q&A feel disjointed.
Get Streaming This Weekend
Real estate live streaming doesn’t need a production truck — it needs a VPS with the right engine already installed, a stable uplink, and about an hour of setup the first time you do it. StreamingVPS.com ships Ant Media Server, Wowza, and NGINX-RTMP pre-installed and ready for RTMP or WebRTC ingest the moment your VPS boots. Get a pre-installed streaming VPS from StreamingVPS.com and go live in 60 seconds — see also our guides on restreaming to Twitch, YouTube & Facebook and WebRTC streaming with Ant Media.
