.NET Developer for Live Streaming Platform

@ambar

Do you already have RTMP ingest server running? Need creator chat saved in DB or only live messages? Should private sessions be 1 host + 1 user only at first? I went through your description carefully. Hi, this is Ambar Shome, I work independently but also run Shome & Associates for larger projects. I can handle this build in practical way, no overcomplication. Main backend in ASP.NET Core API with PostgreSQL. Public live can run RTMP input to FFmpeg, then generate HLS (.m3u8 + .ts) for player. Private and VIP sessions better through LiveKit WebRTC with token based access. SignalR for chat, join/leave events, tip alerts. I’d keep things simple first: separate tables for rooms, sessions, payments, chat logs. Redis for online users + short cache. Docker setup so moving server later is easy. Basic admin endpoints too, useful later. Some small things I’d add from start because they save trouble later: auto delete old HLS files session timeout if host leaves retry webhook for failed payment callback rate limit spam chat record error logs per room manual room block/unblock low quality stream option for weak users For HLS I’d use short segments for better delay. For WebRTC, TURN server enabled so mobile users connect easier. Same token flow can be reused across chat + video. Code will stay readable, not heavy. Swagger docs included. Sure, can start with core modules first and expand after traffic comes. Single server first, or separate media server from day one?

@kamran2012

Hello, I will build your streaming backend in ASP.NET Core — HLS broadcast pipeline, WebRTC private/group sessions via LiveKit, and SignalR chat with room access control and entitlement logic. For the HLS pipeline, I will set up RTMP ingest through NGINX-RTMP, with FFmpeg transcoding into multiple bitrate renditions and LL-HLS segment output. This gives you adaptive bitrate playback while keeping latency under 3-4 seconds — critical for creator-viewer interaction during public broadcasts. Redis will handle pub-sub for real-time events and session state caching across instances. Questions: 1) Are you deploying on AWS — should I architect around MediaLive/CloudFront, or will you use self-managed NGINX-RTMP servers? 2) For group WebRTC sessions, what is the expected max participant count per room? Looking forward to discussing further. Best regards, Kamran

@mayankinnovative

Hi, As per my understanding: You are building a scalable live streaming and creator engagement platform using .NET Core. Public broadcasts will run via RTMP ingest and FFmpeg to generate HLS output, while private and group sessions will use WebRTC. The system must support chat via SignalR, JWT-based access control, tipping, PostgreSQL storage, and Redis for scalability. The focus is production-ready architecture that handles concurrency and low latency. Implementation approach: I would structure the backend using ASP.NET Core with clean layered architecture and JWT authentication. For public broadcasts, I will configure NGINX RTMP for ingest, process streams via FFmpeg, and generate HLS segments optimized for latency, optionally fronted by CDN. Broadcast room logic will manage entitlement and token validation. For private and group sessions, I will integrate LiveKit or similar WebRTC infrastructure with secure session tokens. SignalR will power real-time chat and events. PostgreSQL will manage core data, while Redis handles caching and pub-sub. Dockerized deployment will ensure scalability and clean environment management. A few quick questions: Do you plan to host on AWS or self-managed servers? What concurrency targets should we design for initially? Is LL-HLS required from phase one?

@ank26oct

As a seasoned .NET developer with over 12 years of experience, I am the perfect fit for your live streaming and creator engagement platform. I bring in-depth knowledge of C# programming, ASP.NET Core, and a strong background in building scalable backends. My expertise lies specifically with HLS streaming (HTTP Live Streaming) which is core to your project. I understand the intricacies of setting up RTMP ingest, FFmpeg processing, and HLS segment generation (.m3u8, .ts), making me well-suited to implement your required HLS-based live streaming pipeline. I believe my past experience in constructing livestreaming platforms will significantly contribute to the development of a robust product. Additionally, my competencies with PostgreSQL and Redis align perfectly with your requirements. Benefit from my skillset in using AWS MediaLive/MediaPackage/CloudFront as well as Docker/Kubernetes too. I promise clean coding practices, thorough API documentation, and above all - a quality production-ready implementation on-time that compliments your vision. Let's bring your concept into reality!

@mobiwebsolutions

