FreePBX 16, 17 and FreePBX-based distributions: full editor (read + write). Distros built on FreePBX 16 or 17 work the same way, including PBXact, ClearlyIP, the community Incredible PBX, and OEM/whitelabel boxes. A PBX on FreePBX 14 or 15 that already has CFS keeps updating, but a new install needs 16 or newer. Self-hosted is the keyword. CFS installs over SSH as root, so hosted-only platforms where you don't get shell access (e.g. PBXact Cloud) aren't supported. VitalPBX 3 and 4: a read-only visualizer (see "Why is VitalPBX read-only?" below) that renders the full VitalPBX dial plan: every routable destination type, including IVRs, queues, ring groups, time conditions, and call flow control. The platform is detected at install. Vanilla Asterisk without one of these front-ends isn't supported. CFS draws what's configured in the PBX admin UI, not raw extensions.conf, but custom dial plan still shows up where your routing points at it: a FreePBX Custom Destination renders as a node with its description, target and return path, and the details panel shows the raw Asterisk dial plan it jumps into. A VitalPBX route into a custom context renders as its own node. Don't see your PBX? Email support@callflowstudio.io. We add platforms when there's demand.
No. CFS isn't a FreePBX module and isn't distributed through the FreePBX module store, so none of the commercial-module machinery applies to it. There's no deployment ID to register, no Sangoma account to link, and no entitlement to buy. It installs alongside your PBX at /cfstudio/ and doesn’t care whether the box is registered with anyone. A self-built FreePBX, a distribution rebuild, an OEM or whitelabel box, or one that was never registered and can't be, all work the same way. Nothing appears in Module Admin, and FreePBX module updates can't remove or break it. Your Call Flow Studio license is separate and handled by us directly.
On VitalPBX, Call Flow Studio is a first-class read-only visualizer. The graph, live status, time travel, call replay, export and sticky notes all work as they do on the FreePBX family. What differs is how changes get made. Call Flow Studio's editing is built on the FreePBX family's own configuration tools, and on VitalPBX, changes are made in the VitalPBX admin UI, where they've always been made. If editing becomes possible on VitalPBX in the future, we'll add it.
Yes. A 100-extension dial plan loads in about a second, and faster once it's warm. Larger plans take longer: a 500-extension test box loads in a few seconds. Live status stays accurate on installs carrying several hundred registered endpoints. If a dial plan is unusually large or routes back on itself, CFS renders as much of it as it safely can and tells you the diagram is partial, rather than spinning until the page times out. Size is also what hide-a-branch is for: collapse everything downstream of a node and the diagram shrinks to the path you actually care about, with nothing deleted and everything one click from coming back.
CFS doesn't write SQL into your PBX's database. When you save an IVR, queue, or ring group, it calls FreePBX's own module functions, the same code FreePBX runs when you press Submit in its admin screens, and when you click Apply Config, it runs the same fwconsole reload you'd run yourself. Undo and redo go back through those same functions. Every change CFS makes is an ordinary FreePBX change, then: reversible, auditable, and visible in whatever admin UI you already use. If someone changed the same thing in FreePBX after you opened the call flow, saving stops and asks you to reload instead of writing over their change. Point it at a test DID first if you want to build confidence. On FreePBX you can also build a new call flow as a draft (Beta): nothing is written to the PBX until you click Build, and if building a piece fails, Publish removes the pieces it already built.
Undo isn't a feature in your PBX admin UI. It is in Call Flow Studio. Ctrl-Z reverts the most recent change in the call flow you're viewing; Ctrl-Y redoes. It's a working-session tool: undo reaches back over what you've just been doing in that call flow, not a change from last week. Apply Config surfaces automatically after an undo so the correction goes live the moment you're ready, and that holds even after you've already applied. The Activity Log tab is the record rather than a second undo: who changed what, and when, across every dial plan. (Undo covers rewires and renames, IVR and Dynamic Route entries, details-panel fields, the settings dialogs, recordings and voicemail greetings. Call flow control toggles are logged but aren't undoable. They have their own confirmation prompt. Node creation and time-group edits don't show in the Activity Log tab yet, though the audit log on the PBX records every change.)
No. Your dial plan, extensions, call recordings and call records never leave your server; CFS has no way to send them and never asks for them. Here is everything that does reach our server, and when:
cfs upgrade.cfs release-license: the license key ID and the fingerprint.Installing or upgrading also downloads the release from us, plus a PHP component some systems need, and checks that our license server is reachable. Once it’s installed, nothing else comes to us. The app’s pages load no analytics, no CDN and no external JavaScript, so nothing in your browser phones home. The PBX does need a route out to us for the license check, so a box with no route out isn’t a fit.
The only other service the PBX talks to is the text-to-speech one you choose, and only once it has a key for it. When someone saves an ElevenLabs or OpenAI key, types a greeting or recording, plays a voice sample or transcribes a recording, the PBX sends that service the text and voice, or the recording’s audio, on your own account. None of it passes through us. A key saved in CFS is stored encrypted, and CFS never shows anyone more than its last four characters. Privacy policy →
Everything runs on your own server. There's no cloud component, no CDN, and no third-party JavaScript; the whole app is served from your PBX, so your dial plan never leaves it.
CFS also doesn't write SQL into your PBX's database. Edits go through FreePBX's own module functions, the same code FreePBX runs when you press Submit in its admin screens, and undo and redo take the same route.
A CFS login isn't a PBX admin login. No CFS user, whatever their role, can change your trunks or system settings, or delete an extension. The worst a stolen admin or technician account can do is change call routing, including sending calls to outside numbers over your trunks. On FreePBX it can also change most module and extension settings (caller ID and emergency caller ID, call recording, Follow Me, DISA and conference PINs), add extensions, and replace recordings and voicemail greetings. It gets only as far as that login was allowed: a read-only user can change none of it, and an admin can hold each technician to the modules they need.
Admins can require two-step sign-in by role, with an authenticator app or emailed codes. A failed CFS sign-in is written to the same log your PBX’s fail2ban already watches for its own admin login, so the ban rules you have cover CFS too. Text-to-speech keys saved in CFS are stored encrypted, and no login, admin included, can read one back past its last four characters. Every change is written to the audit log on the PBX with who made it and when.
No release ships unless it passes an automated security suite. If the suite fails, the build stops and there's no tarball to publish. It covers authentication, authorization, injection and session handling. Once a release is out, the same suite runs again against every PBX in our test lab.
If you find something we missed, email support@callflowstudio.io. It goes straight to the developer.
No. CFS runs its own user system, completely separate from your PBX admin auth. Three roles: admins manage everything, technicians edit dial plans and can jump straight into your PBX admin for anything outside CFS's scope, in whichever modules an admin grants them, and users get read-only access: pan, zoom, search, and reload the graph but never edit. Hand out CFS logins to junior techs, customers, or end users without giving them PBX admin access. The shareable URL is https://<PBX_URL>/cfstudio. Pair it with a user login when you want to walk someone through a call flow on the phone while making changes live.
Call Flow Studio is served from your PBX at https://<PBX_URL>/cfstudio, on the same web server your PBX admin already uses. It opens no new ports and exposes nothing that wasn't reachable before, so a CFS login reaches it exactly the way it reaches your PBX. If your PBX is internet-facing, a remote tech or customer can sign in from anywhere; if it's on-prem behind a VPN or firewall, as many are, CFS is reachable to whoever's already on that network. Either way it's a separate read-only login with no PBX admin access, so handing someone a view never widens what's exposed.
Yes, and it stays free. On the FreePBX family, the complete read-only visualizer is yours for good with no credit card and no expiry: every dial plan and module, live registration and queue status, time travel, call replay, export, sticky notes. Editing is the optional part, and you get it for your first 30 days. On VitalPBX, Call Flow Studio is read-only for everyone (see above), so the free tier is a visualizer for your first two tenants and the license opens every tenant. One Call Flow Studio license ($79, one-time and per-PBX) keeps the full experience. No paywall and no locked-out screen. A purchased license doesn’t expire. When a trial ends without one, the install drops back to the free tier, and we never delete your data.
On the old server, run sudo cfs release-license from a shell. That frees the license, and the old box keeps working as the free read-only visualizer. Then install CFS on the new server, go to Admin → License, and paste your original activation code. It binds to the new machine right away; you don't need a new code. Move it as often as you need to. If the old PBX is dead and you can't run the release on it, email support@callflowstudio.io and we'll release it for you. Your license, your hardware. Full steps →
Call Flow Studio is the actively-developed, commercial successor to dpviz, by the same developer. FreePBX has no native call-flow visualizer, and dpviz, the free community module, filled that gap first. It draws your dial plan as a graph with live status, time simulation and basic node creation, and it's lightly maintained, with compatibility updates. Call Flow Studio is what those years of feature requests turned into: forward-building as the main way you work, drafts you publish when they're ready (Beta), templates, undo with change history, call replay, sticky notes, and VitalPBX support. Its visualizer is free for good on the FreePBX family. Full comparison →
CFS is focused: dial-plan visualization, live status, and editing. These are intentionally out of scope, and well-served by other tools: