FreePBX hosting with the carrier already under it.
All of FreePBX's control — dial plans, IVRs, queues, the whole admin surface — with none of the server. SIPNEX provisions a managed instance with our SIP trunks connected, your DIDs pointed at it, and A-level STIR/SHAKEN signed under our own certificate. One vendor, both layers.
A managed FreePBX. Trunks already connected.
A managed FreePBX instance
SIPNEX provisions and runs the instance; you get the FreePBX admin interface. Dial plans, IVRs, and queues stay yours — the patching, uptime babysitting, and 2 a.m. server duty don't.
Trunks connected before handoff
The instance arrives with SIPNEX SIP trunks registered and passing calls. No gateway spelunking, no 'check with your trunk provider' — the carrier is already under the PBX.
No per-channel trunk fees
Trunking on your hosted instance is billed on usage, not on how many simultaneous calls you're allowed to make. Concurrency isn't a line item to outgrow.
A-level attestation on outbound
Calls leaving your instance are signed A-level under our own STIR/SHAKEN SP-KI certificate. No reseller chain deciding what attestation your caller ID deserves.
Your DIDs, CNAM included
Local DIDs from our NANPA-allocated inventory across US area codes — availability varies by rate center — with CNAM registration included. Existing numbers port in with no porting fees — 7 to 14 business days standard.
One vendor for PBX and carrier
When a call fails, there's no PBX host blaming the trunk provider and no trunk provider blaming the PBX. SIPNEX runs both layers and answers for both.
From extension count to dial tone.
Tell us the shape of it
Extension count, call volume, sites, and whether numbers are porting in or starting fresh. That's what sizes the instance and the quote — not a tier chart.
We provision the instance
A managed FreePBX instance on SIPNEX infrastructure, with our SIP trunks connected and registered before you ever log in.
Numbers and E911 go on
DIDs are provisioned to the instance with CNAM registered, ports submitted with no porting fees, and an E911 Registered Location on file for each site — available in the 50 US states.
You run the dial plan
You take FreePBX admin and build routes, IVRs, and queues your way — or hand us the configuration work. Either way, the platform and trunks stay on us.
SIPNEX hosting vs FreePBX on your own VPS.
| THE LAYER | SIPNEX FREEPBX HOSTING | DIY VPS + SEPARATE TRUNKS |
|---|---|---|
| The server | Provisioned and managed by SIPNEX | You build it, patch it, babysit it |
| SIP trunks | Connected before handoff, same vendor | Second provider, second ticket queue |
| Trunk pricing | Usage-based, no per-channel fees | Per-channel or per-trunk line items |
| DIDs and CNAM | Provisioned to the instance, CNAM included | Ordered elsewhere, pointed by hand |
| STIR/SHAKEN | A-level under our own SP-KI certificate | Whatever the trunk reseller passes down |
| E911 | Registered Location on file at turn-up | A checklist item you hope got done |
| When a call fails | One vendor owns PBX and carrier | PBX host and carrier blame each other |
Who this fits. And who it doesn't.
Teams that outgrew the closet server
You like FreePBX. You don't like being its sysadmin — the patches, the failed updates, the box nobody wants to touch. A managed instance keeps the control and retires the server. Deciding on a platform first? Compare options in our small business PBX guide.
Teams happy on cloud PBX
If you don't want a PBX admin interface at all — just working phones and someone else running everything — FreePBX hosting is more control than you need. That's SIPNEX hosted PBX.
Committed self-hosters
If running the box is the point, we won't talk you out of it — we'll carry the trunks under it instead. Wire your own FreePBX to SIPNEX with our SIP trunking for PBX service.
DIY builders wiring it themselves
Building your own instance and just need the trunk side done right? The registration, NAT, and codec settings are all documented step by step in our SIP trunk configuration guide.
Dialer operators
FreePBX is a PBX, not a predictive dialer — no pacing, no campaigns, no agent screens. We don't market this page for dialer workloads. Outbound operations belong on our VICIdial carrier service.
Still weighing platforms before you commit? The honest three-year comparison — licensing, management burden, and where each one bites — is in our 3CX vs FreePBX breakdown.
About FreePBX hosting with SIPNEX.
What is FreePBX hosting?
Are SIP trunks included with SIPNEX FreePBX hosting?
Do I keep admin access to my hosted FreePBX?
Can I move an existing FreePBX system to SIPNEX hosting?
Should I choose FreePBX hosting or SIPNEX hosted PBX?
Can I run VICIdial or an outbound dialer on hosted FreePBX?
Do I pay FreePBX software license fees on a hosted instance?
What does SIPNEX FreePBX hosting cost?
FreePBX control. Carrier accountability.
Tell us your extension count, your call volume, and whether numbers are porting in. We size the instance, connect the trunks, and hand you a FreePBX that's already passing calls. If you'd rather keep running your own box, our SIP trunking for PBX service carries the trunks under it instead.