Made on
Tilda
The option for those to whom hybrid is still too much cloud. Meeting media and their recordings do not leave the data centre in normal operation or in a failure: the cloud is simply not part of the design.
Meeting Connector is the on-premises, non-hybrid version of Zoom's meeting infrastructure. The meeting servers run in your data centres, and participants' media travels only between them. Unlike Meetings Hybrid there is no cloud fallback here: no cascading, no joining through the cloud, no cloud services. Account management stays in the Zoom web portal, and the meetings themselves are entirely on site.
Recording Connector complements it. It records meetings that run through Meeting Connector to your storage on site, without relying on the host's computer. Cloud recording is unavailable to such meetings by definition, and Recording Connector closes that gap locally.
The price of the solution is in features: cloud recording, transcription and other cloud services are unavailable, because there is no cloud in this design. For most companies the right choice is Meetings Hybrid with private mode. Meeting Connector remains for those whose rules forbid cloud fallback as a matter of principle. Both connectors belong to the Zoom Node family of modules.
Hybrid leaves the cloud as a fallback path. Some rules forbid a fallback path.
Meeting Connector cannot go to the cloud. This is not a setting that could be changed by accident, it is the architecture.
Recording Connector writes meetings on site. Without cloud recording and without depending on the host's machine.
Where is the media? In the data centre. Where are the recordings? In the data centre. Where does it go in a failure? Nowhere.
Architecture, limits, neighbours
Zoom's meeting infrastructure is deployed in your data centres. Participants connect to it, not to the cloud.
No fallback, cascading or joining through the cloud infrastructure. The meeting lives only on site.
Local recording of Meeting Connector meetings to your storage. Independent of the host's computer.
Neither audio, nor video, nor recordings leave the data centre. The perimeter is closed at architecture level.
Cloud recording, transcription and the other cloud services. They are absent because the cloud is absent.
The account, users and settings are managed in the Zoom web portal. On site there are only meetings and recordings.
Meeting and Recording Connector are listed among Zoom Node modules alongside Meetings Hybrid, Chat Hybrid and CRC Hybrid.
If the rules allow the cloud as a fallback, Meetings Hybrid gives private mode and survivability with the full feature set.
The connectors are licensed separately, paid. Virtual infrastructure in the data centre, storage for recordings and account administrator rights are needed.
Wherever the cloud is forbidden, not merely unwelcome
The rules forbid cloud fallback. Meetings and recordings inside the perimeter, full stop.
Meetings inside the agency's data centre, recordings on the agency's storage.
Negotiations for which even hybrid private mode does not pass the review.
Discussing developments inside the perimeter without external services. Recordings for the internal archive.
An isolated enterprise network. Zoom inside it, nothing outside.
Checking the rules: whether the non-hybrid option is really needed or private mode is enough, designing the site, deployment, storage for recordings, training. Then support in Russian.
A local perimeter is needed, but the capacity of a full hybrid is not.
A requirement to keep meeting recordings on your own premises.
Internal meetings stop travelling to the cloud and back.
We'll give you a remote demo Monday to Friday, 10:00–16:00 Moscow time, answer all your questions and provide trial access so you can explore the system yourself.
Please note: we work with legal entities only.