Budget: 1500 USD Deadline: 7 days
I will deploy OpenVidu on a dedicated server, configure the stream reception from OBS, and deliver it to viewers via WebRTC. A delay of up to 400 ms is realistic with the right hardware selection and tuning of Kurento. I have experience with media servers and low-latency streaming. Question: Is the server already available or do we need to find hosting for several hundred simultaneous viewers?
Budget: 1500 USD Deadline: 7 days
Good day, I have extensive experience in successfully solving similar tasks, I will complete your project quickly and efficiently.
Budget: 1500 USD Deadline: 7 days
Hello. I can offer the deployment of OpenVidu via Docker Compose with a description of the server configuration in Ansible. This approach will allow not only to set up the server but also to quickly and uniformly reproduce the configuration on other machines later. If necessary, I will also prepare instructions for launching and maintenance.
Budget: 1500 USD Deadline: 5 days
Hello,
I’d be happy to help with this project. I understand the main goal is to set up OBS → OpenVidu → browser viewers with very low latency, ideally under 400 ms, while keeping the system suitable for future scaling.
For Stage 1, I can help with:
-dedicated server selection
-OpenVidu installation and configuration
-OBS publishing setup
-browser playback testing
-end-to-end delay measurement
-basic load and stability evaluation
My focus would be to validate the streaming architecture properly before moving into Stage 2, so the future website and admin panel are built on a reliable foundation.
I’d be glad to discuss the budget and details further.
Best regards,
Nikola
Budget: 1800 USD Deadline: 20 days
Hello, Alexey!
I am ready to implement a streaming system based on OpenVidu, taking into account the requirements for latency and stability.
I would like to note right away: the task is not limited to server installation. It is important to correctly assemble the entire pipeline (OBS → WebRTC → browser), achieve stable transmission, and keep the latency to ~400 ms, as well as lay the foundation for load handling.
From my side:
— selection of a server for WebRTC (CPU, network, region)
— deployment of OpenVidu (Kurento)
— configuration of the streaming pipeline through OBS
— configuration of WebRTC and checking latency
— testing viewing in the browser
— basic load testing and system behavior analysis
The output will be a working streaming system with latency measurements and recommendations for scaling.
Full operation for hundreds of viewers and optimization for load.
Deadline: 20 days
Cost: $1800
I have a couple of questions:
Do you plan to use a single server or consider scaling (multiple nodes) in the future?
How critical is it to maintain latency at ≤400 ms under all conditions, or are deviations acceptable with increased load?
After completion, I will add a bonus: I will prepare recommendations for scaling architecture so that the system can grow without loss of quality.
I look forward to collaborating!
Budget: 1550 USD Deadline: 7 days
Achieving sub-400ms latency for your OpenVidu streaming setup is entirely feasible by implementing a pure WebRTC flow from OBS to the browser using WHIP or tuned zerolatency encoding. I will configure your OpenVidu instance to handle ingest without standard RTMP buffering, ensuring no B-frames and minimal jitter buffer delay for your end users.
With extensive experience in Kurento and WebRTC architectures, I will optimize your TURN/STUN configuration and media node distribution to handle hundreds of concurrent viewers without performance degradation. To give you an idea, we will manage the session lifecycle via the REST API like this:
const resp = await fetch(ov_url + '/api/sessions', {
method: 'POST',
headers: { 'Authorization': auth, 'Content-Type': 'application/json' },
body: JSON.stringify({ customSessionId: 'obs_stream' })
});
I am ready to help you select the right dedicated server to support your scaling needs and perform the initial stress tests. Let's start with the first stage to confirm the 400ms latency on your system.
Looking forward to discussing your project in detail.
Budget: 1500 USD Deadline: 13 days
I worked on https://ou-uv.com/cerberus — AI/HPC infrastructure with VMware, Nginx reverse proxy, and GPU networking for production load. Deploying low-latency streaming servers is the same kind of work.
OpenVidu is a good platform for WebRTC streaming — but to achieve latency below 400ms with a few hundred viewers, several things are needed beyond just the deployment. I will set up OpenVidu CE or Enterprise on a VPS, configure COTURN as a TURN/STUN server, Nginx as a reverse proxy with SSL, and optimize Kurento/mediasoup parameters for low latency. The OBS stream comes in via RTMP or WebRTC, and users watch through a browser. I will stress the architecture before launch and confirm that 400ms is achievable with your VPS provider.
What I will do:
- Deploy OpenVidu CE/Enterprise on VPS (Docker Compose or standalone)
- Configure COTURN (TURN/STUN) for WebRTC through NAT/firewall
- Nginx reverse proxy with SSL (Let's Encrypt)
- Integrate OBS as the stream source (RTMP/WebRTC ingest)
- Optimize latency: mediasoup/Kurento parameters, bitrate, keyframe interval
- Scalability testing: a few hundred viewers simultaneously
- Documentation of configuration and user manual
--- OPTIONS ---
A) Basic deployment: 1500 USD (13 days) — OpenVidu + TURN + Nginx SSL + OBS ingest + latency tests
B) Deployment + optimization + monitoring: 2400 USD (17 days) — A + auto-scaling config, Grafana/Prometheus monitoring, load testing report — best scope/price ratio
C) Enterprise with HA: 3100 USD (22 days) — B + high availability configuration, CDN integration, SLA monitoring
Delivery time: 13 days. I need VPS details (system, RAM, CPU, provider) and the target domain.
Portfolio:
- https://ou-uv.com/cerberus — AI/HPC server infrastructure, Nginx, VMware, production
- https://ou-uv.com/freya2 — ML platform with FastAPI and Docker, network architecture
- https://ou-uv.com — Flask + Python, deployment on VPS, multilingual
4 years in server infrastructure and DevOps — from VPS configuration to enterprise clustering.
Please write what your VPS parameters are and how many viewers you expect simultaneously at peak — I will tailor the architecture to your case.
Since I am new to the freelancehunt service and want to quickly gain a few initial projects for my portfolio, I am offering a 15% discount for the first 5 clients. The offer is valid until 5 orders are obtained.
Budget: 1500 USD Deadline: 5 days
Write in private messages. I will find a server for your task and install openVidu on it.
Budget: 1500 USD Deadline: 25 days
Hello! The task is clear. Achieving a delay of ≤400 ms with this scheme is an ambitious but entirely realistic goal when using WebRTC, on which OpenVidu is based.
Since OpenVidu uses Kurento (or Mediasoup in the new versions of OpenVidu 3), we avoid the traditional delays of HLS/DASH protocols (which usually range from 2 to 30 seconds). We can discuss the budget, expecting from 500-600 bucks, I can consider your option.
