Online events and webinars
Global audiences, so multi-region servers, load balanced and placed close to participants to cut latency.
Consulting
WebRTC Consulting and Development Services
We design, build and fix real-time video. Architecture reviews, custom WebRTC apps, and Jitsi developers who run the platform in production.
- Architecture reviews and capacity planning
- Custom builds on Jitsi, LiveKit, mediasoup and Janus
- Fixes for calls that connect but show no video
WebRTC consulting services
WebRTC looks simple in a demo. Two browsers, a signalling server, done. Then you add a third participant, a corporate firewall, a mobile network and a recording requirement, and suddenly the architecture decisions you made in week one are the ones hurting you.
That is usually when people call a WebRTC consultant. Typical work:
- Architecture review: peer to peer, SFU or MCU, and which media server
- Capacity planning and load testing before a big launch
- Calls that connect but show no video. Nearly always NAT, TURN or UDP ports.
- Audio and video quality problems under real network conditions
- Security and compliance reviews for healthcare, education and finance
Custom WebRTC development
When an off-the-shelf meeting app is not enough, we build on top of open source instead of starting from zero. Our engineers write Node, C, C++, Java, Erlang, Lua and Go, which covers most of the WebRTC stack from the browser down to the media server.
Board and management meetings
Crisp audio, sharp screen share, and setups that get through corporate firewalls and locked-down networks.
Online education and tutoring
Whiteboards, quizzes, attendance lists and meeting security. See how Jitsi works for virtual classrooms.
Telehealth
Private consultations with data kept in your own infrastructure. More in video conferencing in healthcare.
Smaller jobs too: single-presenter broadcasting, a whole new meeting interface for a game, better chat and file sharing. All of it sits on the same open source stack.
Jitsi developers for your project
Jitsi is where we have gone deepest. We have written about it for years, from how its architecture fits together to scaling it past 1,000 users, and we sell ready Jitsi images on AWS and Google Cloud. If you need Jitsi developers, that is the shortest path to people who already know where it breaks.
For ongoing Jitsi work, see commercial support for Jitsi, Jitsi customization and Jitsi hosting on AWS, Azure and GCP.
WebRTC platforms we build on
| Platform | What it is | We use it for |
|---|---|---|
| Jitsi Meet | Complete meeting app on an SFU (the videobridge) | Meetings you host yourself, branded or embedded |
| LiveKit | Modern SFU with client SDKs for web and mobile | Video and audio built into your own product |
| mediasoup | SFU library for Node.js | Custom conferencing where you control every media route |
| Kurento | Media server with recording, mixing and filters | Apps that process video on the server |
| Janus | General-purpose WebRTC server, features come from plugins | Custom apps that need a small, flexible core |
| BigBlueButton | Virtual classroom with whiteboard, chat and attendance | Teaching, ready to go |
| FreeSWITCH | Software telephony stack | Phone dial-in, SIP and PBX integration |
| coturn | TURN and STUN server | Getting calls through firewalls and strict networks |
Not sure which one fits? The LiveKit vs Jitsi comparison is a good start if you are building a product rather than running meetings.
Where our customers are
Meetrix works with customers in the US, the UK, across Europe (Sweden, Germany, Finland, Norway, Denmark and Austria), in Australia, and in Asia, including India, Thailand and South Korea.
Frequently asked questions
What does a WebRTC consultant do?
Reviews or designs the media architecture, picks the right server (SFU, MCU or peer to peer), sizes the infrastructure and finds why calls fail or stutter. Most projects start with a short audit and a written plan.
Do you only work with Jitsi?
No. Jitsi Meet is what we are best known for, but we also build on LiveKit, mediasoup, Janus, Kurento, BigBlueButton and FreeSWITCH. We recommend whichever fits your product, even when that is not Jitsi.
Can you take over an existing WebRTC project?
Yes. We start by reading the code and the deployment, then write down what is broken and what is risky before changing anything.
Where are your customers based?
Mostly the US, UK and Europe, including Sweden, Germany, Finland, Norway, Denmark and Austria, plus Australia and Asia. Almost all of our work is done remotely.
How do WebRTC consulting services usually start?
With a call about what you are building and what is going wrong. Then a scoped piece of work: an audit, a proof of concept, or a fixed-scope build. Longer support contracts come after that, if they make sense.