Zylinc uses Microsoft Azure as a basis and utilizes Docker to host the microservices that make up the solution. Docker provides an infrastructure for isolated services sharing a common pool of computing resources. Each virtual machine acts as a Docker host, which hosts several microservices in Docker containers, and as a group. These virtual machines will share the load, and redistribute the work across all the grouped VMs, called a Docker swarm.
ZYLINC CLOUD builds upon the Asterisk PBX software for non-peer-to-peer communication. The Asterisk is the Zylinc Cloud SIP Trunk.
Access to the ZYLINC CLOUD infrastructure is controlled by an Azure firewall. Access from the outside of the firewall is limited to standard ports for HTTPS except for WebRTC traffic (voice over IP) that uses one separate HTTPS port per tenant for SIP control and a range of UDP ports for the media stream (audio) itself.
Access from the inside of the firewall is granted at different levels to designated Zylinc employees.
All Zylinc software developers working from the Zylinc office, and their home addresses, are IP-whitelisted giving them access to the Docker swarms running the ZYLINC CLOUD backend microservices. Access is further restricted by a shared password. Further they have access to Azure SQL databases on a needs basis, controlled by Zylinc DevOps personnel. Password renewal for shared passwords takes place every second month.
Once a year, Zylinc will have an external security company conduct a penetration test against access to restricted resources.