Skip to content

Deployment

ChannelX is designed to run in environments you control. This page introduces the main deployment approaches at a conceptual level: a self-hosted installation, ISO-based provisioning, and integrating Nexus UC so voice is part of the deployment from the start.

Self-hosted deployment

A self-hosted deployment puts ChannelX on infrastructure you own and manage — whether that's your own servers or your own cloud environment. The appeal is control: your data stays within your boundary, you decide how the system is secured and networked, and you set the maintenance and update schedule.

With that control comes responsibility. In a self-hosted model your team handles provisioning, backups, monitoring, security hardening, and certificate management (for example, the SSL setup described in the Help Center section applies here too). Planning capacity, access controls, and a recovery strategy up front is what keeps a self-hosted environment healthy over time.

ISO-based deployment workflows

For environments that need a repeatable, self-contained install, an ISO-based workflow packages the system into a bootable image. Conceptually, this means the platform and its dependencies are delivered as a single image that can be provisioned onto a machine in a consistent way.

The advantages of this approach are repeatability and predictability:

  • Consistency — each install starts from the same known image, reducing configuration drift between environments.
  • Self-contained provisioning — the image carries what's needed to stand up the system, which suits isolated or on-premises networks.
  • Repeatable rollouts — the same image can be used to deploy multiple environments in a uniform way.

This style of deployment fits organizations that value tightly controlled, reproducible builds over ad-hoc installation.

Nexus UC deployment integration

When voice is part of your rollout, the deployment also needs to account for Nexus UC, Localcom's unified-communications and PBX platform. Integrating it at deployment time means voice calls can flow into ChannelX as conversations from day one, rather than being bolted on later.

At a conceptual level, this involves making sure the voice platform and ChannelX are provisioned together and able to communicate, so that calls — and, where Localcom AI is enabled, their transcripts, sentiment, and summaries — surface in the unified inbox. The end state is a single environment that handles both digital and voice channels.

Confirm specifics with the Localcom infrastructure team

This page is intentionally conceptual. Specific deployment procedures, system requirements, network and security configuration, ISO build steps, and any credentials must be confirmed with the Localcom infrastructure team. Do not assume specific commands, addresses, version numbers, or figures without checking with them first.