Forem: Tahir Almas

Open Source PBX Software in 2026: A Practical Buyer's Guide

Tahir Almas — Thu, 07 May 2026 10:43:59 +0000

Originally published at ictpbx.com

If you're searching for open source PBX software in 2026, you've already worked out that the per-seat SaaS phone bills aren't getting cheaper and the lock-in isn't getting friendlier. The honest follow-up question is which open source PBX you should actually pick, and the honest answer depends almost entirely on what you're trying to do with it. A 30-person office, a hospital, and a service provider running hosted voice for 200 customers should not be picking the same platform. This guide walks through the options that genuinely belong on a 2026 shortlist, where each one fits, and the trade-offs that don't usually make it into the comparison tables.

What "Open Source PBX Software" Actually Means in 2026

The term covers two different things, and conflating them is how teams end up with the wrong tool. The first meaning is a media engine and signaling stack you can self-host: Asterisk and FreeSWITCH are the two foundational projects everyone else builds on. The second meaning is a complete platform with a web dashboard, tenant management, billing, and the operational pieces a service provider needs to actually deliver hosted voice. Most of what people end up reaching for is in the second category, even when the search term is the broader "open source PBX."

The reason this matters is cost. A vanilla Asterisk install is genuinely free. A production-grade multi-tenant PBX platform built on Asterisk is not, because you've either paid an engineer to build the multi-tenant layer or you've paid a vendor for a packaged platform that already has it. Knowing which side of that line you're on saves a lot of confused budgeting later.

The Open Source PBX Options Worth Comparing

1. Asterisk (usually with FreePBX as the dashboard)

Asterisk has been the default open source PBX since 1999, and most of the small-business hosted voice market still runs on it under the hood. On its own, Asterisk is a powerful but command-line-heavy telephony engine. Almost nobody deploys it raw. The pairing you actually see in the field is Asterisk plus FreePBX, where FreePBX provides the web UI and the module system that turns dialplan editing into clicking checkboxes.

What works well: it's mature, the documentation is endless, and the talent pool is genuinely deep. If you need to hire a contractor to fix something at 2am, you'll find one. The module ecosystem covers virtually every PBX feature anyone has ever asked for, including some you'd rather they hadn't.

Where it falls short: multi-tenancy. Asterisk plus FreePBX is fundamentally a single-tenant design. You can run multiple instances per server, isolate them with containers, and stitch a billing layer on top, but you're building integration glue every step of the way. For a 50-person office or a single business, this doesn't matter. For a service provider trying to host 100 customers on shared infrastructure with isolated extension number spaces and tenant-aware billing, it matters a lot.

2. FreeSWITCH (the API-first option)

FreeSWITCH started as a rewrite of the lessons learned from Asterisk, and it's the engine behind a large share of carrier-grade and cloud-PBX deployments worldwide. It's better at concurrent call handling, better at codec transcoding, and far better at being driven by an external control plane through its event socket and REST APIs. The trade-off is that FreeSWITCH is even less of a finished product than raw Asterisk. You're getting a media engine, not a PBX.

This is exactly what you want if you're building a custom voice product, integrating tightly with your own application, or running a contact-center workload where you need precise control over call flows from your own code. It's exactly what you don't want if you need a working PBX UI on day one without writing software.

3. ICTPBX (white-label, multi-tenant, built on FreeSWITCH)

ICTPBX is the platform you reach for when you've decided you want the FreeSWITCH foundation but you don't want to spend the next six months building tenant management, a customer portal, and a provisioning workflow. The stack is ICTCore for the REST API and orchestration, FreeSWITCH for SIP and media, and an Angular dashboard for both system admins and tenant admins. Two things make it different from most other open source PBX options:

Multi-tenancy is built in, not bolted on. Each tenant gets its own extension number space, its own queues and IVRs, its own CDRs and recordings, and a tenant-administrator role with no visibility into other tenants. Two customers can both use extension 1001 on the same instance without colliding. For an ITSP or MSP reselling hosted voice, this is the single biggest piece of the platform you'd otherwise have to build yourself.

White-labeling is part of the base product. Logo, brand color, sub-domain, email templates, and tenant contact info are all configurable from the system admin panel. There's no "Powered by" footer your customers will ask you to remove. You're selling your service, not a re-skinned vendor product.

Day-one feature set covers what a hosted voice customer expects: SIP voice with internal extensions and external trunks, fax over T.38 (properly negotiated, not faked over G.711), IVR menus, time conditions, ring groups, queues with strategy options, voicemail to email, call recording, conferences, and CDRs for billing. The architecture documentation covers how the control plane and media plane separate so you can scale them independently. If you're evaluating where ICTPBX sits in a wider open source ICT product family, the ict.vision/ict-pbx overview lays out the integration story with the rest of the Vision portfolio.

