securephone.co
Get support
SECUREPHONE HELP CENTER

Operate the platform.
Secure every device.

Installation, licensing, administration, device enrollment, service readiness, and recovery guidance—checked against the SecurePhone appliance contract and the live public sandbox.

11 practical guidesOperator + device pathsEN / ES
Choose your path

Show only the guidance that applies.

Appliance operators see installation, licensing, and service operations. Device users see enrollment and application activation.

Start here5 minAppliance contract

Understand the SecurePhone appliance

What runs inside a customer deployment, what remains at SecurePhone, and how an all-in-one installation differs from a three-node layout.

Updated
01

The customer owns the runtime

A SecurePhone appliance has its own administrator and reseller panel, customer portal, device-management API, databases, XMPP service, and the licensed realtime and mail components selected for that deployment. Its customer data and service authority stay on the customer's infrastructure.

The appliance contacts api.securephone.co for signed licensing, entitled release manifests, and content-free health reporting. It does not require an OMEMO.global or HardenedOS panel, account, domain, or signing key to operate.

02

Choose the deployment shape

  • Complete appliance is the recommended default. It installs every licensed component on one server.
  • A three-node deployment separates core, realtime, and mail into virtual machines. It is one platform split by role, not three appliance licences or three physical servers.
  • The evaluation minimum is 8 vCPU, 16 GB RAM, and 250 GB of storage. A production all-in-one starting point is 16 vCPU, 32 GB RAM, and 1 TB NVMe.