securephone.co
Get a quote
SecurePhone deployment architecture

Start compact.
Scale with intent.

SecurePhone packages the communications stack into logical Core, Realtime, and Mail profiles. Run them together, isolate them across three nodes, or expand individual services as demand grows.

Compare profiles Review server requirements
A
COREControl and business systems
CONTROL
B
REALTIMEInteractive traffic
TRAFFIC
C
MAILPrivate mail boundary
PRIVATE
01One host or many02Logical profile isolation03External backups04Scale without replatforming
Deployment profiles

Choose the isolation
your operation needs.

These are supported starting architectures, not rigid ceilings. The architecture review aligns the profile with your workload and availability requirements.

01
CORERTMAIL

All-in-one appliance

Run Core, Realtime, and Mail on one appropriately sized dedicated server or VPS.

Best for pilots, private teams, and focused module deployments.
RECOMMENDED02
CORERTMAIL

Three-node standard

Separate Core, Realtime, and Mail profiles for clean operational and resource isolation.

Recommended for commercial operators and the complete platform.
03
CORERT × NDATA

Scale-out deployment

Add media, mail, database, and storage capacity without changing the product model.

Best for larger reseller networks and higher realtime traffic.
Three logical profiles

Separate by
operating behavior.

The profiles keep business control, latency-sensitive traffic, and private mail storage in clear operating boundaries while preserving one appliance product.

A

CORE

Control and business systems

Commerce Hub, licensing authority, customer administration, subscriptions, reseller operations, MDM, and primary application data.

B

REALTIME

Interactive traffic

Global Chat, SIP, TURN, media, and latency-sensitive services that benefit from independent scaling.

C

MAIL

Private mail boundary

KeyMail queues, mailboxes, delivery services, and storage on a profile sized around quota and retention.

Deployment workflow

From architecture
to supported operation.

Every deployment follows the same four-stage path, whether all profiles share one host or run across a scaled topology.

  1. 01

    Architecture review

    Confirm modules, active users, mailbox quotas, concurrent calls, VPN throughput, retention, and availability requirements.

  2. 02

    Prepare infrastructure

    Provision supported Ubuntu hosts, static public addressing, DNS, provider access, and an external backup destination.

  3. 03

    Preflight and install

    Validate DNS, reachability, TLS, ports, storage, and host prerequisites before signed appliance containers are installed.

  4. 04

    Harden and hand over

    Restrict administration, verify backups and monitoring, issue signed entitlements, and document supported operations.

Growth and availability

Scale the pressure point.

Add realtime or media capacity for call volume, mail nodes or object storage for retention, and dedicated database services or redundancy when the availability target requires it.

SCALE-OUTEXAMPLE
01COREControl plane
02RT × 3Media capacity
03MAIL × 2Storage + queues
04DATADedicated services
Plan the right starting point

Build your deployment quote.

Select modules, active users, infrastructure, and custom requirements in one customer-ready configuration.

Open the configurator