Hello all.
After reading through the Marketplace subforum, it is clear several of us have been building tools to help partners look after a lot of 3CX systems. This is our hat in the ring. I will not compare Kestrel to anyone else — only describe what we built and why.
We are a 3CX partner (ZaheZone). Like many here, we needed a single place to see the systems we support: whether a host is up, what version it is on, where a number actually routes, and whether we are getting close to licensed simultaneous calls. We built that for our own fleet, then opened it to other partners.
Kestrel is partner SaaS. The partner organisation owns the account. End customers do not log in and they do not see the invoice. There is no agent on the PBX. It is a cloud poller over HTTPS to the 3CX Configuration API. A service principal is the preferred connection.
What we use it for today:
There is a read-only demo (no signup) if you want to click through the map and the fleet board:
https://app.kestrelpbx.com/demo
https://kestrelpbx.com
We would genuinely like feedback from people who support 3CX every day. What is missing for your shop? What would you not trust a third-party tool to touch? If you try the demo, tell us what is unclear or wrong.
After reading through the Marketplace subforum, it is clear several of us have been building tools to help partners look after a lot of 3CX systems. This is our hat in the ring. I will not compare Kestrel to anyone else — only describe what we built and why.
We are a 3CX partner (ZaheZone). Like many here, we needed a single place to see the systems we support: whether a host is up, what version it is on, where a number actually routes, and whether we are getting close to licensed simultaneous calls. We built that for our own fleet, then opened it to other partners.
Kestrel is partner SaaS. The partner organisation owns the account. End customers do not log in and they do not see the invoice. There is no agent on the PBX. It is a cloud poller over HTTPS to the 3CX Configuration API. A service principal is the preferred connection.
What we use it for today:
- Call-flow map — inbound path on a host as a picture: trunk → DID → IVR, queue, ring group, or extension. Filter business hours, after hours, and holidays. Open a queue or ring group to see members.
- Fleet board — up/down, hours mode, version, concurrent vs licensed SC, open alerts. The FQDN opens that host’s 3CX console when you need it.
- DID search — look up a number across the hosts you manage and see inbound rule, tenant, and host.
- Config drift / what changed — inbound, outbound, and group diffs since the last snapshot.
- Alerts — host down, stale poll, licence / peak SC. After-hours defaults at partner or per-host level.
- Maintenance — check for 3CX updates across the fleet, queue a backup, then install, with down alerts suppressed for the window.
- Multi-tenant view — host and company records where you run multi-company 3CX.
There is a read-only demo (no signup) if you want to click through the map and the fleet board:
We would genuinely like feedback from people who support 3CX every day. What is missing for your shop? What would you not trust a third-party tool to touch? If you try the demo, tell us what is unclear or wrong.