✋ Hi There!!! ✋ The Goal of the project:- BUILD A SCALABLE LIVE STREAMING PLATFORM USING NET WITH HLS BROADCASTING WEBRTC SESSIONS AND REAL TIME CHAT SYSTEM I have carefully read your requirement for a streaming platform with HLS broadcast, WebRTC private sessions, SignalR chat, and scalable backend using ASP.NET Core with PostgreSQL and Redis. I am the best fit for this project because I have 9+ years experience as a full stack developer with strong expertise in real time systems, video streaming pipelines, and scalable backend architecture. * HLS streaming pipeline setup using RTMP ingest, FFmpeg processing and optimized segment delivery * WebRTC implementation for private and group sessions with secure access control * Real time features using SignalR with chat, events and performance optimization I will provide backend development, database design, API setup, streaming integration, testing, and full source code delivery with Docker deployment and documentation. I have worked on real time streaming and communication platforms with similar architecture and performance needs. Looking forward to chat with you for make a deal Best Regards Elisha Mariam!

@technologiesit

With over a decade of software development experience, I bring the ideal skill set for your live streaming platform project. My expertise spans from .NET to ASP.NET Core, C# Programming to API Development; I have worked extensively with these technologies building scalable and secure solutions. Talking specifically about HLS video streaming and WebRTC, I have a strong understanding and plenty of hands-on experience implementing them in previous projects. For instance, I constructed live streaming and OTT platforms incorporating technologies similar to what you require - AWS MediaLive / MediaPackage / CloudFront, FFmpeg tuning for video encoding, CDN optimization, among others. My approach combines thorough planning, clear communication, and efficient execution consistently delivering high-quality work. I believe in building long-term relationships with my clients by providing not just robust solutions but also impeccable after-sales support. With me on your team, you can rest assured that your vision will be turned into reality keeping your budget and timelines intact. Let's collaborate for a successful project completion!

@mahads31

With a keen understanding of the systems behind HLS broadcasting and private sessions (WebRTC) as well as over a decade's experience as a freelance Full Stack Developer, I believe am uniquely qualified to deliver an exceptional live streaming and creator engagement platform for you. I've successfully implemented similar projects like OTT/video platforms and Real-time communication apps before. With this broad knowledge under my belt, I can effectively build and optimize scalable backend infrastructure using .NET Core while ensuring low-latency HLS, which will greatly enhance the performance of your platform. During my tenure, I owned the entire project life cycle - from the design stage to the final deployment. Consequently, I'm well versed in all areas mentioned in the project description such as designing broadcast rooms, perfecting access controls & entitlement logic, creating real-time features with SignalR and more. My familiarity with NGINX RTMP, Media servers/CDN streaming (AWS Media Services), PostgreSQL and Redis adds more value to your project. As a bonus, I would also be augmenting your team with expertise in Docker/Kubernetes which is invaluable for ensuring a deployment-readiness that aligns with your need for scalable and maintainable architecture. Given the quality and production-ready implementation you seek at this important initial phase of the project, engaging me simply complements your goal of building a platform that stands the test of time.

@sonika1419

**DO NOT PAY ME UNTIL I COMPLETE! :)** Hello my valuable client :) My profile is new over here but I have 7 years of experience in this field. I have completely understood about your project. Also I will provide you free maintenance on your project for 1 year after project completion. I can definitely complete this in your timeframe. Give me one chance to prove myself. Hit the chat button to get started. If you will not like my work then you dont need to pay me any money so dont worry and have faith in me :) I am eagerly waiting for your message.

@abdf2010

Hey, I noticed your project, .NET Developer for Live Streaming Platform and believe I can help. My work in .NET has prepared me well for this kind of project. Looking forward to hearing your thoughts.

@KarthikTechCon

Hi, I’m Karthik with 15+ years of experience in .NET/C# backend development, real-time systems, streaming workflows, and scalable cloud architecture. I can help build your live streaming platform with a production-ready backend using ASP.NET Core, PostgreSQL, Redis, SignalR, HLS for public broadcasts, and WebRTC/LiveKit for private and group sessions. My approach: Build secure ASP.NET Core APIs with JWT auth, room access control, and entitlement logic Set up RTMP ingest → FFmpeg processing → HLS output for broadcast rooms Implement WebRTC private/VIP/group sessions using LiveKit Develop SignalR chat/events Optimize latency, Redis usage, background jobs, and concurrency Deliver Docker-ready deployment with Swagger docs Suggested stack: ASP.NET Core, PostgreSQL, Redis, LiveKit, NGINX RTMP/FFmpeg, CloudFront or similar CDN, Docker. For scale, AWS media services can also be evaluated where needed. I’ve worked on platforms involving streaming/video pipelines, real-time messaging, payment-integrated systems, secure APIs, and performance-focused backend architecture. I’m comfortable with HLS generation, access control, and production hardening. Estimated timeline: 3–6 weeks for the initial phase, depending on final session flows and infra choices. You will receive clean backend code, working HLS pipeline, WebRTC sessions, API docs, and deployment-ready setup. Warm Regards, Karthik

