Skip to content
Home / Solutions / Tech Lead
For Technical Leaders

One platform, built as one system

Voice, infrastructure, security, and apps, built by one team instead of stitched together from four vendor roadmaps. The architecture, resilience, and openness to run workloads that actually matter.

Architecture

Four layers, one team, one release

PBXware runs the calls. SERVERware hosts it. sipPROT protects it. gloCOM is what your users open. Built together and versioned together, so there is no integration layer for you to own.

  1. 01

    PBXware · core

    Multi-tenant from the ground up, with per-tenant isolation. Routing, IVR, queues, AI and CRM run through the core rather than beside it.

  2. 02

    SERVERware · infrastructure

    KVM and LXC virtualization on OpenZFS. Purpose-built to host this platform rather than adapted from general-purpose virtualization.

  3. 03

    sipPROT · security

    Wraps the whole core, not one tenant. Once added, it protects every host it runs on.

  4. 04

    gloCOM · apps

    Desktop, web, mobile and an embedded Teams app, built against the same API your integrations use.

Running it day to day

What your team deals with after go-live

Not the architecture - the day-to-day reality of isolation, security, support, and the interfaces your team actually touches.

PBXware is multi-tenant by design, with tenant creation, policies and updates managed centrally

sipPROT covers the whole core rather than one tenant, protecting every host it runs on

17,000 requests a year, 97% inside SLA, under 30 minutes to first response, from the team that builds the product

REST API v2, Event Publisher, LDAP/AD and SSO, 11+ CRMs, all documented, with an MCP server for PBXware coming soon

WatchWhy the internet is the Wild West without sipPROT
When something fails

What happens next depends on the tier

“Resilient” isn't an answer. What matters is which component can fail, what takes over, and whether anyone has to intervene - and that changes depending on which tier you deploy.

What each tier does when a server goes

  • Virtualize - one server, running PBXware and other workloads in isolated virtual environments. The trade-off: if it fails, that deployment is down until it's back, so it fits smaller or non-critical deployments that don't need failover yet.
  • Mirror - two servers replicating in real time. One fails, the other takes over automatically.
  • Scale - storage and processing separated onto dedicated servers, so load and failure are spread rather than concentrated.
  • Capacity is added by attaching another server, with no downtime for existing tenants.

Data and security posture

  • OpenZFS with disk redundancy, hot spares and snapshots
  • Backup, recovery and disaster recovery provided by the platform
  • sipPROT: live SIP monitoring, dynamic IP blocking with timed release, Geo-IP filtering, INVITE rate limiting
  • 99.93% uptime SLA for Bicom Managed Hosting
What your team can build on

Documented interfaces, not a support ticket

Provisioning, automation and integration should be things your engineers do themselves. Everything below is documented and available without a waitlist.

Extensions, users, trunks and system management, programmatically.
100+ endpoints with full docs.

Live call and SMS events streamed as they happen, with no polling.

Coming soon for PBXware, so your team can build integrations against API v2 with an AI coding assistant.

LDAP/Active Directory, SSO, 11+ CRMs running in parallel and configurable per tenant and per user.

Compliance is handled at platform level rather than left to each deployment: STIR/SHAKEN, Ray Baum's Act, Kari's Law, Alyssa's Law, E.164, plus configurable retention and archiving.

REST API v2200 OK
Event Publishercall.answered
MCPconnected
Migration

You don't run the migration. We do.

The question that decides most technical evaluations is not whether the platform is good - it is what happens to the base you already have. Moving customers onto a new platform is our work, not a toolkit we hand you with a deadline.

  1. 01

    We do it for you

    Our team works from your existing system and carries out the migration. You are not staffing a project or writing conversion scripts.

  2. 02

    One point of contact

    A single coordinator owns the schedule and the communication, so you are never chasing status across departments.

  3. 03

    Your customers stay up

    The process is built around continuity. Your customers should not experience the migration as an outage.

Proof

What other technical teams say

"Bicom's platform, with its open APIs, helps our team and our partners connect and customize solutions without difficulty."

JGJean-Pierre GaertnerAGST  ·  10M+ calls a day worldwide

"We have tried many different platforms over the years but PBXware just works best - the features, ease of programming, and support of the product are why we prefer it over other platforms available."

TRTeresa R.Lead Programmer, (source: SourceForge)

"Always innovative with a forward-looking mindset… always prepared to listen to their partners, which allows us to grow together."

CNCon NakosCloud Kinnekt
1 / 3

Don't take our word for it

You can get into a live system and read the API documentation without speaking to anyone first.