I just double-checked, and it seems that the logistical team stores the tawk.com code behind a paid line, just like talky.io.
In the webRTC ecosystem, providers are either focused on
the application, and the backend is hidden (think Skype or bistri, although the bistri also rotates to offer an API.)
a PaaS and then both code codes are hidden, and you will not have an application, at best a demo, because they do not focus on any verticals and do not execute business logic (think AWS in general or tokbox, temasys for webRTC)
- offer consulting / application development and will provide the full application most often with open source, but the preservation of some key components (priologic: mobile SDK + application, and more: application, algoworks, ...) for paid access. Usually they are combined with the Paas provider and Hardware provide a more comprehensive / scalable solution for their client (priologic / oracle, ...).
This is very unlikely, and I would not know that there is a provider who will provide a complete open source solution. It is still too complicated to provide a nonprofit organization. Those that provide a complete solution do this for a limited amount.
In any case, the application always focuses on the use case. Although the underlying infrastructure may be the same, and the BE / client API may be the same, the contact center application and the social dating application and the conferencing application will be completely different because they implement a completely different business logic and address a completely different market. It is reasonable not to expect a full stack, but to have only the topmost layer left for implementation.
I posted a list of suppliers and products there , but it's a little crude. So, here is the recipe for creating free / open source, and then where to look for updates:
- required: open source signaling server ( easyrtc , signalmaster , peerjs-server , rtc.io , ...)
- Mandatory: BE API ( easyrtc , simplertc , peerjs , rtc.io respectively)
- optional, but highly recommended: add the free rfc5766 server or the most advanced version of "coTurn". Some of the open source servers and libraries offer examples or how to maintain this TURN server yourself.
- optional: a client API that brings you closer to your use case,
- optional: free plug-in for supporting IE and Safari ( free temasys template ),
- optional: media server if you need to receive many-to-many calls or conferences (MCU or SFU) ( licode , meteecho janus , medooze , kurento , jitsi videobridge )
- optional: SIP gateway for connecting to VoIP and / or pone by extension (PSTN). and ... about how much you can go with open source / free libs today. You can quickly solve the scalability problem depending on your traction.
The next step is to create hosted servers, but this is no longer free.
Separate servers:
- ICE / TURN / STUN: see xirsys / twilio for a hosted solution,
- Media server: see dialogic, radisis, for hardware and meedoze, Jitsi, acano , pexip , openclove for software / hosted solutions,
Full Paas, including all of the above:
- tokbox (be careful with the streaming minutes protocol if you have large conferences, have a recording, and some temasys features are not installed yet)
- temasys
- some media server manufacturers also sell themselves as PaaS. I have not tested, so I can not comment or recommend.
- If you want to connect to a SIP / phone, you will need different providers, as temasys and tokbox provide interoperability today.