Jitsi / WebRTC Engineer: Customize Jitsi Meet with Auto-Recording & Live Observer Portal

@serazummunirz

Hi There, Hope you are well. I have extensive experience customizing Jitsi Meet and deploying WebRTC projects. I can fulfill all the requirements listed, including automatic recording and retention, live observer portal setup, and admin dashboard customization. My expertise in DevOps and backend development make me an ideal candidate for this project. "JITSI-READY" Thanks in advance for the opportunity to working with you. Best Regards, Serazum

@Beannsofts

JITSI-READY You need a production-grade Jitsi platform with automatic recording, live observer streaming, and full white-labeling, deployed on DigitalOcean with JWT auth and consent workflows built in. I would deploy Jitsi Meet with Prosody, Jicofo, Videobridge and coturn on DigitalOcean, configure JWT authentication with your backend issuing tokens for host, participant, observer and reviewer roles, and rebrand the web and mobile apps by forking the Jitsi Meet repositories and replacing branding assets, domain and bundle IDs. For auto-start recording I would hook into Prosody's MUC events to trigger Jibri when the first participant joins, and scale recording workers using Docker Swarm or Kubernetes with a queue-based dispatcher. Recordings would upload to DigitalOcean Spaces with server-side encryption, indexed in PostgreSQL with metadata and delete-after timestamps, and served via time-limited signed URLs. For the live observer portal I would use SRS as the media server because it handles RTMP ingest from Jibri and serves LL-HLS or WebRTC with lower latency than NGINX-RTMP, and build the observer frontend in React with role-based login, MFA and audit logging. The consent flow would be a custom pre-join screen with checkbox, stored consent records, and persistent recording and monitoring badges injected into the UI. I have a 4.99 rating from 149 reviews, 143 projects completed, 99.5% on time and 99.8% on budget. My backend work on the Binance Trading Bot and 10XTraders platforms involved real-time data pipelines, role-based dashboards and signed API tokens, which overlap with your admin dashboard and observer auth requirements. Will you handle the mobile SDK customization in-house, or do you need that included in the scope? Let's talk and get started. Thank you.

@intelliresponse

JITSI-READY Hi, I have experience deploying and customizing Jitsi/WebRTC platforms with Docker, JWT authentication, Jibri recording, TURN, and cloud infrastructure. I can handle the full setup including white-label branding, auto-recording workflow, storage/retention, observer streaming portal, and documentation. I’ll use Jitsi events to trigger Jibri automatically and design a scalable recording worker setup. Available for a paid test task and milestone-based delivery.

@AITSoft

JITSI-READY Hi, I understand you need a self-hosted, fully rebranded Jitsi platform on DigitalOcean with JWT roles, secure TURN, automatic Jibri recording, retention controls, and a separate observer portal. I would first deploy and test Prosody, Jicofo, Videobridge, coturn, and Jibri in the EU region, keeping the setup ready for a later Asia region. Recording can start from room events when the first participant joins, while workers are managed to handle active meetings. I would use SRS with LL-HLS or WebRTC for the observer stream, depending on the required delay and browser support. Node.js or Python can handle the backend, consent records, signed playback links, MFA, audit logs, and admin APIs. Android integration can be handled through the Jitsi SDK, with all changes tracked in Git and supported by rebuild scripts and documentation. I can provide a milestone plan covering infrastructure, core meeting features, recording and storage, observer access, dashboard, testing, and handover. The exact monthly cloud cost will depend mainly on concurrent meetings, recording length, and storage volume. How many simultaneous meetings, participants, and recording hours per day should the first production setup support? I am ready to begin with the paid test task and can provide a clear delivery plan with 30 days of bug-fix support after launch. Regards

@Web1devloper

JITSI-READY With my extensive experience in both DevOps and web development, I believe I would be an ideal pick for the Jitsi/ WebRTC project you're undertaking. Over my 8-year career, I've deployed multiple Jitsi projects, and one notable one that aligns well with your needs is a virtual conference platform for a multinational client. To ensure optimal performance and fast scaling of your recording works such as `Jibri`, Kubernetes would be the appropriate choice for orchestration, leveraging its built-in auto-scaling feature. In the case of auto-starting Jibri recording per room, this can be achieved by incorporating a customized logic into Prosody which triggers recording start as soon as the first participant connects. For live observer streaming, I suggest using SRS (Simple RTMP Server) due to its good track of performance and flexibility. When it comes to security and scalability amidst your EU and Bangladesh locations, I 'm well-versed in best practices to guarantee encryption both in transit and at rest with MFA enhanced role-based access.

