Mattermost at CERN: Scaling Chat to 22,000 Users

CERN deployed Mattermost in 2015 to consolidate fragmented chat across 22,000 researchers and staff. Today the platform runs 1,500 teams, 26,000 channels, and 58 million posts. Unlike Slack or Teams, CERN operates it entirely on-premises. This guide explains CERN's setup, its operational costs, and whether self-hosting or managed alternatives fit your organization.

What Is Mattermost at CERN?

Mattermost is an open-source team collaboration platform that CERN has run on-premises since 2015. CERN's instance serves 22,000 registered users (with 10,000 monthly active), organized into 1,500 teams, 26,000 channels, and hosting 58 million posts. Unlike Slack or Microsoft Teams, CERN operates the entire infrastructure itself: no cloud provider, no vendor hosting, complete control.

Before Mattermost, CERN's researchers and engineers scattered their communication across email, IRC, Hipchat, and specialized tools. Knowledge fragmented. Teams context-switched between systems to stay aligned. CERN needed a unified collaboration platform that met two hard constraints: data must stay in Switzerland, and the platform must be open-source so CERN's security team could audit it before deploying 22,000 credentials on it.

Slack was immediately ruled out: cloud-only, US-based, and expensive. Microsoft Teams required Azure integration and raised data-residency concerns. Mattermost offered an alternative: open-source (39,000 GitHub stars, 23,230 commits), deployable on-premises, and integrable with LDAP for seamless authentication. CERN's IT team could audit the code, run it on CERN infrastructure, customize it, and own the data permanently.

Mattermost Inc. (founded by Ian Tien) maintains and improves the open-source project, but has no control over CERN's instance. CERN can run any version, patch it when it wants, and customize it freely.

Why CERN Chose Mattermost

CERN's vendor evaluation came down to four requirements: (1) On-premises deployment, because data residency is mandatory. (2) Open-source code, because CERN must audit security and have full transparency. (3) No per-user licensing fees, because scaling to 22,000 users with cloud tools is prohibitively expensive. (4) Native SSO integration, because users should not manage separate passwords.

Slack failed all four: cloud-only, proprietary, per-user fees, and clunky SSO. Microsoft Teams requires Azure and Microsoft infrastructure, violating data-residency requirements. Rocket.Chat offered on-premises and open-source but lacked CERN's scale and integrations.

Mattermost met every requirement. CERN's choice reflected institutional philosophy: scientific transparency, control, and openness.

CERN's Mattermost at Scale

