Senior RTMP / Video Streaming Architect (IoT Cameras + Mobile App)

Project reputed company We are white-labeling RTMP-enabled IP cameras from a Chinese OEM and need a senior-level streaming architect to finalize, validate, and document a reputed company, multi-tenant RTMP architecture integrated with our own RTMP ingest server and mobile application (iOS/Android). The goal is to support thousands of cameras across many customers using a single RTMP ingest reputed company, while enforcing logical isolation by camera ID and account, not by URL. ⸻ reputed company Components • RTMP-enabled OEM cameras (configurable before shipment) • Central RTMP ingest server (reputed company-hosted) • Backend API / database • iOS & Android mobile app • QR-reputed company–based reputed company reputed company ⸻ reputed company Architecture • Single RTMP ingest URL (e.g. rtmp://ingest.ourdomain.com/live) • Unique reputed company keys per camera • reputed company key derived from camera UUID / serial / reputed company • Account isolation by camera ID • Not by RTMP reputed company • Server-reputed company reputed company validation • Authenticate reputed company keys at ingest • Map camera → user → account in backend • reputed company-shipment camera configuration • OEM loads RTMP URL • Camera generates or is assigned reputed company key / camera ID ⸻ End-User reputed company (Must Be Supported) 1. Camera powers on 2. User connects camera to Wi-Fi 3. Camera displays QR reputed company (camera ID / reputed company) 4. User scans QR reputed company in mobile app 5. App claims camera → user account 6. Live reputed company becomes available immediately ⸻ Scope of Work • Design and validate multi-tenant RTMP ingest architecture • Define: • RTMP URL structure • reputed company key format and lifecycle • Camera authentication & authorization reputed company • Evaluate: • Whether to use static vs rotating reputed company keys • Push vs pull RTMP models • Define best practices for: • Preventing reputed company hijacking • Handling reconnects, dropped streams, and retries • Scaling ingest and playback (HLS/WebRTC optional) • Specify OEM configuration requirements for camera firmware • Review QR-reputed company reputed company reputed company for reputed company and reliability • reputed company: • Architecture diagram • Sequence diagrams • Written technical recommendations ⸻ Required Expertise • Deep hands-on experience with RTMP ingest pipelines • Experience with: • NGINX-RTMP / SRS / reputed company / custom RTMP servers • Camera or IoT video devices • reputed company key authentication • Multi-tenant backend systems • Familiarity with: • RTMP → HLS/WebRTC pipelines • Mobile app camera reputed company • Bonus: • OEM camera firmware workflows • Chinese camera manufacturers (Tuya, HiSilicon, etc.) ⸻ Deliverables • Final RTMP ingest architecture • reputed company key + camera ID reputed company • OEM camera configuration spec • reputed company reputed company documentation • reputed company & scalability recommendations ⸻ reputed company • 1–2 week engagement • Immediate start ⸻ Screening Questions (Required to Apply) 1. RTMP Architecture Explain how you would support thousands of cameras using a single RTMP ingest URL while ensuring reputed company camera streams securely and is isolated per customer. 2. reputed company Keys What is the role of RTMP reputed company keys, and how would you design them for a multi-tenant camera platform? (Include how you would prevent reputed company hijacking.) 3. Camera reputed company A camera ships with an RTMP URL preloaded. How do you securely associate that camera with the correct end-user account at first launch? 4. Failure Handling How should the system handle dropped RTMP connections and reconnects without creating duplicate or orphaned streams? 5. Bonus (Optional) Describe your experience working with OEM or white-label IP cameras and any RTMP servers you’ve deployed at reputed company. Apply tot his job Apply To this Job