In UCaaS, the question isn't which solution, it's who reads your communications
A UCaaS roundup compares features. In the field, what decides is size, cost, and above all what the platform lets itself do with your data. RingCentral asks for access to your recordings and your private messages. This client moved to Wazo.
A UCaaS roundup ranks platforms. It compares features, lines up logos, names winners. In 2026, that's no longer the right question.
The client who calls me doesn't need to be told which UCaaS is best. They need their telephony organized around the giants, Microsoft first, and placed where it makes sense for their size, their budget, and their data. You no longer choose a solution. You compose with an ecosystem that's already there.
Three things actually decide. Size. Cost. And what you allow to be done with the data. The last one is the one no roundup writes down.
| What decides | What I deploy | Why |
|---|---|---|
| Secrecy to protect, sensitive data | On-prem: Wazo, 3CX, Yeastar | The data stays with the client, in the EU, beyond Cloud Act reach |
| Cloud features, acceptable data terms | RingCentral or Zoom, from SMB to enterprise | The platform follows the need and the budget, at any size |
| Already all-in on Microsoft | I integrate with Teams | I organize around the giant, I don't replace it |
The roundup asks the wrong question
A roundup names a universal winner. There isn't one anymore. Microsoft took the center of gravity. The client who already has M365 already has Teams. The question isn't "which UCaaS," it's "how do I organize the rest around that."
On-prem isn't dead for all that. It's a minority, and it will stay a minority for years to come. But minority doesn't mean finished. When it's a requirement, it doesn't sit beside the ecosystem as a rival choice. It plugs in.
The job is no longer to arbitrate between vendors. It's to place each client on the platform that fits their reality, and to hook the rest onto the giants that are already there.
The real criterion is what you allow to be done with the data
One client, a real confidentiality constraint. I look at RingCentral. By default, the vendor asks for total, systematic access. The recordings. The private messages. Not access you enable when needed. Access by default.
No one signs that when there's a secret to protect. This client moved to a Wazo. Self-hosted. The data stays on their own infrastructure, in the EU. No third party reads it. They control the access.
It's not a question of features. RingCentral has more. It's a question of who is allowed to read. And a US vendor's answer doesn't stop at its commercial terms. There's the Cloud Act. A US platform can be compelled to hand the data to a US authority, wherever it's hosted. Keeping the data in the EU, on a stack you host yourself, means stepping out of that reach.
There's AI too. Every vendor pushes its module. Trained on what? On your communications, if the terms allow it. A call recording and a private message aren't data like any other. They're secrets. I read the terms before I read the datasheet.
On-prem isn't dead, it's a minority
I don't sell on-prem as a step backward. It won't become the majority again. But it's the answer when the data is a requirement, not a preference.
A Wazo, a 3CX, a Yeastar do the job, from SMB to multi-site. Control is total, the data stays in the EU. It's not a matter of size. RingCentral and Zoom can serve a small business too. What tips toward on-prem isn't the number of users, it's the secret to keep.
And when the client is already on Microsoft, on-prem doesn't stand against Teams. It integrates with it. You place the stack where the user already works, like an application in their environment, not a silo off to the side.
What this changes for the integrator
The job has shifted. Before, the value was knowing the best product and reselling it. Today, the best product, the client finds on their own. What they don't find on their own is where to place their telephony and how to hook it onto the ecosystem they already have.
Two reflexes come out of this.
You don't compare features, you read terms. A roundup's ranking says what a platform does. The terms say what it lets itself do with your data. The two don't tell the same story, and it's the second that binds the client.
You don't set a solution down next to Microsoft, you organize around it. The giant is already there. The job isn't to compete with it. It's to compose with it, to place each piece in the right spot, and to keep control of what matters to the client.
I don't sell a UCaaS. I place a platform and organize it around the giants. The integrator still selling "the best UCaaS" is answering a question the client no longer asks.
A UCaaS platform choice stuck on the data question, an on-prem stack to integrate into a Microsoft environment, a migration that has to stay in the EU? Get in touch.
Field note by qaryon
Nicolas Marxer
UC/VoIP solution architect focused on operator, integrator, and B2B deployments.
Need a field view on your voice architecture?
Audit, scoping, or deployment: qaryon works directly on SIP, SBC, UCaaS, and automation topics.
Discuss a telecom projectRelated reading
In SIP, what's negotiated isn't what's supported
Three trunks that refused to place a call between two vendors. Each time, a peer that signals one thing and does another. The SBC absorbs it, the trace settles it.
qaryon is officially launched
qaryon is incorporated, insured, in production, and already billing B2B telecom and pragmatic AI consulting work.