Channels and threads
Departments, projects and incidents — in separate channels, with searchable history.
Collaboration 07.5 — Chat
A Slack alternative where the conversation stays on your server. Channels, direct messages, files and calls — in one space.
Mattermost / capabilities
Channel structure, mobile apps, LDAP/SSO and integrations — set up so the team actually uses it.
Departments, projects and incidents — in separate channels, with searchable history.
Voice and video calls, screen sharing — from the browser or the app.
iOS and Android — with push notifications, so a channel never slips away.
One account for every service — adding a new employee to one group makes them appear everywhere.
Webhooks, bots and CI/CD notifications — the channel becomes part of the system.
Conversations stay with you — for audits, legal requests or simply history.
process
Which channels the team needs and what stays private — too many channels create noise.
Mattermost via Docker, PostgreSQL, HTTPS and backups.
Importing history from Slack or Telegram where possible.
Short rules: where we write, how we search and when we call — the team adapts quickly.
cases
Channel structure, part of the history and mobile apps — the team moved in one day.
Uptime Kuma alerts straight into a channel — the incident is resolved inside the chat.
Integration
Mattermost becomes most useful when the systems speak inside it.
faq
Text history and files migrate partially — depending on the Slack export format. I assess it beforehand.
For 20–50 users, 2–4 vCPU and 4–8 GB RAM is enough. Files can live on separate storage.
All directions
I will prepare the channel structure and show how it works from mobile.
Let’s talkContact
Contact me by phone or WhatsApp. Critical incidents are covered 24/7; other requests are handled within the agreed support schedule.
24/7 on critical incidents — Response mode
If I miss your call, I will get back to you.