If you run a single office phone system, FreePBX is a proven, mature choice. If you sell phone service to many customers and want each one branded as your own, ICTPBX fits better. It’s multi-tenant and white-label from the ground up, while FreePBX is built to manage one organization at a time.
What each platform is
FreePBX is a web GUI for Asterisk, maintained by Sangoma. It’s open source, widely deployed, and backed by a large community plus optional commercial modules and support. It does one job well: giving you a friendly interface to configure a single Asterisk PBX.
ICTPBX is a multi-tenant, white-label PBX management application for ISPs, ITSPs, and service providers. It runs on FreeSWITCH and is unified through the open source PBX software layer of the ICTCore REST API, so you manage every tenant, extension, trunk, and DID from one modern dashboard.
ICTPBX vs FreePBX at a glance
| Capability | ICTPBX | FreePBX |
|---|---|---|
| Core engine | FreeSWITCH | Asterisk |
| Multi-tenancy | Native, built in | Single tenant per instance |
| White-label branding | Per-tenant logo, theme, and domain | Limited, mostly commercial |
| REST API | ICTCore REST API | GraphQL and REST, module dependent |
| Billing and packages | Built in, per tenant | Not included |
| Fax | Fax over IP and fax-to-email | Add-on modules |
| Browser softphone | WebRTC calling included | Module or third party |
| Licensing model | Self-hosted, no per-user fees | Free core, paid commercial modules |
| Best fit | Providers reselling to many customers | A single business or IT team |
Multi-tenancy and white-label
This is the clearest dividing line. FreePBX manages one organization per install. To serve many customers, you run a separate instance for each, or you buy a commercial multi-tenant product. That means more servers to patch, more dashboards to watch, and no shared billing view.
ICTPBX treats tenancy as a first-class idea. You create a tenant, set its branding, assign DIDs and trunks, and that customer logs in to a portal that looks like yours. You can set a unique logo, company name, theme colors, login background, and support contact per tenant, so every client runs under your brand from one platform.
Architecture: FreeSWITCH vs Asterisk
FreePBX is tied to Asterisk, which has a huge community and broad device support. ICTPBX runs on FreeSWITCH, which is built for high concurrency and clean call handling across many simultaneous sessions. For a provider pushing real call volume across many tenants, that concurrency model matters. Neither engine is wrong; they’re tuned for different jobs.
API and automation
If you want to provision customers from your own portal or sync with a CRM and billing stack, the API is where you’ll live. ICTPBX exposes the ICTCore REST API, so creating tenants, extensions, trunks, and DIDs can be scripted and tied into your existing systems. FreePBX offers GraphQL and REST endpoints, but coverage depends on the modules you’ve installed, and it’s scoped to a single PBX rather than a fleet of tenants.
Monetizing the platform
FreePBX has no built-in way to package and bill service. You add a separate billing system. ICTPBX includes packages and subscriptions, so you can define resource limits, assign a plan to a tenant, and meter usage like voice minutes and fax pages. For a provider, that turns the PBX from a tool into a product you can sell. Pricing for ICTPBX is published openly on the pricing page, with no per-user licensing.
Which one should you choose
Pick FreePBX if you’re running one phone system for one organization, you’re comfortable with Asterisk, and you value its mature module ecosystem and community.
Pick ICTPBX if you sell communication services, need native multi-tenancy and white-label branding, want a REST API to automate onboarding, and need billing built in. If you’ve been comparing hosted PBX options for resale, this is the gap ICTPBX is designed to fill.
Frequently asked questions
Is ICTPBX a fork of FreePBX?
No. ICTPBX runs on FreeSWITCH and is built on the ICTCore REST API, while FreePBX is a GUI for Asterisk. They share the goal of managing telephony but use different engines and target different users.
Can FreePBX run multiple tenants?
Not natively. You typically run one FreePBX instance per organization or buy a commercial multi-tenant product. ICTPBX supports many tenants from a single install.
Does ICTPBX support fax?
Yes. ICTPBX handles fax over IP and inbound fax-to-email, managed in the same dashboard as voice, alongside SIP trunks and DIDs.
Can I brand ICTPBX for my customers?
Yes. Each tenant can have its own logo, company name, theme colors, login background, and support contact, so customers see your brand instead of a generic interface.
Is ICTPBX open source and self-hosted?
Yes. ICTPBX is open source and self-hosted, with no per-user licensing fees, so you keep control of your data and your customers.
Which is better for a service provider?
For reselling phone service to many customers, ICTPBX fits better because of native multi-tenancy, white-label branding, the ICTCore REST API, and built-in billing. FreePBX is a strong fit for a single organization.
Want to see it running before you decide? Talk to us and we’ll walk you through a multi-tenant setup.