@rbtech1984

Hello There!!! ★★★★ (Scalable HLS + WebRTC streaming backend with real-time chat & payments) ★★★★ Project understanding: You need a .NET backend for live streaming platform with HLS for broadcasts, WebRTC for private/group sessions, and SignalR for chat. Also secure access, payments, and scalable infra. ⚜ ASP.NET Core backend APIs ⚜ HLS pipeline (RTMP → FFmpeg → HLS) ⚜ WebRTC session integration ⚜ SignalR real-time chat ⚜ Redis & PostgreSQL setup ⚜ JWT auth & access control ⚜ Docker deployment I have experince building real-time and streaming-based systems, handling video pipelines and scalable backend logic. I enjoy working on performance critical platforms. Approach: I will setup RTMP ingest via NGINX, process with FFmpeg to HLS, and use LiveKit/WebRTC for private calls. SignalR for chat and Redis for scaling. Let’s connect and discuss timeline, i can deliver production-ready solution. Warm Regards, Farhin B.

@muhammadaqib53

As an experienced full-stack developer specializing in backend systems, I have extensive experience with C# and the ASP.NET Core framework that your project needs. My expertise include all aspects of HLS streaming, from RTMP ingest and FFmpeg processing to HLS output. I also have a strong understanding of the NGINX RTMP infrastructure, which I believe will be extremely valuable to your project. In addition, I’m very experienced with WebRTC, having used it extensively for private sessions in my previous projects. I fully understand the demands of a live-streaming platform and I am confident that my skills and experience make me highly capable of delivering on all aspects of your project scope. Having previously worked with SignalR to implement real-time features such as chat and events, I understand well how these systems can significantly enrich user interaction in this context. The presence of my suggested technologies like Docker and Kubernetes offer easy deployment and scalability. In conclusion, by choosing me for this job you'll be getting a freelance partner who won’t sleep until your platform is churning out high-quality content in every dimension possible. Feel free to explore what other interesting offerings my diverse skills bring to the table!

@fizaa170

I understand you may have many great options to choose from, but getting the opportunity to work on this project would genuinely mean a lot for my growth. I’ll make sure to deliver my absolute best I can build a scalable .NET backend with RTMP to HLS pipeline using FFmpeg and NGINX, plus WebRTC private sessions with SignalR for real time engagement, all structured for high concurrency and low latency. The system will be clean, production ready, and designed to scale easily as your platform grows. Best regards, Muzammil

@rajeshrolen

Hello! You’re building a complex but well-structured streaming system combining HLS (broadcast) and WebRTC (interactive), which is exactly where most platforms run into latency and scaling issues. I’d approach this by: • RTMP → FFmpeg → HLS pipeline optimized for low latency • Separate architecture for broadcast (HLS via CDN) and private sessions (WebRTC / LiveKit) • SignalR + Redis for scalable real-time communication • JWT-based access control for sessions I’ve worked on similar real-time/backend-heavy systems where scalability and performance were critical. Quick question, Are you planning for LL-HLS and high concurrent viewers from the start? Happy to share a clean architecture approach if helpful. Best regards, Dr. Rajesh Rolen

@ngnsoftwareworld

‼️ IF YOU’RE NOT HAPPY YOU DON’T PAY ‼️ Hi, This is a serious real-time system, and honestly, getting HLS + WebRTC working together in a scalable way is where most teams struggle—I’ve already worked on similar streaming and real-time platforms, so I’m confident I can help you build this properly from day one. I’m a senior .NET developer with 8+ years of experience in C#, ASP.NET Core, and distributed systems. Over the past few years, I’ve worked on real-time apps involving video pipelines, SignalR, and event-driven architectures, including RTMP ingest + FFmpeg processing and WebRTC-based private communication flows. My approach: For public broadcasts, I’ll set up a clean pipeline: RTMP ingest (NGINX RTMP or AWS MediaLive) → FFmpeg transcoding → HLS packaging (.m3u8/.ts or LL-HLS if needed) → CDN (CloudFront or similar). This ensures scalability for large audiences. For private/group sessions, I’d integrate WebRTC using LiveKit (or similar SFU), handling signaling, room lifecycle, and token-based access. This keeps latency low and supports scaling across multiple sessions. SignalR will handle chat, reactions, and real-time events, backed by Redis (pub/sub + scaling). PostgreSQL for core data, with proper indexing and session tracking. I design systems with clean architecture, Dockerized deployment, and clear API layers (Swagger included). Also experienced in handling auth (JWT), entitlement logic, and performance tuning under load.

