Keep the PBX on site. Keep the design modern.
Purpose-built Yeastar hardware for customers whose operating model calls for an on-premises phone system, with Australian solution guidance and partner support from TeraFi.
Choose on-premises for a reason.
An appliance can be worth assessing when a customer has a clear on-site requirement, established local IT ownership, particular network conditions or a preference for dedicated PBX hardware. It should still be evaluated against growth, resilience, remote-user needs, integrations and lifecycle ownership.
- Local infrastructure requirement
- On-site administrative ownership
- Existing telephony interfaces
- Defined resilience approach
- Remote and mobile users
- Support and replacement planning
Size the appliance around users, calls and interfaces.
The current family runs from the compact P520 through P550, P560 and P570. Capacity, expansion and interface options vary, so model selection should follow discovery rather than a headline user count.
Compact requirements
A current entry model for smaller on-premises requirements. Availability is subject to regional sales policy.
Established SME deployments
A step up in users, concurrent calls and supported telephony interfaces for suitable environments.
Expandable capacity
Supports capacity and interface expansion options for more demanding on-site designs.
Larger appliance deployments
The highest-capacity current appliance model, with broader expansion options for qualified designs.
Model specifications, plans, modules and regional availability can change. TeraFi confirms the current datasheet and Australian supply position before quoting.
Validate the operating model before installation.
Owning the appliance is only one part of owning the service.
Define infrastructure ownership
Assign installation, network readiness, administrator access and physical-site responsibilities.
Map every dependency
Confirm phones, SIP services, analogue devices, gateways and business integrations.
Plan lifecycle and resilience
Document backup, updates, monitoring, recovery, spares and support escalation.
Appliance is one of three routes.
Compare it with P-Series Cloud Edition for a managed cloud pathway and P-Series Software Edition for a supported self-hosted environment.
The right route follows operational ownership—not a generic feature checklist.
Take an on-premises opportunity through proper discovery.
Bring TeraFi the user count, concurrent-call need, interfaces, sites, resilience expectations and support model. We will help validate the current appliance pathway before you quote.
Fact-checked on 11 August 2026 against Yeastar’s current Appliance Edition information.