CERN runs Mattermost on OpenShift (Red Hat's Kubernetes distribution) with a PostgreSQL cluster, network-attached storage, and load balancers. User authentication is federated through CERN's LDAP directory: employees log in once and automatically access Mattermost based on their departmental role.

The platform handles substantial traffic: 22,000 registered users, 10,000 monthly active (roughly 45% adoption, typical for enterprise), 1,500 teams, 26,000 channels, and 58 million accumulated posts. That is roughly 17 channels per team and 9 posts per user over a decade.

Teams organize by department, experiment, or project. The LHCb experiment might have a dedicated team with 200+ members and 40 channels (one per sub-group: trigger, offline computing, physics analysis). Channels range from formal (#announcements, #official-decisions) to informal (#coffee, #off-topic).

New employees automatically join the #welcome team, which hosts channels for onboarding, housing, benefits, transport, and visa support. Moderators in #help respond to questions. This structure drives rapid onboarding: new CERN staff are productive within days, not weeks.

100+ Integrations and Workflows

CERN has integrated over 100 tools into Mattermost, including Jira, GitLab, GitHub, and ServiceNow. CERN engineers see build notifications, merge requests, and Jira updates in channels without leaving chat. ServiceNow tickets can be created from Mattermost. Custom webhooks post infrastructure alerts and monitoring data to #ops and #incidents in real time.

These integrations matter because they eliminate tool-switching. On-call engineers check one platform (Mattermost) instead of five. A researcher needs to know her team's latest build status without opening GitLab. Integrations make that happen. CERN's 100+ integrations are not nice-to-have; they are the reason people open Mattermost daily.

Deploying Mattermost at Enterprise Scale

If you run a 10,000-20,000-user organization, here is what you need:

Infrastructure: Kubernetes cluster (CERN uses OpenShift), high-availability PostgreSQL (3+ replicas), object storage (S3-compatible for files), load balancer.

Sizing (typical for 20K+ users): 4-6 Mattermost application servers, 3 PostgreSQL replicas, 1-5 TB storage (depends on file retention policy), 10-50 Mbps sustained bandwidth.

Operations: Monitoring (logs, database performance, infrastructure health), daily backups of PostgreSQL and storage, monthly security patches from Mattermost Inc., LDAP sync scripts to auto-add and remove users.

Timeline: CERN's rollout took 3-6 months for infrastructure, integrations, SSO testing, and staged onboarding. Expect similar timelines at comparable scale.

Self-Hosted vs. Managed Hosting: CERN's Trade-Offs

CERN self-hosts and gains full control: data residency in Switzerland, unlimited customization, no vendor lock-in, and code audits. But it pays the price.

CERN's costs: Infrastructure for 4-6 application servers and database replicas, 1.5-2 FTE operations staff, monthly security patches, backup systems, and disaster recovery infrastructure. For organizations at CERN's scale (22,000 users), this represents a substantial annual investment.

Managed alternative: Many organizations choose managed Mattermost hosting to eliminate infrastructure complexity, patching burden, and 24/7 operations staffing. You get professional support, automated backups, security patching, and monitoring.

For CERN, self-hosting makes sense: per-user pricing from cloud platforms would be expensive at 22,000 users, data residency is mandatory, and CERN has the engineering staff to operate it. For smaller organizations (under 500 users), managed Mattermost hosting often costs less than hiring a full-time infrastructure operator.

Getting Started with CERN's Mattermost

If you work at CERN and need to join Mattermost:

1. Navigate to https://mattermost.web.cern.ch
2. Log in using your CERN username and password (same as for email and CERN GitLab)
3. LDAP automatically syncs your roles and group memberships, so you will see teams and channels relevant to your position
4. Browse the team directory or ask colleagues for team/channel invitations
5. Read the code of conduct in the #welcome team (required before participating in most channels)

For help: The official CERN Mattermost documentation is at https://mattermost.docs.cern.ch, with a FAQ section at https://mattermost.docs.cern.ch/faq/. You can also open support tickets through CERN ServiceNow (search "Mattermost" and submit a request) or ask in the #help channel for community help (moderated, typically responds same day). CERN maintains an active #newcomers team where new employees introduce themselves. The #general channel broadcasts institutional announcements. Department-specific channels allow teams to organize discussions by project or experiment.

Deploying Mattermost Elsewhere: Lessons from CERN

CERN's 11-year deployment (2015-2026) teaches organizations evaluating Mattermost three critical lessons.

Lesson 1: SSO is non-negotiable for adoption. CERN's success stems from frictionless authentication: users log in once via LDAP and automatically access Mattermost. If users must create and remember a separate Mattermost password, adoption suffers significantly. Before deploying Mattermost, ensure LDAP, Okta, Azure AD, or SAML integration is built and tested. Avoid any platform requiring manual password creation for 10,000+ users.

Lesson 2: Integrations transform Mattermost from chat to command center. CERN's 100+ integrations (Jira, GitLab, GitHub, ServiceNow, monitoring, alerting) are the reason people open Mattermost daily. Without integrations, Mattermost is just another chat app. With integrations, it becomes a unified nerve center for incident response, deployments, and team coordination. Budget time for integration architecture early: define which systems matter most, build those integrations first, then expand.

Lesson 3: Self-hosting is a 24/7 operational commitment. CERN maintains 1.5-2 FTE dedicated to Mattermost infrastructure. They monitor database performance, test and deploy monthly security patches, manage backups and disaster recovery, and troubleshoot production incidents. If your organization lacks this capacity or does not want to hire for it, managed hosting eliminates the burden.

Frequently Asked Questions

What is the URL of the CERN Mattermost server?

The CERN Mattermost instance is at https://mattermost.web.cern.ch. Access requires CERN credentials (username and password from your CERN account). CERN employees, visiting researchers, and contracted staff with CERN IDs can log in. External collaborators can contact their CERN sponsor for access.

What company owns Mattermost?

Mattermost Inc., founded by CEO and Co-Founder Ian Tien, owns and develops Mattermost. The company is based in Palo Alto, California. The Mattermost platform is open-source (39,000+ GitHub stars), and Mattermost Inc. monetizes through enterprise licensing, managed hosting, and professional services. CERN runs the open-source version with no commercial relationship to Mattermost Inc.

Is Mattermost free if self-hosted?

The open-source Mattermost core is free. Self-hosting costs arise from infrastructure (servers, storage, databases), operations (staff), and network. Enterprise features (advanced permissions, auditing, advanced analytics, SAML provisioning) require commercial licensing from Mattermost Inc. or community alternatives. CERN uses the open-source edition.

What is Mattermost used for at CERN?

CERN uses Mattermost for team chat, cross-department collaboration, research coordination, incident response, onboarding, and integrations with development tools. The platform acts as CERN's unified communication layer: when a CI/CD pipeline finishes, when a Jira ticket is updated, or when an infrastructure alert fires, the relevant team learns about it in Mattermost first.

Who are Mattermost's main competitors?

Slack dominates cloud-based team chat and leads in SMB and mid-market segments. Microsoft Teams leads in enterprises with existing Microsoft licensing. Rocket.Chat, Matrix (distributed protocol), Zulip, and Jitsi compete in the open-source space. For on-premises deployments, Mattermost and Rocket.Chat are the top choices.

Why did CERN choose Mattermost over Slack or Teams?

CERN required on-premises deployment (non-negotiable data residency in Switzerland), open-source code (for security audits and customization), no per-user licensing (cost-prohibitive at 22,000 users), and native SSO/LDAP (so users do not manage separate passwords). Slack failed on data residency and cost. Teams required Azure and Microsoft integration. Mattermost met all criteria.

Is Mattermost compliant with data privacy regulations?

Yes. CERN, an international research organization, operates under strict data governance. Because Mattermost runs on-premises and CERN controls all infrastructure, CERN can ensure full compliance with data residency laws, GDPR (for EU employees), and CERN's institutional policies. Cloud-based platforms (Slack, Teams) cannot offer this level of control.

The Bottom Line

CERN's Mattermost deployment demonstrates that open-source collaboration platforms scale to 22,000 users, 1,500 teams, and 58 million posts. CERN achieved this by running Mattermost on-premises, integrating deeply with LDAP and 100+ third-party tools, and staffing a dedicated operations team.

Scaling Mattermost carries real costs: infrastructure, operations staff, and monthly security patches. For organizations with 10,000+ users and mandatory data residency, self-hosting makes sense. For smaller teams (500-5,000 users) or those without strict data-residency requirements, managed hosting eliminates infrastructure complexity.

Whether you choose self-hosting or managed Mattermost, CERN's lessons apply: prioritize SSO, build integrations early, and plan for operations. Explore managed Mattermost hosting options like Opsily that scale to enterprise reliability without the 24/7 ops commitment.