@Hrolgar

The architecture split here is what makes or breaks this platform. HLS and WebRTC aren't just two features, they're two completely different media stacks. HLS handles your public broadcasts (10-30s latency, one-to-many, CDN-friendly), WebRTC handles private sessions (sub-500ms, few-to-few, much heavier on infra). Trying to shoehorn them into the same pipeline is where these projects usually go sideways. My approach: RTMP ingest via NGINX-RTMP or AWS MediaLive depending on your infra preference, FFmpeg transcoding to HLS (.m3u8/.ts segments), CloudFront as CDN origin. The .NET API doesn't touch media at all, it handles token issuance, access control, and orchestration. For WebRTC, LiveKit is the right call, open source SFU with a solid .NET SDK, scales horizontally, and keeps your private session logic clean. The platform lives in the access layer. JWT scopes control who gets a LiveKit room token, who's on a paid HLS stream, who can tip. That's the core and it maps well to ASP.NET Core + SignalR + Postgres + Redis (session state + rate limiting). Phase 1 deliverables: - RTMP ingest pipeline to HLS output with FFmpeg tuning for target latency - LiveKit WebRTC integration for private 1:1 and group sessions - SignalR chat with room scoping - JWT token service with broadcast and session access control - Tipping transaction hooks (payment processor integration) - Docker Compose deployment, Swagger docs I'm a senior .NET developer, ASP.NET Core is my day job. SignalR, JWT, Postgres, REST, all standard. I've worked through the NGINX-RTMP vs MediaLive trade-off on real projects. 37,500-75,000 INR won't get you a solid Phase 1 with this stack. I'm proposing 125,000 INR / 30 days for delivery that won't need to be rebuilt at Phase 2. Three quick questions: self-hosted ingest (NGINX-RTMP on your infra) or AWS MediaLive? Expected concurrent viewers at launch, that changes CDN and origin scaling significantly. Is tipping going through Stripe Connect or something else?

@arshkumar213

I will build a scalable .NET streaming backend with RTMP→FFmpeg→HLS pipeline, WebRTC (LiveKit) for private sessions, and SignalR for real-time chat. Includes JWT auth, room logic, and Dockerized deployment. Result: low-latency, production-ready streaming system supporting broadcast and interactive sessions.

@Sufyan0Khan

My name is Hafiz Muhammad Sufiyan, a seasoned .NET(C#) developer with over five years of experience in building scalable web applications. I've worked extensively with ASP.NET Core, FFmpeg, RTMP configurations, and HLS streaming, aligning perfectly with your project's needs. Prioritizing clean, structured, and maintainable codes, you can rest assured that I'll deliver production-ready backend implementations. My track record in live-streaming platforms development would also come handy in this project. I understand the need for fast turnarounds while guaranteeing security and scalability- qualities I possess that parallel the demands of HLS broadcasting pipeline from RTMP → HLS as well WebRTC private sessions. Commitment to quality also permeates into my system architecture decisions when handling functionalities such as broadcast rooms (HLS), private sessions (WebRTC) and group sessions(WebRTC)- an area your project will benefit greatly. Given my expertise in PostgreSQL and Redis (both of which are stipulated in the project requirements), my experience is supplemented with Docker and Kubernetes proficiency to provide a scalable setup. Lastly, as a problem-solving freelancer aligned with the dynamicity of your project's requirements, timely and satisfactory delivery remains paramount on my agenda. Choose me today for dedicated service to get your live streaming platform off to a fitting start!

@tonyl63

As a seasoned dotNET developer with a wealth of experience in designing and creating live-streaming platforms, I'm confident that I can meet your needs effectively. My prowess in HLS streaming coupled with setting up RTMP ingest and FFmpeg aligns perfectly with your project requirements. I understand the importance of optimizing streaming latency and performance while ensuring a seamless end user experience, and this has formed the cornerstone of my career so far. Over the years, I've built a reputation for delivering scalable and maintainable code, which is particularly important for the long-term success of any application, let alone a live-streaming platform. My knowledge of Media servers/CDN streaming (including NGINX RTMP) will be invaluable as we establish an efficient pipeline for your broadcast using HLS. Likewise, my competencies in WebRTC (particularly LiveKit as you need) reaffirm my capability to tackle private sessions head-on. Lastly, my familiarity with SignalR rounds out the skill set you need for your project as it allows me to create real-time features like chat and events that guarantee smooth communication between users & creators. Given my prior successes building live-streaming platforms & OTT/video platforms (which also involved real-time communication), I'm confident we'll achieve great things together.