Infrastructure,
built for communications
SERVERware is virtualization built specifically to host communications - scalable, resilient, geo-redundant, and built to stay up when it actually matters. It's included with every hosted deployment on our private servers, and bundled into on-premise packages too.
Communications and infrastructure, from one partner
Bicom Systems does not only provide the communications platform. It also builds the infrastructure technology that runs, protects and scales it - which is why the pieces fit together without you doing the integration work.
- Purpose-built for communications - The infrastructure is designed to host voice, not adapted from general-purpose virtualization.
- Scalable infrastructure path - Start on a single host and move to mirrored or clustered infrastructure without changing platform.
- Observability and resiliency - Monitor CPU, memory, storage and call activity from one dashboard, with disk redundancy, hot spares and snapshots protecting your data.
- Fault tolerance and redundancy - On Mirror and Scale, real-time replication, host redundancy and automatic VPS failover keep service running when a host fails.
- Real-time threat detection - Watches live SIP traffic and spots attacks as they happen.
- Automatic blocking - Blocks offending IPs automatically, without anyone stepping in.
- Access control - Allow and deny lists decide who can reach your system.
- Protocol coverage - Protection extends to TLS, WSS and WS connections.
- Integrated deployment - PBXware instances are provisioned from the same console that manages the hosts they run on.
- One technology ecosystem - Same vendor, same release cycle, same support desk - no integration layer for you to own.
- Call statistics in SERVERware - Call statistics collected from PBXware are displayed on the SERVERware dashboard and statistics page.
- Integrated snapshots - Updating PBXware automatically creates a snapshot in SERVERware.
Virtualize. Mirror. Scale. Expand.
SERVERware scales in three tiers, from a single host to a fully redundant, clustered deployment - then expands further from there by adding hosts as your needs grow. Every tier shares the same virtualization, storage, and management foundation - what changes is the level of redundancy and scale.
KVM
LXC
VPS
Virtualize
Single-host. Run PBXware in isolated virtual environments.
Mirror
Resilient production with mirrored hosts and real-time failover.
Scale
Scalable production with dedicated storage and processing hosts.
Expand
Add processing or storage hosts as infrastructure requirements increase.
Core functionalities
KVM, LXC, VPS management, resource allocation, virtual networks, OCI images.
OpenZFS, disk redundancy, hot spares, storage monitoring, snapshots, backup & recovery.
Real-time replication, host redundancy, failover, fault-tolerant storage.
Dedicated processing hosts, shared storage, additional compute, horizontal scaling.
Every capability, side by side, across all three tiers:
| Capability | Description | Virtualize | Mirror | Scale |
|---|---|---|---|---|
| Deployment architecture | ||||
| Primary use case | Intended infrastructure deployment model | Simple virtualization | Resilient production | Scalable production |
| Architecture | Underlying SERVERware architecture | Standalone | Mirror | Cluster |
| Infrastructure model | How compute and storage resources are organized | Single host | Mirrored hosts | Dedicated storage & processing |
| High availability | Infrastructure redundancy and failover capability | - | ✓ | ✓ |
| Horizontal scalability | Scale infrastructure by adding additional hosts | - | - | ✓ |
| Virtualization foundation | ||||
| VPS virtualization | Create and run isolated virtual server workloads | ✓ | ✓ | ✓ |
| KVM & LXC support | Full virtual machines and lightweight containers | ✓ | ✓ | ✓ |
| Centralized management | Centralized infrastructure and workload management | ✓ | ✓ | ✓ |
| Resource allocation | CPU, memory and storage allocation | ✓ | ✓ | ✓ |
| Virtual networking | Virtual network management | ✓ | ✓ | ✓ |
| Templates & OCI images | Template and image-based deployment | ✓ | ✓ | ✓ |
| Storage & data protection | ||||
| OpenZFS storage | ZFS-based storage with data-integrity capabilities | ✓ | ✓ | ✓ |
| Disk redundancy | Protection against individual disk failure | ✓ | ✓ | ✓ |
| Storage expansion | Expand storage as requirements grow | ✓ | ✓ | ✓ |
| Hot spare support | Spare disk capability for recovery | ✓ | ✓ | ✓ |
| Storage health monitoring | Monitor storage and disk health | ✓ | ✓ | ✓ |
| VPS snapshots | Point-in-time workload snapshots | ✓ | ✓ | ✓ |
| VPS backup & recovery | Backup and restore virtual workloads | ✓ | ✓ | ✓ |
| High availability & resilience | ||||
| Real-time data replication | Replicate data between redundant SERVERware hosts | - | ✓ | ✓ |
| Host redundancy | Protect against infrastructure host failure | - | ✓ | ✓ |
| VPS failover | Recover workloads following infrastructure failure | - | ✓ | ✓ |
| Redundant storage layer | Maintain resilient storage infrastructure | - | ✓ | ✓ |
| Dedicated storage hosts | Separate storage from workload processing | - | - | ✓ |
| Scalability & performance | ||||
| Dedicated processing hosts | Run workloads on dedicated processing infrastructure | - | - | ✓ |
| Shared storage architecture | Processing hosts access the resilient storage layer | - | - | ✓ |
| Additional processing capacity | Increase capacity by adding processing hosts | - | - | ✓ |
| Independent compute scaling | Expand processing independently of storage | - | - | ✓ |
| Horizontal infrastructure scaling | Expand infrastructure through additional hosts | - | - | ✓ |
| Business continuity | ||||
| Backup Host | Dedicated backup infrastructure | Optional | Optional | Optional |
| Geo-Redundancy | Secondary geographically separated SERVERware environment | Optional | Optional | Optional |
| Multi-site resilience | Protection against loss of the primary infrastructure location | Optional | Optional | Optional |
Where it runs doesn't
change what it does
The tiers, the failover behavior and the storage integrity don't change with the address or the operator. Run your business in the cloud or on hardware you own; keep it in-house or hand it to our hosting team. The engineering underneath is the same in every combination - what changes is who gets the 3am alert.
When voice goes down, customers leave
For a service provider, reliability isn't a feature - it's the business. Every minute of downtime is a support storm and a reason for a customer to look elsewhere. SERVERware is designed to make outages a non-event: redundancy, failover, and replication already in place, so a hardware failure never becomes a customer-facing one.
Spin up PBXs and VPSs with a click
- Deploy isolated VPS instances and PBXware in one click, using KVM or LXC
- Partition resources into custom spaces for optimal performance per workload
- Use OCI images from third-party sources to extend your offering
- Expand by adding remote processing hosts to scale the cluster across locations
- NVMe/TCP for higher performance and lower latency, with an intuitive management GUI
- Built-in observability with Prometheus metrics and Grafana dashboards, giving real-time insight into resource and process consumption across the cluster and VPSs
Built to keep running
- 01
OpenZFS data integrity
Flexible storage expansion, disk redundancy, hot sparing, and continuous health monitoring.
- 02
Storage failover
Shared storage fails over to a mirrored host, protecting data and integrity.
- 03
VPS failover
VPSs move automatically from a failed host to a healthy one, reducing operational risk.
Disaster-proof by design
Extend SERVERware resilience across geographically separated locations, and prepare communications infrastructure for major site-level failures.
Geo-Redundancy
A secondary, geographically separated SERVERware environment, kept in sync with the primary site for true geo-redundancy and no data loss.
Remote recovery
Integrated DNS repoints records quickly, so service resumes at the secondary site on time - even in a disaster-recovery scenario.
Multi-site resilience
Protection against the loss of the primary infrastructure location, not just a single host.
Backup infrastructure
Dedicated backup hosts, kept separate from live production workloads.
What is new in SERVERware
A walkthrough of the SERVERware 5.1 and sipPROT updates: performance improvements, smarter monitoring, sharper security alerts and better visibility into the system.

"SERVERware is really a solution that's going to make a difference. If you want to do failovers, you need extra solutions on the side. Here it's all packaged, all in one."
Jean-Pierre Gaertner · AGST