4. 3CX (worth naming, not actually open source)

3CX shows up in nearly every open source PBX comparison thread, even though it isn't open source. It's commercial proprietary software with a free tier for small deployments. The reason it ends up in this conversation is that 3CX customers are often the ones searching for an open source PBX in the first place, usually after a licensing change or a forced cloud migration prompted them to look at the alternatives. If that's you, the actual open source options worth evaluating are the three above.

Open Source PBX Comparison at a Glance

PlatformBest ForMulti-TenantWeb DashboardWhite-LabelSetup EffortAsterisk + FreePBXSingle business, on-premiseWorkarounds onlyFreePBXCustom workMediumFreeSWITCH (vanilla)Custom builds, contact center enginesYou build itNoneYou build itHighICTPBXITSPs, MSPs, hosted voice resellersNativeAngular SPANativeLow to medium
The row this table doesn't show is the one most teams need to think about: who you're going to be calling when something breaks at 11pm. Asterisk has the deepest support market by a wide margin. FreeSWITCH has a smaller but very capable community. ICTPBX has direct vendor support; if you'd rather pay a support contract than maintain a relationship with a freelance Asterisk consultant, that's a feature, not a footnote.

Where Most Open Source PBX Stacks Fall Short: Multi-Tenant and White-Label

This is the part of the buying decision that's most often hand-waved in comparison articles, and it's where service providers feel the pain six months in. "Multi-tenant" in the marketing sense usually means "the software lets you make multiple accounts." That's not the same thing as proper tenant isolation, and the difference shows up the first time two customers want to use the same extension number, or the first time you have to explain to one customer why their CDR export contains another customer's call records.

A real multi-tenant PBX has isolated extension number spaces per tenant, per-tenant CDR storage, per-tenant call recording paths, per-tenant gateway and trunk routing, and a tenant administrator role that can't see the rest of the platform. Building all of that on top of a single-tenant codebase like Asterisk plus FreePBX is the work that turns a "free" PBX into a six-month engineering project. Picking a platform where it's already done is the difference between launching a hosted voice service in a quarter and launching one next year.

White-labeling has a similar gap between marketing and reality. Most open source PBX projects let you swap the logo. A platform that's actually white-label-by-default lets you swap the logo, the favicon, the brand color, the email-notification templates, the customer-facing sub-domain, and the support contact information, all without forking the codebase. If you're reselling, anything less means your customers eventually figure out who the real vendor is, and your margin pressure starts there.

What Self-Hosting an Open Source PBX Actually Costs

The software is free. Everything else is not. Here's the realistic three-year cost picture for an ITSP running 100 extensions across, say, ten customer tenants:

Server infrastructure: a media node sized for 100 concurrent calls runs comfortably on a 4 vCPU / 8GB VPS at $40 to $80 per month, depending on disk and recording retention. Plan two nodes for redundancy.
SIP carrier minutes and DIDs: entirely separate from the PBX cost. Budget $0.005 to $0.02 per minute for outbound and $1 to $3 per DID per month for inbound, depending on geography and carrier.
Engineering time: the part most underestimated. A vanilla Asterisk + FreePBX deployment with no multi-tenant work needed is maybe 40 to 80 hours of initial setup. Add tenant isolation work and you're looking at 200 to 400 engineering hours before you can sell. Platforms with native multi-tenancy collapse this to the dashboard configuration work, often 10 to 20 hours per tenant.
Ongoing maintenance: security patches, version upgrades, backups, monitoring, and the inevitable Tuesday-night carrier issue. Plan one to two hours a week per production deployment, more during major version upgrades.
Support contracts (optional): if you don't have in-house FreeSWITCH or Asterisk expertise, a support contract from a vendor like ICT Innovations is usually cheaper than a senior contractor on retainer.

The math that actually changes the answer: at any reasonable extension count above 50, an open source PBX with native multi-tenancy beats per-seat SaaS PBX pricing on a three-year basis. Below that, the SaaS model often wins on operational simplicity, and that's not nothing. Don't pick open source on principle if you're a 12-person company that just needs phones to work.

Picking the Right Open Source PBX for Your Use Case

The decision is shorter than the comparison tables suggest.

You're a single business with under 100 extensions, on-premise or self-hosted, and you don't plan to resell voice service. Pick Asterisk plus FreePBX. The community is huge, the deployment is well-trodden, and the feature set is more than enough for an internal phone system.

