The shared building blocks.
What LOBAKA products share, and the real stage of each block. For technical partners and IT leads.
Real-time audio
Already in placeLow-delay audio over WebRTC, through a media server (SFU). Each participant only receives the channel they picked; switching channels doesn't drop the connection.
Sasa · Pamoja · Picha
The audience's own phone
Already in placeParticipants listen in their own phone's browser. No app, no account.
Sasa · Pamoja · Picha
Sessions and QR codes
Already in placeOne session, one code, one QR. Personal, revocable links for speakers. Limits enforced by the server.
Sasa · Pamoja · Picha
Language routing
Already in placeWho listens to whom, in which language. Relay interpretation, loop rejection, alerts when a source drops. Explicit rules, no artificial intelligence.
Sasa
Synchronized media
In preparationOne shared video and several audio tracks locked to the picture.
Picha
Recording
In preparationKeep a tour or a talk, with the consent of the people recorded.
Pamoja
Usage measurement
Already in placeSessions, connections, channels, reconnections, demand per language. Aggregated figures, never tracking of a person.
Sasa
Voice intelligence
In researchTranscription, translation and speech synthesis, developed by LOBAKA Sauti.
Sauti
What the server enforces.
- HTTPS for pages and the API, encrypted WebRTC for audio
- Speaking and listening rights are enforced by the media server, not just the interface
- A participant can only listen to the session they have the code for; interpreter-only streams live separately
- No personal data required to listen
Proven components, a LOBAKA product.
Audio travels over WebRTC through an open-source media server; LOBAKA builds everything above it: sessions, channels, rights, routing, interfaces.
Every figure published on this site comes from a real measurement or configuration. What hasn't been measured yet is said to be so.
Want to integrate LOBAKA?
Venue, agency, publisher, institution: let's talk about your architecture.