Enterprise Messenger: One Platform for Your Entire Organization

One-time payment · Lifetime license · Hosted on your own server

Unify every department, branch and remote team with secure, self-hosted messaging, file sharing, and voice and video calls, running on your own server.


Start Free Trial

Trusted by 7,500+ Companies Worldwide

Output Messenger enterprise chat window showing departments, online users, chat rooms and the Obo assistant
Self-hostedYour server, your data
Active Directory/ LDAP sign-in
Voice & videoWindows · Linux · Mac · Web · Mobile

  • Unified Team Communication
  • Self-hosted server deployment
  • Active Directory / LDAP integration
  • Secure messaging and file sharing
  • Voice and video communication
  • Windows, Linux, Mac, Web and Mobile
  • Government
  • Banking & Finance
  • Healthcare
  • Manufacturing
  • IT & Technology
  • Education
  • Defence
  • Retail & Wholesale
Enterprise communication problems

Why Consumer Chat Apps and Public Cloud Tools Fail
at Enterprise Scale

As an organization grows past a few dozen people, informal communication turns into an IT, security and compliance problem. These are the issues we hear most from IT managers, and how an enterprise messenger resolves them.

Departments work in silos

Teams use different apps, so information is scattered and cross-department requests get lost in email.

One platform for every department

Org-wide directory, departments, group chats, chat rooms and announcements give everyone a single place to reach anyone.

Company data lives on someone else’s cloud

Public messengers store conversations and files on third-party servers, outside your policies and your jurisdiction.

Self-hosted on your own server

Messages, files and logs are stored on infrastructure you own, inside your network, under your backup and retention rules.

Separate logins and manual user management

Every new hire and leaver means another account to create or remove, and another password to forget.

Active Directory / LDAP integration

Users sign in with their existing directory credentials and are imported from your directory. No duplicate identities.

Uncontrolled file sharing and shadow IT

Staff send business documents through personal chat and file-sharing accounts that IT cannot see or audit.

Secure messaging and file sharing

Encrypted transfers, Output Drive for shared files, admin-defined communication restrictions and central logs keep sharing inside policy.

Too many tools for chat, calls and tasks

Chat in one app, video in another, tasks in a third. Licensing costs and context-switching add up.

Voice, video and collaboration built in

Voice and video calls, conferencing, desktop sharing, tasks, calendar, polls and internal mail ship in the same client.

Recurring per-user subscriptions

SaaS messaging fees grow every year with headcount, and you lose access when you stop paying.

One-time lifetime license

Pay once per user for a perpetual license, or choose an annual plan. Predictable cost, and the software keeps working.

Deployment architecture

How Output Messenger Fits Into Your Infrastructure

A single server inside your network. Office users connect over the LAN, remote users connect through your VPN or a firewall-published SSL endpoint, and your directory and database stay exactly where they are today.

Output Messenger enterprise deployment architecture Office users on Windows, Mac, Linux and web browsers connect over the internal network to the Output Messenger server. The server integrates with Active Directory or LDAP and a MySQL or Microsoft SQL Server database. Remote and mobile users connect through a VPN or a firewall-published SSL port to the same server. YOUR INTERNAL NETWORK (LAN / WAN) ① USERS Windows desktopsOutput Messenger client Mac & LinuxOutput Messenger client Web browserBrowser version (HTTPS) Branch officesSite-to-site VPN / WAN Internal switch TCP 14121–14124 ② OUTPUT MESSENGER SERVER Output Messenger Server Chat · File transfer · VoIP Web client · API · Admin panel Central logs · Policies SSL / TLS encryption ③ YOUR EXISTING SYSTEMS Active Directory / LDAP directory user sign-in & import Database MySQL / MS SQL Server messages & metadata Backups, antivirus and monitoring follow your existing IT policies. Data never leaves your network unless you publish it. FIREWALL Publish only the required ports VPN or SSL port-forward REMOTE ACCESS ④ REMOTE USERS Work from homeDesktop & web Mobile staffAndroid & iOS apps Field & travelingAny internet link Remote branchesVPN tunnel Push notifications Mobile alerts when the app is in the background (outbound from server)

1Users → server

Desktop, web and branch-office users connect to one Output Messenger server across your LAN or WAN. No per-user cloud accounts.

2Server → your systems

