Companies Private Server

Private Server Mode (Company)

Private Server mode lets a company run the relay inside its own infrastructure, keeping control over who can connect, where traffic flows, and how data is handled. The phone still delivers messages; you control the relay.

What You Control

Network

Run on LAN/VPN/VPC, behind firewall rules and your own TLS termination.

Access

Issue/rotate API keys, restrict clients, enforce rate limits and allowlists.

Data Flow

Browser/app → your relay → your phone. You decide retention and logging.

Operations

Monitoring, backups, upgrades, incident response: all on your side.

Why Companies Use This

Compliance: keep traffic in your network boundary.
Control: you decide who can send and to whom.
Reliability: run close to your systems; integrate with your alerting/automation.
Security: lock down via VPN + IP allowlists + key rotation.

The public API for sending remains the same: HTTPS API.

Suggested Deployment Checklist (High-Level)

Put the relay behind HTTPS (reverse proxy) and restrict inbound network access.
Use IP allowlists for server endpoints if possible.
Store secrets securely (vault/secret manager); rotate keys on staff changes.
Set rate limits for all senders (prevents abuse and protects the phone).
Define retention: how long queued content can exist if the phone is offline.

If you want an “AI notifications gateway” for many users, build a server-side notification manager that owns the API key and applies policy before sending.

For day-to-day usage (sending and status), use: HTTP API Examples.

For the sender UI, use: pChat.

Private Server Mode (Company)

What You Control

Why Companies Use This

Suggested Deployment Checklist (High-Level)

Next