@denisSolution

JITSI-READY Hello, I'm Denis, a full-stack developer with production experience deploying and customizing Jitsi Meet, including Jibri recording, Prosody configuration, and videobridge scaling. You need a fully rebranded, self-hosted Jitsi platform with automatic recording, cloud storage, retention policies, and a live observer portal for secure team collaboration across Bangladesh and the EU while meeting GDPR requirements. I understand server-side recording requires disabling end-to-end encryption and have worked around this. My approach: 1. Confirm role hierarchy and consent flow with you 2. Deploy core stack on DigitalOcean EU (Prosody, Jicofo, videobridge) 3. Set up self-hosted coturn with time-limited credentials 4. White-label the web app and integrate Jibri for auto-start recording 5. Build recording worker pool with autoscaling and encrypted cloud uploads 6. Deploy observer portal using SRS for low-latency HLS playback with JWT role-based access 7. Create admin dashboard, test full flow, and provide 30 days of support Key challenges and solutions: - Scaling Jibri reliably: Docker Compose with health checks, job queue for recording tasks, and retry logic - Consent requirements: Propose a template with per-region text and version control for easy updates Technical details: - Auto-start recording uses Jibri's REST API with webhook on first participant join - Worker scaling via Docker Swarm or Kubernetes (your preference) - SRS for observer stream with low-latenc

@bcosley

Hi, You're building a self-hosted Jitsi Meet with auto-recording, an observer portal, and full white-labeling, with EU-first deployment and a plan to add Asia later. I’ve delivered similar deployments with JWT auth, scaled Jibri, and encrypted storage integrations. I’d start by validating the current Jitsi stack and the recording trigger, then enable per-room Jibri startups, implement a worker pool that scales with meetings, and wire in encrypted storage with meeting metadata. This keeps changes incremental and testable against real usage patterns before broader rollout. One technical risk / key challenge: Coordinating consent persistence with real-time events and GDPR-aligned retention could be tricky. Two clarification questions: What should happen to an ongoing recording if the meeting ends unexpectedly and a new session starts later with the same ID? How should observer access be refreshed or revoked when MFA or roles change mid-cycle? If we're aligned, I’d be happy to walk you through the implementation plan before we get started. Best regards, Brandon

@shadabkhan92

JITSI-READY. Harnessing our seasoned experience in deploying and customizing Jitsi Meet projects, my team and I are ready to take your platform to the next level. Our comprehensive understanding of Jibri, Prosody, and the videobridge, in conjunction with extensive backend skills in Node.js and Python, makes us the perfect fit for this task. We are well-versed with automatic recording hooks and scaling recording workers ensuring that meeting data is captured seamlessly and efficiently. When it comes to streaming, our proficiency in RTMP, HLS, WebRTC, integrating media servers like SRS and NGINX-RTMP will enable us to develop the live observer stream utilizing the most optimal solution for your requirement. Security being paramount, we ensure encryption in transit and at rest as well as enforce role-based access via MFA.

@gutibs

JITSI-READY Hi! This is a build we can take on end to end — not an experiment for us, it's territory we know well. One thing worth nailing down before pricing out milestones: do you expect concurrent meetings to stay in the low double digits, or should we design for real scale from day one? That answer decides whether Jibri workers run on a fixed pool behind a queue or whether we need a DigitalOcean autoscaling group reacting to meeting load — it changes both the infra cost structure and how soon monitoring and alerting need to be production-grade. On the architecture: Jibri triggered automatically via Jicofo's conference-start event, writing straight to encrypted Spaces with a Postgres row per recording for retention tracking and the 180-day purge job. For the observer stream, we'd lean toward SRS over NGINX-RTMP — better LL-HLS support and lower latency for live listening without joining. JWT auth through your backend, role separation for host/participant/observer/reviewer, and the consent/notice flow all sit cleanly on top. The EU-first, Asia-later region split is a sound call and doesn't complicate the initial deployment. We'd rather lock the recording and streaming architecture with you before breaking down milestone pricing. Happy to go through specifics here. Gustavo & the DoTheCode team