The server authenticates against Active Directory / LDAP and stores data in your MySQL or Microsoft SQL Server database. All traffic is SSL-encrypted.

3Remote access

Remote and mobile users reach the same server through your VPN or a firewall-published SSL port, so the experience is identical on and off the network.

Active Directory & LDAP

Enterprise Messenger with Active Directory Integration

Staff sign in with their domain accounts. IT imports users from the directory. No duplicate passwords, no manual setup.

  • One login. Employees use their Active Directory username and password.
  • Quick user import. Bring in users from Active Directory or any LDAP directory.
  • Single Sign-On. Fewer password prompts and faster adoption.
  • Departments & permissions. Organise teams and set access from one admin panel.
  • Your policies stay in force. Password rules remain under your directory.

See the Active Directory integration guide →

Who manages what
Item Managed by
Identity & passwords Active Directory / LDAP
User accounts Directory import
Chats & files Your Output Messenger server
Departments & permissions Output Messenger admin panel
Network & firewall Your IT team

Security & administration

Secure Enterprise Messaging with Full Admin Control

Keep company chat, files and calls on your own server, with the controls IT teams expect.

Encrypted messaging

SSL / TLS encryption for chat, with your own certificate.

Two-factor login

Add SMTP-based two-factor authentication to every account.

Role-based admin

Admin and manager roles with department permissions.

Communication controls

Restrict who can message whom, by user or department.

Central chat logs

Review chat logs, status history and work hours from one place.

Off-the-record chat

Confidential OTR messages are never logged.

LAN chat continuity

Teams on the same network keep chatting if the server is down.

Data ownership

On-premise data supports your residency and retention policies.

Secure remote access

Connect remote and mobile staff over your VPN or an SSL-secured connection.

Deployment requirements

Simple On-Premise Deployment

Install on your own server. Give every user a desktop, web or mobile app.

Server requirements
Operating system Windows Server or Windows 11. Linux and NAS hosting also available.
Hardware 1 GHz CPU · 1 GB RAM · 2 GB disk, plus storage for files
Software .NET Framework 4.8 (auto-installed)
Database MySQL or Microsoft SQL Server
Directory Active Directory or LDAP (optional)
Network ports TCP 14121–14123 and 14125 · TCP/UDP 14124 (voice & video)

Supported platforms
Platform Client
Windows Desktop app
Linux Desktop app (incl. Ubuntu)
Mac Desktop app
Web Browser version (TCP 14123)
Android Google Play app
iOS App Store app

Minimum specs. Size your server for user count and file sharing. See the server install guide.

For remote access, use a VPN or publish only the ports you need. See the remote-access guide.

See Output Messenger Running on Your Network Design

Book a walkthrough with our team and see how Output Messenger fits your servers, Active Directory and remote-access setup.

Request an Enterprise Demo

Frequently asked questions

Enterprise Messenger FAQ

What is an enterprise messenger?

An enterprise messenger is a business chat platform that gives every department one place for instant messaging, file sharing and voice and video calls, with central administration, directory integration and security controls that consumer chat apps do not provide.

Can Output Messenger be installed on our own server?

Yes. Output Messenger is self-hosted. You install the server inside your own network, so messages, files and user data stay on infrastructure you control.

Does Output Messenger integrate with Active Directory?

Yes. Users can sign in with their Active Directory accounts, and users can be imported from a directory that supports LDAP, so you do not maintain a separate set of passwords.

Which platforms does Output Messenger support?

Desktop clients for Windows, Linux and Mac, a browser-based web client, and mobile apps for Android and iOS.

Can remote and mobile employees connect when they are off the office network?

Yes. Remote users can connect over a VPN or through an SSL-secured internet connection that you publish through your firewall, so field and work-from-home staff use the same platform as office staff.

Is Output Messenger secure for enterprise use?

Yes. You host the server on your own network, so company data stays under your control. Chat is protected with SSL / TLS encryption, and you can install your own certificate. You can also add two-factor authentication, restrict who can message whom, and review chat logs centrally. Off-the-record messages are never logged.

Can Output Messenger integrate with our existing business systems?

Yes. Along with Active Directory / LDAP, Output Messenger has a Web API for managing users, departments and chat rooms, and for sending chat messages and notifications from your own applications. It also supports integrations such as GitHub and Jitsi Meet, so you can connect it to the tools your teams already use.