Multi-Channel RTMP Server Setup

I run dev.smasshbox.com, a custom social-media platform, and I’m ready to move our in-house video stack from “proof of concept” to production. The goal is a rock-solid RTMP server that can ingest between 10 and 50 concurrent channels, push each feed to my application in real time, and keep a copy for later viewing.

Here’s the flow I have in mind: broadcasters connect with standard RTMP, the server transcodes if needed, forwards a HLS/DASH output that my front-end player can consume, and writes an archival file to cloud or local storage. Everything must remain inside my ecosystem—no relaying to Facebook, YouTube or Twitch—so authentication hooks and API callbacks to my platform are essential.

Deliverables
• Fully configured RTMP stack (Nginx-RTMP, MediaSoup, Wowza, or your preferred tool) on a fresh VPS or cloud instance of my choosing
• Sample nginx.conf (or equivalent) showing multi-channel support, stream key authentication tied to my user IDs, and automatic file recording
• Step-by-step deployment notes so my team can replicate the setup in staging and production
• Short load-test report confirming stable performance at 50 simultaneous 720p streams

Acceptance criteria
1. A test broadcaster can go live, the player on dev.smasshbox.com renders the stream within two seconds of latency, and the .mp4 archive appears in the designated bucket.
2. CPU, memory and network usage remain under 70 % during a 50-stream stress test.
3. All configuration is documented and committed to my private repo.

Let me know which tech stack you’d pick, how quickly you can spin up the first working instance, and any prior RTMP projects you’ve handled.
Also need video on demand