Run Fronic's encrypted backbone under your own roof.
The Fronic app is free. The signaling server behind it — the service that registers devices and sets up calls and messages without ever holding a key that could open them — is the one part of Fronic available as a commercial, self-hosted license for organizations that want their own instance, under their own infrastructure control.
A routing service, not a listening one.
A licensed instance runs on infrastructure you control, under your own domain, and never holds a key capable of decrypting a call or a message — the same architecture Fronic's own public instance runs on.
Your infrastructure
Deployed on hardware or cloud capacity you choose, under your own domain and certificate. Fronic never touches it once it's running.
Nothing to decrypt
Calls and messages stay end-to-end encrypted between devices. Your instance routes and relays; it never holds a key that could open either.
Built for teams
A fit for organizations — internal comms, regulated industries, or anyone replacing a phone system with an encrypted one they run themselves — that need calling and messaging without a third party able to listen in.
Nothing here is secret. It's the build, stated plainly.
Fronic's security rests on public, well-reviewed primitives — combined so that breaking any single one isn't enough.
- Call protocol
- FSCP-v1 — a Noise XX-derived mutual handshake. Both phones authenticate each other directly; the server sets the call up but never holds a key that can open it.
- Key agreement
- X25519 + ML-KEM-768, mixed through HKDF-SHA256. Classical and post-quantum key exchange combined — recorded traffic stays sealed unless an attacker breaks both.
- Identity signatures
- Ed25519 + ML-DSA-65. Each side signs the whole handshake transcript twice; altering any earlier byte invalidates both signatures.
- Voice encryption
- ChaCha20-Poly1305, per audio frame. A frame tampered with in flight is dropped, not played.
- Signaling transport
- TLS 1.3, pinned certificate. The app trusts exactly one certificate, built into it — a tampered device or network trust store can't substitute another.
- Media path
- Direct UDP, encrypted relay fallback. The relay forwards sealed frames it cannot read.
Tell us about your deployment.
Fill in the fields below and Send emails it straight to contact@fronic.net — nothing stored beyond that one message.