The fundamental difference
3CX's native multi-tenant capability is a hosting model — you put many small customers on one server you control. Sikurd is a management layer that sits across many separate 3CX servers, giving you one pane of glass for monitoring, alerts, and operational tasks.
Most MSPs end up needing both approaches for different clients. The question is what you use to manage the dedicated instances.
Feature comparison
| Capability | 3CX Instance Manager (native) | Sikurd |
|---|---|---|
| Manages multiple independent 3CX instances | Limited | Yes |
| Single dashboard across all client servers | No | Yes |
| Proactive monitoring & alerting | Basic | Yes |
| Mobile push alerts (iOS / Android) | No | Yes |
| Automatic service restart on failure | No | Yes |
| Works with dedicated client instances (CRM, M365, hotel) | Yes | Yes |
| Cross-instance reporting | No | Yes |
| PSA integrations (ConnectWise, Autotask, HaloPSA, Syncro) | No | Yes |
| MSP-focused workflows | No | Yes |
| Built into 3CX licensing | Yes | No |
Where 3CX's native tools fall short for MSPs
This is where you'll feel the gap if you're managing more than a handful of clients.
Multi-tenant mode is capped at small customers.3CX itself recommends dedicated instances for anything over ~10–15 users, or anything needing CRM, M365, Teams integration, or hotel features. MSPs with mid-market clients still need to manage many dedicated instances — and the native Instance Manager doesn't help much beyond inventory.
No native cross-instance view.Each 3CX server is managed on its own. There's no built-in single pane to monitor uptime, trunk status, or alerts across all the instances you operate.
Tenants can't have separate CRM integrations on multi-tenant.Per 3CX's own FAQ, CRM is a dedicated-instance feature only. So the moment a customer needs CRM, they need their own instance — and you need a way to manage it.
Limited delegation.System Owner / System Admin roles don't translate cleanly to MSP team structures with on-call rotations, escalation chains, or role-based access by client.
No proactive alerting that reaches you on mobile. The Partner Portal is an inventory tool, not an operations platform. A SIP trunk deregisters at 2am and you find out from a customer email at 9am.
Where 3CX Instance Manager wins
Being honest here builds trust — and it builds rankings.
- It's included in your 3CX license; no extra subscription.
- For pure consolidation of micro-SMB customers, it's the simplest path.
- Native integration means no third-party tool to learn or maintain.
Which should you choose?
- All clients are <10 users with basic needs: 3CX Multi-Tenant alone is probably enough.
- Mix of dedicated and shared instances: 3CX for the small ones, Sikurd to manage the dedicated ones.
- Mostly dedicated instances across many clients: Sikurd as your primary management layer.