Messengers for local networks can operate under different models, ranging from simple LAN solutions to enterprise platforms with servers hosted within a company's infrastructure. This article examines solutions deployed locally on company servers (on-premise).
What is a local messenger?
In a corporate environment, local messengers generally refer to services whose server components can be deployed in infrastructure controlled by the company. This deployment model is also called on-premise.
With on-premise deployment, the company manages the messenger's server components, data location, and connections to internal systems. If the messenger needs to operate on a network without access to the public internet, a separate isolated-deployment scenario or a LAN (Local Area Network) solution is required.
Regardless of their application, locally deployed (on-premise) messengers offer several fundamental advantages:
- Control over data location, including the physical location of servers;
- Flexible management of integrations with the company's internal systems;
- The ability to establish an isolated environment without internet access when necessary.
When do you need a local messenger?
The messenger must be integrated into internal IT infrastructure
A corporate platform can be connected to user directories, authentication systems, and other internal services. Integration capabilities depend on the particular product, so it is best to verify their scope before deployment.
Data must remain within the company's infrastructure
The IT department gains complete control over the data lifecycle. The company defines its own access, storage, and backup policies based on its IT architecture and information security requirements.
How to choose a locally deployed messenger
Scalability and performance
Each solution has its own requirements for server resources, component count, and deployment architecture. For corporate communications, it matters how the system scales as the number of users and workload increase and whether it supports redundancy and fault-tolerant configurations.
Communication capabilities
A local messenger should cover the main employee communication scenarios: individual and group chats, channels, threads, file sharing, and audio and video calls. If the platform will primarily be used for online meetings, assess its video conferencing capabilities separately: participant limits, screen sharing, meeting recording, guest access, and conference management tools.
For a local solution, it is important to determine which of these functions are available under the selected deployment model. For example, can calls and video conferences run on the company's servers while retaining the necessary functionality?
Ability to operate without internet access
On-premise deployment does not guarantee autonomous operation within a local network. A product may still have external dependencies for notifications, video communication, licensing, updates, and other functions. If a company plans an isolated deployment without internet access, it should separately verify support for this scenario and the features available within it.
Total cost of ownership
In addition to license costs, account for server hardware, electricity, IT staff salaries for support, and update costs. Sometimes a solution with a high initial price proves cheaper in the long term due to lower maintenance costs.
Top 5 locally deployed corporate messengers
This selection includes solutions whose developers state that their server components can be deployed within the customer's infrastructure.
eXpress
eXpress is a Russian communications platform offering individual and group chats, channels, threads, calls, video conferences for 500+ participants, and chatbots. The corporate superapp supports integrations with various internal company services (CRM, electronic document management systems, and others), as well as embedded SmartApps.
The corporate edition supports centralized management of users and access permissions. Data protection measures include encryption in transit and at rest, multifactor authentication, and a role-based access control model. For example, an administrator can restrict file transfers or screen sharing depending on whether a user is inside or outside the corporate network.
A distinctive feature of eXpress is its Federation, which connects corporate servers and public users in a shared network. This allows employees to communicate within their company, with users of other corporate servers, and with users of the public eXpress edition. Direct communication is possible between trusted corporate servers.
For infrastructures requiring complete network isolation, an option to deploy outside the shared Federation is available upon separate request.
MTS Link
MTS Link combines a corporate messenger with services for online meetings, webinars, collaboration, and training. The server edition includes Chats, Meetings, Webinars, Boards, Courses, and Forms.
The platform integrates with Active Directory, LDAP, and SSO, enabling corporate accounts and centralized access management. Documentation for the server edition also provides for integration with DLP systems.
Another MTS Link feature is its video conferencing capability: hardware video conferencing systems can be connected via SIP and combined with software clients.
Compass
Compass is a corporate messenger with chats, threads, file sharing, and audio and video calls. The platform offers video conferences for 1,000+ participants, meeting recording, screen sharing, and external participant access via links.
Companies can use an on-premise edition hosted within their own infrastructure. Compass supports integrations with DLP, SIEM, antivirus tools, LDAP, and SSO. Administrators can manage employee permissions and restrict specific actions involving corporate data.
Compass also offers a separate free plan for small teams of up to 10 people.
VK Teams
VK Teams is a corporate messenger within VK WorkSpace. It can be used separately or alongside other platform services, including corporate email, calendar, and cloud storage. For user management, the platform can be connected to a corporate directory and a single sign-on system. The service also supports integrations with DLP, SIEM, antivirus solutions, and external S3 storage.
The local edition is designed for centralized administration: managing employee accounts and access, and connecting corporate security and data storage systems.
TrueConf
TrueConf is a Russian platform for which local installation is one of the primary deployment scenarios. TrueConf Server is installed on a company's physical or virtual server and supports Windows Server and several Russian Linux distributions. The platform also supports operation within a closed corporate network without internet access.
However, TrueConf is primarily a video conferencing platform rather than a conventional corporate messenger. It is designed for large conferences and supports connecting meeting rooms and video conferencing equipment. Its client applications also include chats, messaging and file sharing, calls, and other communication features.
SaaS vs. on-premise
A cloud messenger (SaaS) does not need to be installed on company servers. The organization subscribes to a ready-made service, and the provider maintains its infrastructure: installing updates and monitoring the operation and availability of server components. This model is easier to launch and maintain without extensive in-house resources.
The local edition (on-premise) is deployed within infrastructure controlled by the company. The company manages server components, corporate data location, and connections between the messenger and internal systems. This requires resources for deployment and ongoing platform maintenance.
Cloud messengers have advantages in terms of rapid launch, no capital expenditure on servers, and simpler updates. However, they are less advantageous in terms of data security. Disadvantages of on-premise solutions include high initial investment and the resources required for deployment. In return, such solutions provide a high level of protection and data control.
Frequently asked questions (FAQ)
What is an on-premise messenger?
It is messaging software installed on a company's physical or virtual servers.
Which is more secure: a cloud or local messenger?
The deployment model alone does not determine the level of security. With on-premise deployment, a company gains more control over server components and data location but assumes responsibility for configuration, updates, redundancy, and infrastructure protection. In SaaS, the service provider handles a substantial portion of these processes.
What are the advantages of FSTEC-certified messengers?
A certificate confirms that the software has undergone verification for compliance with information security requirements. This is critically important for government organizations and companies handling confidential data because it guarantees a verified architecture and protection mechanisms.
Can an on-premise messenger be used without internet access?
It depends on the particular product and configuration. The on-premise model alone does not guarantee this capability. To operate without the public internet, all necessary components must be accessible within the corporate network, and the product must officially support an isolated-environment scenario.
Where is data stored when a messenger is deployed locally?
Server components and corporate data reside in infrastructure controlled by the company. This may include the organization's own servers or infrastructure dedicated to it.