For IT · network and routing

Network and routing

Each meeting runs through one node. This ensures all participants land in the same room instead of splitting across transports. The route is selected automatically by meeting size and node availability.

For the business overview, see the company document. For node installation, see the company node guide.

Node types

Node	Purpose	Limits
Company server	Always-on operation, critical meetings, larger rooms	Requires a server and access; configured by Meeter
Browser	Quick start without a separate server	Up to 6 participants while the tab is active
Phone	Small meeting from the app	Up to 6 participants while the app is active

If no suitable node is available, the meeting runs through Meeter's central server. For companies with data requirements, the primary scenario is a dedicated server node.

How the route is selected

Room size, node availability and network state are considered.
The route is pinned to the room so all participants use one transport.
If a node becomes unavailable, the meeting moves to a fallback route; participants stay in the same room.
The route can be agreed at launch; for critical meetings, use a server node.

What the node operator sees

The node operator is the company or its IT team providing the server. In protected mode, the node relays encrypted data and does not read communication content. It sees network metadata: addresses, time, duration, volume and packet timing.

The node does not store meeting recordings by default. Recordings and transcripts are a separate feature enabled by the company.

Continuity and support

SLA and uptime are fixed in the contract; for critical meetings, plan a backup communication channel.
Meeter updates the node and monitors its status; the company provides the server and access.
License suspension does not delete company data; exports and backups stay in the company environment.
Support is by email; terms and target response time are fixed in the contract.

Limitations