Custom vs White-Label Softphone: Which to Choose

The two options

A white-label softphone is an existing app that a vendor rebrands for you. You choose a name, logo and colours and supply your SIP settings; the vendor builds your branded version, publishes it (often under your app store accounts) and keeps it updated. You pay a set-up fee and a monthly fee, sometimes with charges per active user or per feature.

A custom softphone is built specifically for you. A development team takes a proven SIP engine, such as Linphone or PJSIP, and builds your interface, features and integrations around it. You own the code and decide what it does and when it changes; you also carry the build cost and ongoing maintenance, directly or through your partner.

There's a middle option

Between the two sits an SDK-based app: your own interface and features, built on a commercial or open-source SIP SDK that handles the calling engine. It is really a form of custom development, but much faster than writing a SIP stack, which almost nobody should do.

White-label vs custom, side by side

Cost and time to launch

White-label pricing is usually published or quoted per month. As one published example, Acrobits lists its white-label Cloud Softphone from about $549 a month, with optional per-user charges for some features, and quotes a one-time fee of around $4,200 plus monthly support for apps built on its platform. Other vendors price differently, so compare like for like, including per-user fees at your expected user numbers.

Custom ranges match our VoIP mobile app development page.

Over several years the picture can flip. A monthly fee that is trivial for a hundred users can become significant for tens of thousands, especially where per-user charges apply, while a custom app's cost is mostly upfront.

What any softphone must get right

Whichever route you choose, these are the things that separate a softphone customers rely on from one they uninstall. Ask any vendor or developer how they handle each.

Our Flutter CallKit and PushKit guide and React Native CallKit guide cover push and native calling screens in detail.

SIP engine licensing: read this before building custom

Custom softphones almost always use an existing SIP engine, and the licence matters as much as the code.

Budget the licence into the project from the start. Our Linphone and PJSIP guide compares the two engines in depth.

Provisioning: the feature that saves support time

For a provider with many customers, setup support is a real cost. Both white-label and custom apps should provision accounts automatically. Here is what a simple remote-provisioning file looks like for a Linphone-based app; the app fetches it over HTTPS after the customer scans a QR code.

<?xml version="1.0" encoding="UTF-8"?>
<config xmlns="http://www.linphone.org/xsds/lpconfig.xsd">
  <section name="proxy_0">
    <entry name="reg_proxy">&lt;sip:sip.example.com;transport=tls&gt;</entry>
    <entry name="reg_identity">"Alice" &lt;sip:[email protected]&gt;</entry>
    <entry name="reg_expires">3600</entry>
    <entry name="reg_sendregister">1</entry>
    <entry name="push_notification_allowed">1</entry>
  </section>
  <section name="auth_info_0">
    <entry name="username">alice</entry>
    <entry name="ha1">8f2b...e91c</entry>   <!-- hashed, never the plain password -->
    <entry name="realm">example.com</entry>
  </section>
  <section name="sip">
    <entry name="media_encryption">srtp</entry>
  </section>
</config>

Keep the provisioning service on your own platform, whichever app you use. Then you can change servers or features centrally, and you can switch apps later without re-onboarding every customer by hand.

Desktop and web: the platforms people forget

Mobile gets the attention, but many business customers spend their day at a computer. A complete calling service usually needs a desktop app for Windows and macOS, a web softphone that runs in the browser, or both.

White-label vendors differ widely on desktop and web support, so check both if your customers need them. For custom builds, a shared interface codebase, for example Flutter, keeps all platforms consistent. Our WebRTC-SIP gateway case study shows how browser calling reaches a provider's SIP platform.

Maintenance after launch

A softphone is never finished. Every major iOS and Android release can change how background tasks, notifications and calling screens behave, and app stores update their policies regularly. Whoever owns the app has to keep up.

• Test every new iOS and Android version before it reaches customers, especially incoming calls on locked phones.
• Update the SIP engine and its security fixes on a regular schedule.
• Keep push certificates and keys current; expired credentials silently stop incoming calls.
• Watch app store reviews and crash reports, and respond quickly to call failures.
• Re-check app store declarations, such as Android's full-screen intent permission, when policies change.

With white-label, this is the vendor's job, which is part of what the monthly fee pays for. With custom, it is yours or your partner's, so plan a maintenance arrangement before launch rather than after the first broken release.

Moving from white-label to custom later

Many providers start with white-label and move to custom once the app matters more to their business. The move is straightforward if you prepare for it from the start.

When white-label is the right choice

• You need an app in weeks, for example to win or keep customers who ask for one.
• Standard calling, messaging and perhaps video cover what your customers need.
• The app supports your service rather than being the product itself.
• You have a modest number of users, so monthly and per-user fees stay small.
• You don't want to manage app development or app store releases.

If this is you, a good white-label vendor is the sensible choice. Our sister company Sheerbit offers ready-made white-label products; CelloIP focuses on custom, branded apps.

When custom is the right choice

• The app is part of your product and should look and behave like your brand, not a template.
• You need features or integrations a vendor won't build: your portal, billing, CRM, custom call flows.
• You serve many users, so per-user fees would add up over the years.
• You need control over releases, data and security reviews.
• You want to differentiate from providers using the same white-label base app.
• You want to own the code and its value.

A real custom example

CelloIP built a branded SIP softphone for a VoIP service provider, covering Android, iOS, desktop and web:

• One Flutter codebase for the interface over a native SIP engine, with WebRTC for the web version.
• Push for incoming calls through Firebase Cloud Messaging on Android and PushKit with CallKit on iOS.
• TLS and SRTP encryption, QR code or link provisioning, video calls and chat.
• Published under the provider's own name; built in three to six months and maintained by CelloIP.

Questions to ask before you decide

Frequently asked questions