You're a software team building a custom voice product or a contact-center workload where you control the call flow from your own code. Pick FreeSWITCH. You'll write more code, but you'll have the precise control that PBX-in-a-box products can't give you.

You're an ITSP, MSP, or reseller that needs to host hosted voice for multiple customers, with branded portals and isolated tenant data, and you don't want to spend a quarter building the multi-tenant layer yourself. Pick ICTPBX. The native multi-tenancy and white-labeling are the parts you'd otherwise be building, and the FreeSWITCH foundation under it gives you the same media engine the carriers use.

You're currently on 3CX or a per-seat SaaS PBX brand and you're tired of the licensing model. Re-evaluate based on the criteria above. Most refugees from per-seat pricing fall into one of the three buckets, and "open source" by itself isn't a destination, it's a category.

FAQ: Open Source PBX Software

What's the best open source PBX software in 2026?

There isn't a single "best" because the right pick depends on whether you're a single business, a software team building a custom voice product, or a service provider hosting voice for multiple customers. Asterisk plus FreePBX wins for single-business deployments. FreeSWITCH wins for custom builds. ICTPBX wins for multi-tenant hosted voice scenarios where white-labeling and tenant isolation matter.

Is FreeSWITCH better than Asterisk?

It's not better in the abstract. FreeSWITCH handles concurrent calls and codec transcoding more efficiently and exposes a cleaner API surface, which makes it the natural choice for custom voice applications and carrier-grade media nodes. Asterisk has a deeper community, more pre-built modules, and a much wider talent pool. For a finished, web-managed PBX experience, neither one is a complete answer on its own.

What is multi-tenant PBX software?

It's PBX software designed so multiple customer organizations can share one platform installation while staying fully isolated from each other. Each tenant gets its own extension number space, its own users and admins, its own call records, and its own configuration. ITSPs and MSPs use multi-tenant PBX platforms to deliver hosted voice service to many customers without provisioning a separate server per customer.

Can I white-label open source PBX software?

You can with most platforms, but the depth of the white-labeling varies a lot. Some let you swap the logo and call it done. Others let you customize the logo, favicon, brand color, email templates, and customer-facing portal sub-domain without code changes. ICTPBX is white-label by default; Asterisk plus FreePBX requires custom theme work to reach the same depth.

Does open source PBX software support fax?

Yes, but the implementation matters. T.38 is the protocol you want for fax over IP; G.711 audio passthrough fails on most modern carriers because the audio compression destroys the fax tones. ICTPBX includes T.38 fax in the day-one feature set. Asterisk and FreeSWITCH both support T.38 with proper configuration; FreePBX has fax modules that handle the dialplan side.

What does it really cost to self-host an open source PBX?

The software is free. Server infrastructure runs $40 to $150 per month for a small to mid production deployment. Carrier minutes and DIDs are separate. The biggest hidden cost is engineering time: a vanilla deployment is 40 to 80 hours, while building proper multi-tenancy on top of a single-tenant platform adds 200 to 400 hours. Platforms with native multi-tenancy collapse that to dashboard configuration time.

Is ICTPBX based on Asterisk?

No. ICTPBX is built on FreeSWITCH for the SIP signaling and media engine, ICTCore for the REST API and orchestration layer, and Angular for the web dashboard. The choice of FreeSWITCH over Asterisk reflects the platform's focus on multi-tenant, carrier-grade workloads where concurrent call density and API control matter more than module breadth.

Ready to Look at ICTPBX in Detail?

If multi-tenant hosted voice with native white-labeling is what you're actually trying to build, the ICTPBX platform overview and the documentation are the next two stops. The ICT Vision support portal handles pre-sales questions, evaluation environments, and managed deployment requests through the same queue.

Related Resources

Open Source Customer Support Ticket System: Best Picks for 2026

Tahir Almas — Thu, 07 May 2026 09:23:08 +0000

Originally published at ictdesk.net

If you're hunting for an open source customer support ticket system, you're probably one of two people. Either your Zendesk renewal just landed and the per-agent pricing finally crossed the line from annoying to absurd, or you're a small team launching a product and you don't want to start the customer relationship by funnelling every conversation through somebody else's database. Both reasons are valid. The shortlist that fits each one, though, is different — and that's what this guide is really about.

Before we get into the comparisons, a quick reality check. "Free" software is rarely free once you add up server time, the inevitable Saturday spent debugging an SMTP setup, and the weeks of agent retraining. The honest math still favours open source for most growing teams, but only if you pick the platform that matches how your support actually works today, not the one with the prettiest screenshots.

What an Open Source Customer Support Ticket System Is — and Isn't