@teodorgeorge

JITSI-READY Hi, I can approach this as a secure, self-hosted communications platform with a clear workflow: Jitsi deployment and rebrand → JWT-based roles → consent capture → automatic recording → encrypted storage and retention → observer access → audit/admin reporting. My relevant experience includes deploying and maintaining server-based monitoring platforms, building Node.js API pollers, Python integrations, dashboards, role-based multi-tenant workflows, and operational documentation. I would structure the deployment and configuration so the EU installation is maintainable and ready for future regional expansion. For recording, I would implement a room-join workflow that triggers a recording worker when the first authorized participant enters, then tracks meeting state to prevent duplicate jobs. Recording metadata, consent version, retention date, and deletion status would be indexed for administration and scheduled cleanup. For the observer capability, I would first validate the media and access-control path with a small proof of concept before building the portal, ensuring observers are authenticated, auditable, and clearly indicated to participants. I do not have a public Jitsi/WebRTC deployment link to claim. I can, however, provide disciplined infrastructure work, backend integration, monitoring, documentation, and handover based on my experience delivering production server and platform workflows.

@arslanshahid386

Hi, I understand you are seeking to enhance a self-hosted Jitsi Meet platform on DigitalOcean with features like auto-recording and a live observer portal. This project requires not only customization but also a deep understanding of Jitsi's architecture and integration capabilities. The main challenge here is ensuring that the auto-recording and observer functionalities are seamlessly integrated without compromising the platform's performance or security. My approach would be to first assess the current setup, prioritize system stability, and then methodically implement these features while ensuring scalability and data retention protocols are adhered to. I have extensive experience working with Jitsi and WebRTC technologies, along with solid DevOps skills, which have been instrumental in similar projects involving complex integrations and customizations. Q1 – What specific retention policies do you want for the recorded sessions? Q2 – Are there any particular branding or UI/UX requirements for the observer portal? Q3 – Do you have existing infrastructure preferences or constraints on DigitalOcean that need to be considered? Looking forward to discussing how I can help you achieve your project goals.

@zditanuel

I've worked with Jitse before. The 180-day purge with matching DB rows I wire through the same job as the consent flags. One thing: should observers join as real participants or view via a separate relile

@AZTURK1

JITSI-READY I understand the deployment requirements for running branded Jitsi on DigitalOcean with multi-role JWT, automated Jibri triggers, and an isolated observer portal. ✅ Production Jitsi stack (Prosody, Jicofo, JVB, Coturn on TLS 443) fully white-labeled with custom JWT auth (host, participant, observer, reviewer) ✅ Auto-recording via custom Prosody room hook calling an orchestrator service to spawn Jibri workers, auto-scaling on DigitalOcean API based on active meetings, uploading encrypted to Spaces with 180-day lifecycle purge ✅ SRS (Simple Realtime Server) deployment ingesting Jibri RTMP and serving low-latency WebRTC/LL-HLS to the observer portal with audit logs and MFA ✅ Complete staging environment and droplet snapshots taken before production cutover ✅ 10+ years production experience | 400+ completed projects | 320+ five-star reviews ✅ Microsoft® Certified: MCSA | MCSE | MCT & cPanel Certified (CWSA-2) Infrastructure will run ~$90-150/mo on DigitalOcean depending on concurrent Jibri worker demand. I am in CET with full availability. Are you building the mobile apps from the Jitsi React Native SDK internally, or do you need the branded iOS/Android builds packaged as well? I can deliver this in 1 day for 240 USD and can jump on it right now.

@razmiks2

Hi, I’ve deployed and customized self-hosted WebRTC video platforms with React/Node.js APIs and production-grade automation. I will tailor a single-region Jitsi Meet on DigitalOcean, fully rebrand it, and wire JWT roles plus EU/near-Bangladesh quality needs. I’ve integrated automated media processing pipelines with Python and Node.js backends to ensure reliable uploads, retention, and access controls. Best, Razmik

@efanntyo

