Skip to content

535 040 361511 275 531

Book an IT review

Team chat and video meetings, on your company's server.

Team conversations in threads instead of private messengers, video meetings without accounts at an outside provider, and an online training room. We also say when a new chat app would only add one more window.

What you get after the review

Company conversations take place in private apps.

In many companies, the team talks in a messenger everyone has on their private phone. It works until an employee leaves with the history of arrangements with a customer, or until someone sends personal data to a group that includes people from outside the company.

A company chat solves this only if the team actually moves to it. That is why deployment starts with agreeing which conversations happen there, who creates channels and how long you keep the history, not with installation.

Video meetings are a separate matter. Their quality depends more on the server's connection and the number of participants than on the application itself. We check hardware requirements and bandwidth before deployment, so that the first board meeting is not a load test.

What we look at when choosing.

  1. 1

    Notifications on the phone

    With some vendors, the free edition limits push notifications or the number of users who receive them. We show this cost before the decision, because without notifications a chat app will not replace the phone.

  2. 2

    Number of users and history

    We check whether the free edition has a limit on accounts or on the messages the team can see in the history. A limit discovered after six months ends in a rushed migration.

  3. 3

    Integrations with other systems

    A chat app that receives notifications from the helpdesk, monitoring and sales replaces several mailboxes. We agree what should go there.

  4. 4

    Meetings or training

    A lighter video tool is enough for team conversations. A training room with a whiteboard and breakout rooms has much higher server requirements.

  5. 5

    The server's connection

    Video sends a lot of data in both directions. A server in the office with an asymmetric connection is often a worse choice than a server in a data centre.

Applications we deploy.

Every description of features, licences and limits comes from the vendor's materials, read on 2 October 2026. For each application we add our assessment of when it fits. We make the final choice after talking about your case.

Full application catalogue

Zulip

A good starting point for most companies

A team chat app in which conversations are organised into threads.

Licence
Apache 2.0
Language
interface in Polish
  • On a self-hosted server, free mobile push notifications cover up to 10 users. A larger team needs a paid plan from the vendor or, if it qualifies, the Community plan.

Our assessment: All the code is open, and the only significant cost for a larger team is the mobile notification plan, known before deployment.

Vendor website (zulip.com)

Jitsi Meet

A good starting point for most companies

Video conferencing in the browser, which can be run on your own server.

Licence
Apache 2.0
Language
interface in Polish
  • The documentation usually recommends 8 GB of RAM. Requirements grow with the number of participants, and recording needs separate resources.

Our assessment: Internal meetings without accounts at an outside provider. We check the server's bandwidth before going live.

Vendor website (jitsi.org)

BigBlueButton

We deploy it when it fits the case

A virtual classroom for online training with a whiteboard, presentation and breakout rooms.

Licence
LGPLv3
Language
interface in Polish
  • The server requires, among other things, 8 cores and 16 GB of RAM.

Our assessment: It makes sense for companies that run training regularly. A lighter tool is enough for ordinary meetings.

Vendor website (bigbluebutton.org)

When not to deploy another chat app.

If the company already has a chat app in its office suite and the team uses it, a new system usually adds yet another place with messages. In that situation we help tidy up what is there and do not propose a deployment.

Your own chat app makes sense when there's a specific reason: data must not go to an outside provider, the team works on a network without internet access, or the chat should collect notifications from systems running on your servers.

Microsoft 365 and Google Workspace implementations

How we deploy, step by step.

  1. 1

    Communication rules

    Channels, who creates channels, how long the history is kept and rules for guests from outside the company.

  2. 2

    A server with a suitable connection

    Choosing a server for the number of users and video. For meetings, we check bandwidth before installation.

  3. 3

    Installation and sign-in

    A separate environment, HTTPS, user accounts and, if the edition allows it, shared sign-in with other applications.

  4. 4

    Phone apps and notifications

    Configuring notifications within what the chosen edition provides, and testing on phones with different systems.

  5. 5

    Backup, updates, support

    Backup of the database and files outside the server, updates in a maintenance window and support for the team in the first weeks.

The server, domain and vendor licences are in your company's name. We record response time and fix time separately in the contract, and state the restore time after a test. Service terms

Questions before you decide.

Will team chat replace internal e-mail?

Largely yes, if the team agrees which matters it handles in channels. E-mail stays for contact with customers and formal correspondence.

Can customers join a video meeting?

Yes, through a link in the browser. We set who can create meetings and whether guests wait to be admitted by the host.

How many users will the server handle?

That depends on the application, the number of simultaneous meetings and the connection. The vendor's requirements are a starting point, and we check the real capacity with a test before acceptance.

Why are some well-known chat apps missing here?

Some vendors require permission to use the product name when describing paid services. Until we have it, we do not name them on the website. In a conversation we can discuss any tool you are considering.

Other needs

Free · 60 minutes online · no obligation

First, a conversation about the process, then the tool.

  1. You tell us about the processOnline, by video call. What takes up time today, which systems hold the data and what you want to achieve.
  2. We tell you whether it's worth itSometimes a change to a spreadsheet or a process is enough. If so, we'll say that instead of proposing a project.
  3. You get the next stepBy email after the meeting: what to map, what data to prepare and what the price depends on.

office@nexait.plMessage us on WhatsApp

We don't use a contact form, but we answer the phone and reply to emails and WhatsApp messages during working hours.