At its core, the software does three things: capture an inbound message (email, web form, chat), turn it into a tracked ticket, and give an agent the tools to reply, route, escalate, and eventually close it. Open source just means the source code is public, you can self-host it, and the licence lets you modify and redistribute it. That's it. The label tells you nothing about whether the product is good for your team.

What it isn't: a magic cost-saving lever. The minute your team grows past a couple of agents, you'll need infrastructure, backups, monitoring, and someone who genuinely understands the platform. Plan for those costs and the savings versus a per-seat SaaS bill are still big. Skip them and you'll wish you'd just paid Zendesk.

The Open Source Customer Support Ticket Systems Worth Your Time

osTicket — The Reliable Default

osTicket has been around since 2003 and it shows, in good ways and bad. The good: rock-solid email-to-ticket conversion, departments, SLA plans, canned replies, a simple customer portal, and a community-supported codebase that hasn't broken anyone's deployment in years. You can have it running on shared LAMP hosting if you want to. For a small support team that lives in email, this is the lowest-effort starting point you'll find.

Where osTicket falls short is the modern stuff. The interface is dated. There's no built-in live chat. The mobile experience is functional rather than pleasant. If your customer support workflow is "we read emails and reply to them," none of that matters. If you've ever offered a chat widget on your site, it will.

Real-world fit
A 4-person nonprofit running grant inquiries through a single shared inbox switched to osTicket on a $12/month VPS. Setup took an afternoon. Two years later, no upgrade pressure — they simply don't need anything else.

Zammad — The Modern All-Rounder

Zammad is what osTicket would look like if it had been redesigned in 2020. A clean Vue interface, a unified inbox that pulls in email, Twitter, Facebook, Telegram, and chat, Elasticsearch under the hood for fast search across million-ticket histories, and a customer portal that doesn't make your customers wince. The free self-hosted edition is genuinely full-featured.

Honest pick for: mid-size teams (10–50 agents) that have multiple inbound channels and want one inbox to rule them all. The trade-off is infrastructure weight. Elasticsearch alone wants 4GB of RAM and steady CPU; you're not running this on a budget VPS the way you would with osTicket. Plan a proper server.

FreeScout — The Helpscout Lookalike

FreeScout is the platform people pick when they want the Helpscout interface without the per-mailbox bill. Conversations, not tickets. Threaded email, internal notes, customer profiles, saved replies. The interface is genuinely the cleanest of any open source option here, and a SaaS team migrating from Helpscout will feel at home in twenty minutes.

Where it sits in the lineup: best for SaaS and ecommerce teams that conceptually treat support as conversations rather than tickets. Limited reporting compared to Zammad, no native ITSM features, and the live chat integration is via paid third-party modules. For its core use case, though — small to mid SaaS support teams that need email handled gracefully — it's the strongest fit on this list.

UVdesk — The PHP/Laravel Option

UVdesk is built on Symfony and aimed squarely at ecommerce. It plugs into Shopify, Magento, OpenCart, and Prestashop out of the box, which means an agent answering a Shopify customer can see the order, the shipping status, and the refund history without leaving the ticket. For online stores doing five-figure ticket volume a month, that integration alone usually justifies the choice.

It's less interesting outside ecommerce. The UI is fine but not striking, the community is smaller than Zammad's or osTicket's, and you'll find fewer Stack Overflow answers when something breaks. That last point matters more than people admit when they evaluate open source.

ICTDesk — When Live Chat and AI Need to Be in the Same Place as Tickets

ICTDesk is worth a look if your support model is shifting from "we answer email" toward "we answer in the moment, on the website, and an AI handles the easy questions." It bundles real-time live chat, an AI assistant trained on your own help content, visitor intelligence so agents see who they're talking to, and a structured ticket layer underneath all of it. For a SaaS support team trying to reduce tier-1 volume without firing anyone, the combination is genuinely useful.

The source-code licence model is what tips the scales for white-label scenarios. You get the full Laravel backend and the apps, you deploy it on your own servers, and you can run multiple branded tenants from one install. That's a different value proposition from osTicket or Zammad, both of which can be self-hosted but aren't really designed for an agency to resell.

Try ICTDesk Free for 14 Days

Live chat, AI bot, and ticketing in one platform. Self-hosted or managed. No credit card to start.

