What is an all-in-one messenger?
A single window holding WhatsApp, Teams, Telegram, your mailbox and your calendar, each in its place in a sidebar. The idea is about fifteen years old; what has changed is the reason you need one.
The principle
A messaging aggregator is a desktop application that loads web services into separate views, much as a browser would, but with a sidebar instead of tabs. Each service keeps its place, its icon and its keyboard shortcut. Nothing is reinvented at the protocol level: what you see is each service’s official web interface.
So it is not a messaging client in the strict sense. It does not talk to WhatsApp’s or Teams’ servers: it displays their pages, in a frame more convenient than fifty tabs.
Two problems, and only one is handled well
The first is tab saturation: the applications you keep open all day end up buried, and finding the right one costs a few seconds, fifty times a day. Every product in the category solves this, and a tidy browser gets close.
The second is more interesting, because the browser has no answer for it: several accounts of the same service at once. A browser keeps one session per site. Opening the second WhatsApp Web account signs the first one out, and Microsoft’s official answer for two Teams accounts is to open a different browser.
What an aggregator does not do
- It does not merge your conversations into a single inbox: each service stays where it is, with its own interface.
- It does not work offline any better than the service itself: what the service never supported does not become supported.
- It does not replace a native application where that one does more: features exclusive to the official client stay exclusive.
- It does not make you anonymous: you sign in to your usual accounts, with the same credentials.
The criteria that matter when choosing
| Criterion | Why it matters | How to check it |
|---|---|---|
| Isolated sessions | It is the feature separating an aggregator from a tidy browser | Add the same service twice and check both stay signed in |
| Engine freshness | A lagging engine ends up blocked by services, one at a time | Show the user agent inside a service: the number after “Chrome/” |
| Release cadence | It predicts whether the engine will keep up with the next deprecation | Look at the dates of stable releases on the releases page |
| Native notifications | Without them the app does not replace the tabs it claims to remove | Close the window and check a message still arrives |
| Licence | It determines whether today’s free product can become paid tomorrow | Look for the licence file in the public repository |
Where Nexus sits
Nexus is an aggregator for Windows 10 and 11, free and MIT-licensed. It gives every service an isolated session, sends real Windows notifications, keeps unread badges visible with the window closed, and follows the Electron stable line so the engine does not fall behind.
It does not try to advertise the largest number of built-in services: the catalogue covers the common ones, and any web address can be added as a service in its own right.
Common questions
- How is this different from pinned tabs?
- Pinned tabs solve tidiness, not multi-account: a browser keeps one session per site. They also give you no system notifications once the browser is closed.
- Is it heavier than a browser?
- Each service uses memory much as a tab would, so the order of magnitude is the same. Per-service sleep returns memory to the system for services you are not using.
- Are my credentials safe?
- You sign in on each service’s official pages, inside a local session. Nexus has no server, no user account, and never sees a password or a message.
- Should I uninstall the native apps?
- No. They can coexist, and some keep features the web version lacks. Plenty of people keep the native client for their main service and group the rest.