PChannel Desktop is in alpha. For controlled evaluation.Release information
PChannel.
TECHNICAL / SMFX

Clear structure.
Explicit evidence.

SMFX (Secure Message and File Exchange Protocol) provides the model for durable, structured, authenticated business communication.

EXPLORE / CUSTODY

PChannel vs. Email

Where does the continuing correspondence record live, and whose policies govern its copies?

The Question of Custody ↗
01 / THE CONNECTION

Desktop to Desktop.
Through the Relay.

PChannel DesktopParticipant node
HTTPS
RelayTemporary custody
HTTPS
HTTPS
PChannel DesktopParticipant node
PChannel DesktopParticipant node
Correspondence stays with the participants. The Relay holds packages temporarily for recipient retrieval. The Relay listens for update requests from every node. All connections to the Relay are initiated as outgoing from the Desktop node. No listener setup is required at the node.
02 / COMPONENTS
01

Desktop

Local correspondence, protected signing identity, participant verification, and synchronization.

02

Relay

Temporary custody of message packages between endpoints. Alpha content is not end-to-end encrypted or cryptographically concealed from the Relay.

bcr1.pchannel.cc
03

Activation

Authorizes one installation to enroll with the Relay.

activate.pchannel.cc
What does the Relay know?

The Relay handles transport and custody metadata and opaque payloads. It does not manage company membership or interpret business correspondence. Alpha content is not end-to-end encrypted or cryptographically concealed from the Relay. Current custody is bounded to a maximum of 48 hours.

What does “Delivered” mean?

A signed recipient-custody receipt satisfies the sender's local delivery obligation. It does not establish human reading, business acceptance, payment, or fulfillment. Relay acceptance alone is not delivery.

How is identity handled?

Installation activation and customer registration are separate from Channel membership. To join a Channel, open its invitation and enter the passphrase shared separately by the inviter. The apps authenticate using SPAKE2 and complete enrollment automatically, with completion notifications on both installations. No manual approval step is required. This invitation authentication does not provide end-to-end encryption of Message content. See the start and join guide.

Is SMFX published independently?

SMFX stands for Secure Message and File Exchange Protocol. Its draft proposal will be hosted independently at smfx.dev.

Claims we do not make.

No suitability for CUI, production federation, organization PKI, read receipts, business acceptance, or compliance certification is claimed for the current alpha.

See planned capabilities ↗