[Create Your Account](https://service.ictdesk.net/tenant/register)
[View All Features](/features.html)

Comparison at a Glance

      Tool
      Best For
      Channels
      Live Chat
      AI / Bot
      Setup Effort



    osTicketTiny teams, email-onlyEmail, formNoNoLow
    ZammadMid-size, multi-channelEmail, social, chatBuilt-inLimitedMedium
    FreeScoutSaaS, ecommerceEmail-firstModulesModulesLow
    UVdeskShopify/Magento storesEmail, store integrationsModulesNoMedium
    ICTDeskLive chat + AI + ticketing, MSPsChat, email, AIBuilt-inBuilt-inLow

The row the table doesn't show is the one that matters most: how much your support volume is shifting from email to real-time. If it's stable, osTicket or FreeScout will serve you for years. If chat conversations are climbing every quarter, you're going to outgrow an email-first tool faster than you think, and the migration is painful enough that picking right the first time pays for itself.

Picking the One That Actually Fits You

Forget the binary checklists. Here's how teams I'd trust would think about it.

You're a two-person nonprofit, charity, or solo consultant. Your customers email you. They will keep emailing you. Pick osTicket. It runs on cheap hosting, the learning curve is an afternoon, and you can stop reading help desk reviews and get on with your actual work.

You're a SaaS team of 5–15 supporters and your inbox is starting to feel like a swamp. FreeScout if you want a Helpscout-style conversation feel, Zammad if you've got Twitter, Facebook, and chat all funnelling questions in alongside email and need a unified inbox. Both are solid; the choice is taste, not capability.

You sell through Shopify, WooCommerce, or Magento and your ticket volume is mostly order-related. UVdesk. The store integrations save more agent time per ticket than any feature you'd buy elsewhere.

You're running a B2B product, customers expect a chat widget on the marketing site, and you want an AI that handles the "where do I find my invoice" questions without paging a human. ICTDesk. The reason isn't that it ticks the most checkboxes — it's that the live chat and bot pieces aren't bolted on, they're how the platform is designed to work.

What Self-Hosting Actually Costs

Two numbers most blog posts skip. First, the infrastructure: a serious deployment of any of these tools — even osTicket past a couple of agents — will run somewhere between $30 and $150 a month in cloud costs, depending on disk and RAM. Zammad is at the higher end because of Elasticsearch. Second, the human cost: someone owns the upgrades, the SSL certificate renewal, the off-site backups, and the inevitable Tuesday when something breaks. If nobody on your team wants that role, the math changes a lot.

For teams that don't want the operational tail, every platform on this list has a managed option. ICTDesk offers managed deployment alongside the source code licence, which is roughly the best of both: you keep the freedom to migrate off, but somebody else handles the patching. That's the pragmatic choice for most SaaS teams who'd rather build their product than babysit a Linux box.

Migrating Off Zendesk, Freshdesk, or Intercom

This is where most teams get stuck and quietly give up on the move. The actual mechanics aren't bad — every tool here imports CSV, several have direct Zendesk and Freshdesk JSON importers — but you have to plan a parallel-run window. Run the new system in shadow for a couple of weeks. Route 10% of new tickets there. Train agents on the new interface while they're still mostly in the old one. Then cut over.

Teams that try to flip a switch on Friday and have everyone using the new tool on Monday almost always bounce back to the SaaS platform. Teams that run parallel for two to four weeks rarely do.

FAQ: Open Source Customer Support Ticket Systems

What is an open source customer support ticket system?
It's customer support software whose source code is publicly available. You can self-host, modify, and extend it. Popular options include osTicket, Zammad, FreeScout, and ICTDesk. The label says nothing about quality — it just means you have the freedom to control how the software runs and where the data lives.



Is there a free customer support ticket system that handles email and live chat together?
Yes. Zammad and ICTDesk both bundle email ticketing with live chat in their free or open editions. FreeScout focuses on email but integrates with chat tools through paid modules. Pure email-only options like osTicket need a separate live chat app such as Tawk.to or Crisp wired in.



Can a small team really self-host a ticket system?
Yes, if someone on the team is comfortable with a Linux server. osTicket and FreeScout are the easiest to install. Zammad needs more horsepower because of Elasticsearch. Plan to spend a weekend on initial setup, then a few hours a month on updates and backups. If nobody wants that work, pick a managed deployment instead.



What's the difference between an open source help desk and a customer support ticket system?
Most people use the terms interchangeably. Strictly speaking, a help desk often implies internal IT support, while a customer support ticket system points outward at end customers. The underlying software is usually the same — only the configuration and reporting differ.



Is open source actually safer than a SaaS help desk?
It can be. You control where customer data lives, who has access, and how long it's retained. But security still depends on patching, backups, and config. A neglected self-hosted server is less safe than a well-run SaaS provider. Open source gives you the option to be more secure, not the guarantee.



Can I migrate from Zendesk or Freshdesk to an open source ticket system?
Yes. Most platforms accept email/contact CSV imports, and several have direct importers for Zendesk and Freshdesk JSON exports. Plan for a parallel-run period of a couple of weeks so agents adapt without dropping live tickets. The technical migration is usually faster than the organisational one.

Related Resources

  [IT Ticketing System Open Source: Best Tools for IT Teams in 2026](/blog/it-ticketing-system-open-source.html)
  The companion guide for internal IT service desks — osTicket, Znuny, Zammad, GLPI, and ICTDesk compared.



  [Open Source Help Desk Software: The 2026 Buyer's Guide](/blog/open-source-help-desk-software.html)
  Broader buyer's guide covering help desk platforms across every team size.



  [ICTDesk Platform Features](/features.html)
  Live chat, AI chatbot, visitor intelligence, multi-tenant support, and white-label options.



  [Start Your Free Trial](https://service.ictdesk.net/tenant/register)
  14-day full access to ICTDesk. No credit card required. AI bot live in 5 minutes.

Open Source PBX Software in 2026: A Practical Buyer's Guide

Tahir Almas — Thu, 07 May 2026 09:23:07 +0000

Originally published at ictpbx.com

What "Open Source PBX Software" Actually Means in 2026

The Open Source PBX Options Worth Comparing

1. Asterisk (usually with FreePBX as the dashboard)

2. FreeSWITCH (the API-first option)

3. ICTPBX (white-label, multi-tenant, built on FreeSWITCH)

4. 3CX (worth naming, not actually open source)

Open Source PBX Comparison at a Glance

PlatformBest ForMulti-TenantWeb DashboardWhite-LabelSetup EffortAsterisk + FreePBXSingle business, on-premiseWorkarounds onlyFreePBXCustom workMediumFreeSWITCH (vanilla)Custom builds, contact center enginesYou build itNoneYou build itHighICTPBXITSPs, MSPs, hosted voice resellersNativeAngular SPANativeLow to mediumThe row this table doesn't show is the one most teams need to think about: who you're going to be calling when something breaks at 11pm. Asterisk has the deepest support market by a wide margin. FreeSWITCH has a smaller but very capable community. ICTPBX has direct vendor support; if you'd rather pay a support contract than maintain a relationship with a freelance Asterisk consultant, that's a feature, not a footnote.

Where Most Open Source PBX Stacks Fall Short: Multi-Tenant and White-Label

What Self-Hosting an Open Source PBX Actually Costs

The software is free. Everything else is not. Here's the realistic three-year cost picture for an ITSP running 100 extensions across, say, ten customer tenants:

Server infrastructure: a media node sized for 100 concurrent calls runs comfortably on a 4 vCPU / 8GB VPS at $40 to $80 per month, depending on disk and recording retention. Plan two nodes for redundancy.
SIP carrier minutes and DIDs: entirely separate from the PBX cost. Budget $0.005 to $0.02 per minute for outbound and $1 to $3 per DID per month for inbound, depending on geography and carrier.
Engineering time: the part most underestimated. A vanilla Asterisk + FreePBX deployment with no multi-tenant work needed is maybe 40 to 80 hours of initial setup. Add tenant isolation work and you're looking at 200 to 400 engineering hours before you can sell. Platforms with native multi-tenancy collapse this to the dashboard configuration work, often 10 to 20 hours per tenant.
Ongoing maintenance: security patches, version upgrades, backups, monitoring, and the inevitable Tuesday-night carrier issue. Plan one to two hours a week per production deployment, more during major version upgrades.
Support contracts (optional): if you don't have in-house FreeSWITCH or Asterisk expertise, a support contract from a vendor like ICT Innovations is usually cheaper than a senior contractor on retainer.

Picking the Right Open Source PBX for Your Use Case

The decision is shorter than the comparison tables suggest.

FAQ: Open Source PBX Software

What's the best open source PBX software in 2026?

Is FreeSWITCH better than Asterisk?

What is multi-tenant PBX software?

Can I white-label open source PBX software?

Does open source PBX software support fax?

What does it really cost to self-host an open source PBX?

Is ICTPBX based on Asterisk?

Ready to Look at ICTPBX in Detail?

Related Resources

ICTPBX Released: White-Label, Multi-Tenant PBX Software Now Available for ITSPs and Service Providers

Tahir Almas — Wed, 06 May 2026 21:23:05 +0000

Originally published at ictpbx.com

ICTPBX is now generally available. It's a white-label, multi-tenant PBX platform designed for internet telephony service providers, MSPs, and resellers who want to launch a hosted voice service without building a softswitch from scratch. The stack is ICTCore for orchestration, FreeSWITCH for media, and an Angular dashboard for day-to-day management. Voice over SIP and fax over T.38 are live on day one.

What ICTPBX Is

ICTPBX is the platform you reach for when you're an ITSP and you've decided you don't want to keep duct-taping FreeSWITCH dialplans for every new customer. It gives you a multi-tenant control plane: every customer gets their own users, extensions, queues, IVRs, and call recordings, all isolated from every other tenant on the same instance. You sell the service. The platform handles the rest.

It's white-label by default. Drop your logo on the portal, point a sub-domain at the tenant view, and your customers see your brand, not ours. There's no "Powered by" footer you need to negotiate to remove.

The shortest description of who this is for: if you've been quoting SIP trunks and calling it a hosted PBX offer, ICTPBX is the product that turns that pitch into something real.

The Stack: ICTCore, FreeSWITCH, Angular

ICTPBX is built on three open standards-friendly components, and we want you to know exactly what's running under the hood. There's no proprietary black box.

ICTCore handles the REST API and orchestration. It's the layer that turns a click in the dashboard into a configured extension, a routed inbound DID, or a billable CDR. ICTCore has been in production across the ICT product family for years, so you're not getting a v1 control plane.
FreeSWITCH is the media engine. It runs SIP signaling, RTP, codecs, conferencing, and T.38 fax. FreeSWITCH is the same telephony engine behind a large share of cloud contact centers and hosted PBX services worldwide, which means there's a deep talent pool if you ever need a contractor and a long history of carrier-grade deployments.
Angular is the dashboard framework. Every screen your customer sees, and every screen your support team uses, is a modern single-page app that works on any modern browser. No softphone install for management. No Java applets. No IE-only admin pages.

If you want the deeper technical context on why a FreeSWITCH foundation matters, the ICT Innovations blog has a useful primer on how the open source SIP and media servers compare in production.

Multi-Tenant Architecture, Not Just "Multi-User"

This part matters, because there's a meaningful difference between a PBX that lets you create lots of accounts and a PBX that's actually designed for tenant isolation.

On ICTPBX, each tenant has its own:

User accounts and roles, with no visibility into other tenants
Extension number space (two tenants can both have extension 1001 without collision)
Queues, ring groups, IVR menus, time conditions, and call flows
Inbound DID assignments and gateway routing
Voicemail, music-on-hold, call recording storage, and CDRs
Billing and usage views

The tenant administrator sees only their own organization. The system administrator (you, the service provider) sees the whole instance, plus a tenant-management layer for provisioning, suspension, billing thresholds, and resource limits. The architecture documentation walks through how the control plane and media plane separate so you can scale them independently.

What You Can Run on Day One

ICTPBX ships with the modules a hosted PBX customer expects on the first day, not a roadmap that says "coming Q3."

SIP voice with internal extensions, external trunks, and standard codecs (G.711, G.722, Opus)
Fax over T.38 / FoIP, properly negotiated rather than passed through as G.711 audio (which falls apart on most carriers)
IVR menus and time conditions for after-hours routing
Call queues with strategy options (ring-all, longest-idle, round-robin, fewest-calls)
Ring groups for departments and sales teams
Voicemail with email notification and audio attachment
Conferences, follow-me, music-on-hold, and call block lists
Call recording with per-tenant storage
CDRs and usage reports for billing and audit

The call queue configuration guide and the IVR setup walkthrough are good starting points if you're seeing the platform for the first time.

What's Not in This Release (and Why We're Saying So)

Honesty up front: ICTPBX does not currently ship with email or SMS messaging modules. Both are on the roadmap, both are being actively worked on, but neither is in production yet. If your offer depends on omnichannel today, you'll want to wait or plan to integrate a separate messaging layer through the REST API.

For pure voice and fax, which is what most service-provider PBX deals are actually built around, you're set.

White-Label by Default

The white-label work is something we deliberately put on the critical path. Too many "PBX platforms" treat branding as an enterprise add-on you pay extra for. On ICTPBX it's part of the base product:

Replace the logo, favicon, and brand color from the system admin panel
Set custom email-notification templates per tenant
Use sub-domains or your own custom domains for the tenant portal
Configure your own support and contact information per tenant

The result is that your customers experience your service. Not ours. That's the difference between selling a PBX and selling someone else's PBX with your invoice attached.

Why Service Providers Are Looking at This Now

The hosted-PBX market has consolidated around two patterns, and both have problems.

The big SaaS PBX brands (you know the names) charge per seat, often $20 to $40 per user per month, and force you to resell at razor margins. Your customer's bill goes up every time they hire someone, and so does yours. You don't own the platform; you're a reseller of someone else's revenue stream.

The DIY route, where you self-build on raw FreeSWITCH or another open source softswitch, gives you control but burns engineering hours by the dozen on every new customer onboarding. By the time you've built tenant isolation, a billing layer, a customer portal, and a provisioning workflow, you've effectively built ICTPBX, just with more bugs and less documentation.

ICTPBX is the middle path. You get a multi-tenant platform with the control-plane work already done, the source code open and inspectable, and pricing that doesn't scale per seat. The economics start to work for service providers somewhere around the 50-extension mark and only get better from there. The ICT Innovations writeup on building scalable VoIP infrastructure with open source tools covers this argument in more depth.

Where ICTPBX Fits in the Vision Product Line

ICTPBX joins a product family that already includes ICTBroadcast (call center and broadcasting), ICTContact (contact center), ICTDialer (auto dialer), ICTFax (fax server), and ICTCRM. They share the ICTCore foundation, which means a service provider running multiple ICT products gets a consistent administration model and a single REST API surface to integrate against.

The product overview on the parent site at ict.vision/ict-pbx shows where the PBX sits in the wider Vision portfolio if you're evaluating a multi-product rollout.

Getting Started

If you're an ITSP, MSP, or reseller looking at ICTPBX for the first time, here's the shortest path to a working evaluation:

Pick a server. A modest VPS (4 vCPU, 8 GB RAM) handles a single-tenant pilot or a small multi-tenant deployment. For production density, expect to size based on concurrent calls rather than extensions: a media node sized for 100 concurrent calls comfortably supports 800 to 1,000 extensions on typical busy-hour assumptions.
Install the platform. The installation guide walks through the steps. If you want managed installation or hosting, the ICT operations team can do the deployment for you.
Configure your first tenant. The tenant-management documentation covers provisioning, resource limits, and suspension workflows. Spin up a test tenant, add a few extensions, and place a real call.
Connect a SIP trunk. Bring your own carrier (Twilio, Bandwidth, Telnyx, Flowroute, or any standard SIP provider). The gateway and inbound-route configuration are documented per tenant.
Brand it. Drop your logo, set the portal sub-domain, and verify the customer-facing screens show your identity.
Pilot with a friendly customer. A 10-extension pilot on a single tenant uncovers most operational questions you'll have at scale. From there, the path to general availability is mostly capacity planning and support process.

FAQ

Is ICTPBX really multi-tenant, or just multi-user with permissions?

It's multi-tenant. Each tenant has an isolated extension number space, isolated CDRs, isolated recordings, and its own admin role. Two tenants can share the same instance with no visibility into each other's traffic, users, or configuration. The system administrator sees the whole platform; tenant administrators see only their organization.

What's the underlying tech stack?

ICTCore for the REST API and orchestration, FreeSWITCH for SIP signaling and media, and Angular for the web dashboard. All three are mature components with active maintenance. The architecture cleanly separates the control plane from the media plane so you can scale them independently.

Does ICTPBX support fax?

Yes. Fax over T.38 (also called FoIP) is part of the day-one feature set, properly negotiated rather than passed through as G.711 audio. T.38 is what you want if you're carrying fax traffic over real SIP trunks; the audio-passthrough approach falls apart on most modern carriers.

Does ICTPBX support SMS or email?

Not in this release. SMS messaging and email modules are on the roadmap and being actively developed, but neither is in production today. If your offer requires omnichannel from the start, plan to integrate a separate messaging layer through the REST API.

How is ICTPBX priced?

The platform isn't priced per seat or per extension. Service providers pay for the platform license and optional support, then add their own carrier minutes and infrastructure costs on top. The economics start to favor ICTPBX over per-seat SaaS PBX brands somewhere around the 50-extension mark and improve from there.

Can I white-label the customer portal completely?

Yes. Logo, favicon, brand color, sub-domain (or your own custom domain), email templates, and contact information are all configurable. There's no "Powered by ICTPBX" footer that customers see by default.

Can I bring my own SIP trunk?

Yes. ICTPBX is carrier-agnostic. Configure your SIP gateway in the system admin panel, point inbound routes to the appropriate tenant, and you're delivering calls. Most providers run separate trunks for outbound (rated minutes) and inbound (DIDs).

Where do I get support during evaluation or production?

Open a ticket through the ICT Vision support portal. Pre-sales questions go to the same queue. Paid support and managed-hosting options are available for production deployments.

Ready to Evaluate ICTPBX?

If you've been waiting for a multi-tenant PBX platform that you can actually brand as your own and run on your own infrastructure, the wait's over. Visit the ICTPBX homepage for the platform overview, browse the documentation for the technical detail, or reach the team through the support portal to set up an evaluation environment.