The MaX UC client portfolio — desktop, mobile, web, Microsoft Teams — is what service providers built on top of MetaSphere for the last decade. That decade is ending. We took a to look at what MaX UC publicly enables service providers to build today, side by side versus The NetSapiens Platform. Here’s the honest read for service providers deciding where to migrate.
The Metaswitch platform roadmap, architecture, and developer experience isn’t where modern UCaaS is heading. MaX UC publishes no public developer portal. Its meeting features are powered by Zoom. Its IM and presence run over XMPP through the Accession Messaging Service. Its backend APIs sit behind license gates and partner agreements. Add to that: Alianza’s post-acquisition roadmap is steering service providers off MaX UC toward Alianza One.1 NetSapiens on the other hand publishes 80+ API categories at docs.ns-api.com for service providers building AI voice agents, conversation intelligence, vertical bundles, and embedded calling products.
NetSapiens API categories publicly documented at docs.ns-api.com
Public MaX UC developer portal. No equivalent to docs.ns-api.com or developer.alianza.com
MaX UC meetings are powered by Zoom — not built natively into the platform
MaX UC IM & presence delivered via XMPP through the Accession Messaging Service
Hundreds of service providers deployed MaX UC over the last decade. Understanding the stack is the first step in understanding the migration decision.
MaX UC is Metaswitch’s unified-communications client portfolio. It’s what end users see and use: the softphone app on the desktop, the mobile app on iOS and Android, the web client in CommPortal, and the plug-in inside Microsoft Teams. The clients deliver voice, video, IM, presence, voicemail, and meetings to subscribers.
MaX UC runs on top of the MetaSphere stack — specifically the Call Feature Server (CFS) and the Enhanced Application Server (EAS). Service providers running MaX UC are running the full Metaswitch stack underneath: MetaSphere for call control and applications, CommPortal as the subscriber self-service web layer, the Accession Messaging Service for IM/presence over XMPP, and Zoom integration for meetings.
Since the acquisition, the direction of travel1 is one way: off Metaswitch, onto Alianza One. The only thing service providers still control is whether they choose to stick around or move to the next generation UCaaS platforms that is modern, open and developer-led.
NetSapiens publishes a developer platform. Metaswitch publishes a UC client suite and product datasheets.
80+ API categories for building on top of UCaaS
A legacy UCaaS stack — closed, partner-gated, no public developer portal
Backend APIs (CommPortal JSON, MetaSphere EAS Web Services, MetaView Web Services, Network-Wide Web Services) exist but are not publicly documented in a developer portal. Access requires a platform license and partner relationship. Positioned for OSS/BSS integration, not service-provider product development.
Metaswitch MaX UC isn’t a different category of product. It’s an older generation built before AI, before programmable UCaaS. The migration from MaX UC to NetSapiens isn’t a like for like upgrade. It’s a generational shift.
Twelve capabilities a service provider needs to build modern UCaaS innovation products.
| Capability | ✓ NetSapiens | ✘ Metaswitch MaX UC |
|---|---|---|
| Real-time call control - Intercept, redirect, transfer, hold programmatically | ✓ First-class public API category. Foundation for AI voice agents and call coaching. | ✘ Not exposed as a public developer API. Call control happens inside MaX UC clients via end-user interaction. |
| Webhooks & event subscriptions - Real-time event streaming | ✓ Published as a primary integration mechanism for event-driven architectures. | ✘ No public webhooks documented. Integration is client-side or via license-gated backend APIs. |
| Transcription & sentiment - AI-ready voice intelligence | ✓ Native API category. Direct integration hooks for AI products. | ✘ Voicemail-only speech-to-text via optional cloud subscription. No real-time transcription API for developers. |
| Media manipulation - TTS, greetings, voicemail, MoH | ✓ Comprehensive media APIs for caller-experience customization. | ✘ Not exposed as a public developer API. Media handling lives inside MetaSphere EAS / CFS, license-gated. |
| Mobile SDK - Foundation for branded mobile apps | ✓ SNAPmobile SDK published — full white-label mobile app foundation. | ✘ MaX UC Mobile is brandable (logo, colors, app-store listing), but there is no SDK to build a different mobile app. |
| Low-code UI builder - Service-provider portal customization | ✓ SNAPbuilder published for branded portals and self-service apps. | ✘ CommPortal is brandable but not a developer-extensible UI platform. No low-code equivalent. |
| Native video & meetings - Built into the platform | ✓ Conference and Meeting APIs documented as platform-native. | ✘ Meetings powered by Zoom (per official Metaswitch datasheet). Service providers are reselling Zoom-backed meetings. |
| Programmable IM & messaging - SMS / chat APIs | ✓ Messages, SMS, and SMS Number APIs documented for developer use. | ✘ IM runs over XMPP via Accession Messaging Service. End-user IM works; developer-facing programmable IM is not publicly documented. |
| Contact center / ACD - Queues, agents, real-time stats APIs | ✓ Call Center / CCaaS APIs documented for developer integration. | ✘ Integrated ACD exists as a MaX UC feature. Separate "Cloud Contact Center" product exists. Developer-facing APIs not publicly documented. |
| Recordings & audit logs - Compliance, QA, surveillance | ✓ Recordings, Audit Log, and Access Log APIs documented. | ✘ Call recording exists as a MaX UC end-user feature. Developer access to recordings via backend APIs is license-gated. |
| Public developer portal - Interactive, no certification required | ✓ Interactive ReadMe-style portal at docs.ns-api.com. OpenAPI schema, try-it-now, downloadable JSON schemas. No certification gate. | ✘ No public developer portal. Documentation at docs.metaswitch.com is end-user tutorials. Backend API access requires platform license + partner status. |
| Client branding - End-user app appearance customization | ✓ Full white-label customization across web, mobile, AI receptionist, and admin surfaces. | ✘ MaX UC clients are brandable — logo, colors, app store presence. This is one of the strongest aspects of MaX UC. |
Here’s how to think about which one fits yours.
MaX UC mature clients work today. The branding works. The Teams integration is solid. None of that is in dispute. The dispute is about how soon will they be forced to move to Alianza’s own solution, and the answers aren’t ambiguous:
The question isn’t whether to migrate. It’s when. Service providers that move while their MaX UC investment is still recouping switching costs come out ahead. Service providers that wait until Alianza forces the conversation come out behind.
If You want unlimited API innovation. 80+ documented API categories, full OpenAPI schema, no certification gate, no permission required to ship.
That’s NetSapiens. Every capability above is documented and publicly accessible at docs.ns-api.com. No certification gate. No PDF downloads. No “talk to your account rep” before you can prototype.
Yes. NetSapiens has migrated hundreds of service providers off the Metaswitch stack, and is among the most common destinations for operators evaluating alternatives. NetSapiens is purpose-built for the same audience MaX UC serves — service providers delivering UCaaS to business and residential subscribers — with a modern, open, developer-led architecture rather than a closed legacy stack. The migration path is well-trodden: voice continuity, subscriber data import, number porting, and feature parity are standard practice rather than greenfield work.
Metaswitch MaX UC is a closed UCaaS stack — MetaSphere CFS at the core, EAS for applications, CommPortal for self-service, MaX UC clients on top, with backend APIs gated behind platform license and partner status. The architecture was designed in an era when service providers didn’t expect to build their own software. NetSapiens is the opposite posture: an open developer platform with 80+ documented API categories at docs.ns-api.com, OpenAPI schema published, no certification gate to access. Service providers build directly on the platform, not around it.
Metaswitch MaX UC has no documented public APIs for live call control, real-time transcription, sentiment analysis, or media manipulation — the surfaces required to build AI voice agents or conversation intelligence products. Voicemail speech-to-text exists as an optional cloud subscription, but that’s not a developer surface. NetSapiens documents all of these as first-class API categories: live call control for AI agent orchestration, webhooks for real-time event streaming, transcription and sentiment APIs for conversation intelligence, and media APIs for programmable voice experiences. AI-driven UCaaS innovation requires the platform to expose these capabilities. Today, only one of the two does.
NetSapiens publishes an interactive developer portal at docs.ns-api.com — full OpenAPI schema, searchable reference, downloadable JSON schemas, no certification required to start building. A developer can land on the site, explore the API surface, and prototype against it the same day. Metaswitch publishes end-user documentation at docs.metaswitch.com, but no equivalent developer portal. The backend APIs (CommPortal JSON, MetaSphere EAS Web Services, MetaView Web Services) require platform license and partner status to access, and are positioned for OSS/BSS integration partners — billing systems like Calix and IDI — rather than for service-provider developers.
Metaswitch MaX UC meetings are powered by Zoom — explicitly stated in the official Metaswitch MaX UC Client datasheet. Service providers using MaX UC are reselling Zoom-powered meetings to their end customers, not running natively integrated video. NetSapiens provides native conferencing and meeting APIs as part of the platform, with the ability for service providers to build, brand, and own the meeting experience without a third-party dependency. The difference matters in pricing, margin, and brand control — three things that compound over the life of a customer.
Since Alianza acquired Metaswitch in March 2025, industry analysts have documented the post-acquisition convergence toward Alianza Fusion and Alianza One — Alianza’s own cloud-native platforms.1 Service providers running MaX UC today face strategic uncertainty about long-term roadmap investment in the Metaswitch-origin product line. NetSapiens is the platform Crexendo invests in directly as its UCaaS engine, with active development across AI, mobile, contact center, and platform automation. Service providers on NetSapiens are aligned with a forward-looking roadmap rather than a managed sunset.
Metaswitch MaX UC is sold through the Alianza commercial model — subscription-based, in Alianza’s cloud, on Alianza’s terms. NetSapiens offers service providers two paths: subscription licensing (OpEx) or perpetual license (CapEx), with self-host or Crexendo-cloud deployment options. The platform adapts to the service provider’s commercial strategy rather than the other way around. The flexibility is preserved over time — service providers can change commercial models as their business evolves.
Both platforms support brandable end-user clients (logo, colors, app store presence). The difference is at the platform level: NetSapiens is 100% white-label across every customer touchpoint, with no NetSapiens or Crexendo branding visible to end users anywhere in the experience. The platform disappears so the service provider’s brand takes center stage. MaX UC’s brandable client experience is mature, but operational and managed-service touchpoints have more visible vendor presence over time.
You’re not alone. Service providers are migrating off Metaswitch every quarter — and NetSapiens is where most of them end up. 80+ API categories, full OpenAPI schema, interactive reference, no certification gate. Build a webhook-driven prototype this weekend.
HS Form: Netsapiens | Contact Us
