Node Media Streaming Platform
Budget: $500 – $560 USD
I’m upgrading my existing live-streaming environment to a clean, lightweight Node-powered media server that pairs a MongoDB backend with a crisp single-page front end. The core of the build is Node-Media-Server (or an equivalent RTMP module you’re fully versed in), extended with an admin dashboard that gives me full control over every user and feature.
Key functions I need implemented
• User flows – self-registration, login, and a single-page viewer console.
• RTMP credentials – the system must issue keys automatically or manually, YouTube-style, keeping the exact URL/key format I already use. For each new key the UI should also prompt an associated audio-file upload.
• Streaming features – push, pull, logo overlay, scrolling text, transcoding, and recording. Both the preview player and any pushed stream must display the logo and ticker.
• Plans & limits – plans will be created by the admin and tied to users in MongoDB. Every streaming feature must be switchable per plan from the dashboard.
• Database migration – I’ll supply a dump of my current MongoDB; import it so existing users and keys work untouched.
• Admin console – metrics, on/off toggles for each feature, and resource usage stats in one place.
• Performance – the finished stack should be as lean as possible on CPU/RAM while remaining stable under concurrent streams.
Deliverables
1. Source code with clear structure and comments.
2. MongoDB import script plus verification that legacy data loads correctly.
3. SPA front end for users, React/Vue/Angular or vanilla—your call, as long as it’s fast.
4. Admin dashboard with complete feature control and plan management.
5. Documentation: setup, deploy, and how to add future modules.
I’ll share a few minor edge cases once development starts, but the outline above captures the essentials. Clean code, strong RTMP know-how, and an eye on efficiency are paramount.
Key functions I need implemented
• User flows – self-registration, login, and a single-page viewer console.
• RTMP credentials – the system must issue keys automatically or manually, YouTube-style, keeping the exact URL/key format I already use. For each new key the UI should also prompt an associated audio-file upload.
• Streaming features – push, pull, logo overlay, scrolling text, transcoding, and recording. Both the preview player and any pushed stream must display the logo and ticker.
• Plans & limits – plans will be created by the admin and tied to users in MongoDB. Every streaming feature must be switchable per plan from the dashboard.
• Database migration – I’ll supply a dump of my current MongoDB; import it so existing users and keys work untouched.
• Admin console – metrics, on/off toggles for each feature, and resource usage stats in one place.
• Performance – the finished stack should be as lean as possible on CPU/RAM while remaining stable under concurrent streams.
Deliverables
1. Source code with clear structure and comments.
2. MongoDB import script plus verification that legacy data loads correctly.
3. SPA front end for users, React/Vue/Angular or vanilla—your call, as long as it’s fast.
4. Admin dashboard with complete feature control and plan management.
5. Documentation: setup, deploy, and how to add future modules.
I’ll share a few minor edge cases once development starts, but the outline above captures the essentials. Clean code, strong RTMP know-how, and an eye on efficiency are paramount.