A cross-platform softphone built by a Bulgarian team. It only does the client, which keeps it neutral towards every SIP provider.
# No corporate parent, no open-source licence, and yet it covers virtually every mainstream platform and is treated as a default client by carriers and call centres alike. Its survival logic is worth a closer look.
Zoiper is a softphone that runs on Windows, macOS, Linux, Android and iOS. You configure any SIP or IAX2 account inside it and dial out like a normal phone. The interface is not beautiful, but in VoIP circles it is one of the names most often recommended.
The developer is Securax EOOD, a small software company in Sofia, Bulgaria. Unlike many communications vendors it runs no carrier business and has no vast hardware line — revenue comes from commercial softphone licences, SDK licensing and white-label branding work.
That client-only positioning keeps it neutral in the ecosystem: it does not compete with carriers and does not bind itself to one platform. Whatever SIP provider's account you hold, it works inside Zoiper.
In communications the most stable business is rarely selling calls. It is selling the client that makes the calls.
The hard part of a softphone was never the interface. It is running the same protocol stack correctly on every system: audio device enumeration, Bluetooth switching, background keep-alive, push wakeup, platform power policy — every platform fails differently. Zoiper implements native code per platform rather than wrapping a cross-platform UI framework. More work, in exchange for control over the audio path.
That matters most in call centres. An agent takes dozens of calls a day and will report every single 'connected with no audio'.
The free tier is not crippled: basic calling, multiple accounts and common codecs are included. Payment unlocks recording, conferencing and the management and customisation enterprise deployment requires. The strategy brought in a large base of individuals and small teams while giving the commercial edition a natural upgrade path.
Individuals holding a SIP account who need it across devices; carriers and MSPs white-labelling a softphone; software vendors embedding calling; support teams needing recording and transcription.
It suits less well teams wanting to modify open-source code deeply — this is a closed product, and customisation goes through the official SDK and branding service.