Tools
That Work
Every platform decision at Dyzyrai starts with a single question: does this make the learning experience more reliable, more responsive, or more useful for participants? We run 14 concurrent live streams across 6 time zones without degradation — not because we invested in expensive hardware, but because we chose the right architecture from the start.
How the
Stack
Is Built
Dyzyrai's platform is not a single monolith — it is a set of focused services that each handle one job well. The broadcast layer, the chat and polling engine, the recording pipeline, and the participant management system run independently. When one component needs updating, the rest keep running. This separation is what allowed us to ship 23 platform improvements in 2024 without scheduling a single maintenance window.
Participant-facing tools are built on a progressive web architecture — no app install required. A participant joining from Warsaw and another joining from São Paulo both open the same URL and reach the same session within 1.2 seconds on a standard broadband connection. Mobile performance is treated as a first-class requirement, not an afterthought: 38% of Dyzyrai participants attend sessions from a phone or tablet.
The recording and replay system stores sessions in a format that allows chapter-level navigation. A 90-minute webinar becomes a searchable, indexed resource within 8 minutes of the session ending — no manual editing required.
Broadcast Layer
The streaming engine uses WebRTC for presenter-to-platform and HLS for platform-to-participant. This split keeps latency low at the capture point while ensuring compatibility across every device and network condition. Adaptive bitrate encoding adjusts quality 4 times per second based on each participant's measured bandwidth.
Interaction Engine
Chat, Q&A, polling, and hand-raise signals run over a dedicated WebSocket cluster separate from the video pipeline. During a session with 800 participants, the interaction engine handles around 3,400 events per minute without affecting stream quality. Moderators see a prioritised queue — not a flood of unfiltered messages.
Data and Access
Participant access is managed through OAuth 2.0 with optional single sign-on for organisations that need it. All session data — attendance, engagement signals, poll responses — is available via a structured export within 2 hours of session end. GDPR compliance is built into the data layer, not bolted on afterward.
Tobias Wrenfeld
Platform Engineer
We spent four months choosing the streaming architecture before writing a single line of production code. The uptime numbers we have now are a direct result of that patience. Rushing infrastructure decisions is how you end up firefighting during live sessions.
- Stream reliability engineering
- Latency optimisation across regions
- Failover architecture design
Renata Olejnik
UX and Frontend Lead
The interface a participant sees during a live session has to be invisible — it should never make them think about the tool. We run usability tests with participants from 12 different countries because what feels intuitive in one context can be genuinely confusing in another.
- Cross-cultural interface design
- Progressive web application build
- Accessibility compliance (WCAG AAA)
Marek Szymański
Data and Security Architect
Organisations joining Dyzyrai often ask about data residency first. That is a reasonable question — participant data for European organisations stays within EU infrastructure by default. We do not treat this as a premium feature; it is the baseline.
- GDPR-compliant data architecture
- EU data residency by default
- Access control and audit logging