Alianza Acquired MetaSwitch: What Operators Need to Know

When Microsoft bought MetaSwitch for roughly $270 million in 2020, the move looked like a validation of carrier-grade infrastructure. Five years later, MetaSwitch has changed hands again, this time to Alianza, a cloud communications company that also owns CounterPath, the maker of Bria.

For operators running MaX UC, the acquisition raises practical questions about roadmap stability, pricing pressure, and application-layer control. It also changes what operators should consider now.

What happened: three ownership transitions in five years

MetaSwitch's recent history is a study in strategic pivots:

• May 2020: Microsoft acquired MetaSwitch, positioning the deal as part of its 5G and carrier transformation strategy.
• June 2024: Microsoft laid off approximately 1,500 employees across Teams, Azure, and other divisions. MetaSwitch teams were included in the restructuring.
• March 2025: Alianza completed its acquisition of MetaSwitch from Microsoft.

Each transition introduced uncertainty. The latest one adds a new layer of concern for operators evaluating long-term control and leverage.

Alianza now owns both MetaSwitch infrastructure and CounterPath's Bria softphone. Whether operators stay on MaX UC or migrate to Bria, both paths now sit under the same parent company. For some operators, that may raise questions about leverage, pricing predictability, and long-term alignment.

What operators are reporting

The acquisition did not happen in a vacuum. During conversations with operators evaluating alternatives to MaX UC, our sales team has heard recurring concerns in a few specific areas:

• Battery drain: Some Android users report up to 50 percent battery consumption in seven hours.
• Call reliability problems: Frozen incoming calls and audio routing bugs have been documented in production environments.
• Support degradation: Response times have lengthened, and escalation paths have become less clear.
• Price increases: Reports suggest roughly 40 percent price hikes, reminiscent of the pricing pressure Cisco BroadSoft customers experienced after acquisition.

A loose 2029 sunset date has circulated informally, but no binding roadmap has been published. That leaves operators managing subscriber expectations without clarity on how long MaX UC will remain viable.

The real risk: application-layer dependence

The deeper issue is not just ownership churn. It is control.

When your client application is vendor-controlled, you inherit every roadmap decision, pricing change, and support policy shift. You cannot fix battery drain. You cannot patch call reliability bugs. You cannot negotiate from strength when the vendor owns both your current app and the migration path.

Infrastructure decisions can be deferred. Application control cannot.

If MaX UC becomes unsustainable, operators face two difficult options:

1. Migrate to Bria: Stay within the Alianza ecosystem, but lose negotiating leverage and remain dependent on a vendor-controlled client.
2. Rebuild in-house: Take on the operational complexity of maintaining a production softphone, including push notifications, provisioning, cross-platform support, and lifecycle management.

Both paths force a tradeoff between control and capacity.

What a white-label strategy changes

A white-label softphone decouples the application layer from backend infrastructure. That means you can replace MaX UC today without forcing an immediate backend migration decision.

Here is what that looks like in practice:

• Preserve branding: Your app, your name, your app store presence. Subscribers do not experience the change as a vendor swap.
• Maintain user experience: No retraining, no new login flows, no feature regression.
• Keep backend optionality open: Stay on MetaSwitch if it still makes sense. Migrate to another platform when you are ready. The client layer does not dictate the timeline.
• Control your roadmap: Feature requests, release schedules, and support escalations flow through your relationship with a white-label provider, not through a vendor managing competing priorities.

This is not about abandoning MetaSwitch infrastructure overnight. It is about separating the decision to replace a problematic client application from the decision to re-architect your entire backend.

What to do next

If you are running MaX UC and evaluating your options, here is a practical framework:

1. Assess current MaX UC stability: Document battery drain reports, call reliability issues, and support response times. Quantify the operational cost of continuing.
2. Evaluate vendor lock-in risk: Consider what happens if pricing increases again, or if the 2029 sunset becomes formal. How much leverage do you have?
3. Test a white-label alternative: Run a pilot with a subset of users. Measure battery performance, call reliability, and provisioning behavior against MaX UC.
4. Preserve backend flexibility: Choose a client that works with MetaSwitch today and supports other platforms tomorrow. Do not trade one lock-in for another.

The goal is not to react to acquisition news. It is to build a strategy that gives you control over your application layer, regardless of who owns the infrastructure underneath.

Acrobits Cloud Softphone replaces MaX UC without forcing a backend migration. You keep your branding, your subscribers, and your timeline.

Sources

• Microsoft announces definitive agreement to acquire MetaSwitch Networks
• Alianza completes acquisition of MetaSwitch from Microsoft
• Microsoft to quit Affirmed and MetaSwitch in telecom retreat
• Major MetaSwitch layoffs reported