Hi there, JITSI-READY. I am excited about the opportunity to collaborate on customizing your Jitsi Meet platform. With extensive experience in deploying and enhancing Jitsi solutions, I am well-equipped to meet the needs outlined in your project scope. My background includes successful deployments of Jitsi Meet with Jibri for automated recording, as well as expertise in handling media servers like SRS for streaming, ensuring seamless observer experiences. Understanding the importance of call quality and data location, I propose deploying your solution on DigitalOcean's EU datacenters, with scalability for future expansion to Asia. My approach will ensure robust JWT authentication and efficient autoscaling of recording workers to accommodate fluctuating meeting loads. Additionally, I will implement encrypted cloud storage solutions for secure recording retention, adhering to your 180-day deletion policy. I am adept at backend development using Node.js and Python, and have a strong foundation in DevOps practices, including Docker and infrastructure as code, to ensure a smooth, reliable deployment. My familiarity with GDPR principles will guide the implementation of notice and consent features, crucial for user transparency. Please let me know if there are specific areas you'd like to discuss further. I am eager to contribute to delivering a customized, high-quality Jitsi Meet platform for your team. Best Regards,

@jayantkumar314

JITSI-READY I can deploy and customize the complete self-hosted Jitsi stack on DigitalOcean, including Prosody, Jicofo, Videobridge, coturn, JWT authentication, recording/storage, observer access, monitoring, security, and full white-labeling. For recording, I’d automate Jibri triggering based on room/participant events and use multiple Jibri workers as concurrent meeting demand increases. For the observer layer, I’d use SRS for the RTMP/WebRTC/LL-HLS pipeline because it provides more flexibility for low-latency streaming. I can share relevant experience privately. I’m open to your paid test task and milestone-based delivery. After reviewing the expected concurrent meetings, recording volume, and mobile requirements, I can provide an accurate timeline, fixed milestone pricing, and monthly infrastructure estimate.

@longngoc2307

==== Hi - Truong here ==== "JITSI-READY WEBRTC PLATFORM" - you need a secure Jitsi setup with recording and observer access built around your rules. I would handle this by keeping Jitsi core stable and adding the recording, access control, and observer layers around it. For auto recording, I would use room events with Jibri control hooks, then manage recording workers separately so one busy meeting does not affect others. The key part is making consent, retention, signed playback links, and observer audit logs work together. I would also design the deployment so adding an Asia region later does not require rebuilding the whole stack. My approach would use Jibri for capture and SRS or NGINX-RTMP for the observer stream depending on latency and scaling needs. Which existing backend should handle JWT roles and user identity: your current system or a new service built with this platform? Looking forward to work with you.

@TechizeBuilder

Dear Client, I read "Web-based Custom Voice Text-to-Speech Tool" carefully and understand your requirement. My experience with AI integration, full-stack development, and voice-based applications aligns well with this project, and I can help you build a reliable, scalable and user-friendly solution tailored to your workflow. I can handle the complete development cycle, including UI/UX implementation, frontend, backend, custom voice text-to-speech engine integration, API development, database management, third-party services, and deployment. I have worked on AI-powered web tools, including speech synthesis systems, custom voice generation, and real-time audio processing platforms designed for smooth performance and high-quality output. A couple of quick questions: 1. Do you already have a preferred TTS/AI voice API, or should I suggest the best options? 2. Is this a standalone tool or should it be integrated into an existing platform? Thanks & Regards, Deepak

@kumarashish99

JITSI-READY: With a strong background in backend development and DevOps engineering, I bring comprehensive skills to customize and extend Jitsi Meet to meet your unique needs. Having worked with Jitsi's primary components like Jibri, Prosody, and videobridge, my experience aligns perfectly with your project requirements. I have successfully deployed complex Jitsi projects in the past, and familiar with automatic recording hooks and scaling recording workers for optimal performance and scalability. The media server I would leverage for the live observer stream is SRS or NGINX-RTMP which have proven to be reliable and flexible in handling real-time streams. Furthermore, I ensure safety and GDPR-compliance by implementing robust security measures, including encryption in transit and at rest, role-based access control mechanisms, MFA among others. In addition to delivering a fully-customized and scalable platform upon completion of the project, I'll also provide robust documentation on architecture, deployment procedures alongside a short hands-on session to ensure seamless handover. As my timezone aligns well with Bangladesh - EU working hours (+2 GMT), you can expect constant communication during the entire project lifespan. Looking forward to leveraging my skills for a successful collaboration that guarantees your utmost satisfaction!