SKYTALSKYTAL

Architecture

P2P where it actually works

SKYTAL is built around direct device interaction, with fallback infrastructure where reliability requires it. We do not claim full decentralization and we do not hide the server layer role in message and file delivery.

Calls

P2P calls with automatic relay fallback. A direct connection between devices is preferred; a protected relay is used when the route is unavailable.

Direct routeDeviceDevice
Primary scenario when the network allows a direct WebRTC connection.
Relay fallbackDeviceDeviceRelay
Automatic backup route when a direct connection is not possible.

Messages today

Messages are protected with end-to-end encryption. The server participates in delivering encrypted data but is not intended to receive message plaintext.

E2EE delivery layerDeviceDeviceInfrastructure
WebSocket is used for delivery hints; payload stays encrypted.

Files today

Attachments are transferred through the server media layer in encrypted form. Direct device-to-device file transfer is not claimed as a current feature.

Encrypted media layerDeviceDeviceInfrastructure

Roadmap

Now

  • P2P calls with relay fallback
  • 1:1 E2EE on Android
  • Encrypted message delivery
  • Encrypted file transfer through media layer
  • Invitation-based access

Direct P2P delivery for messages and files is the next architecture stage — not a current feature.

Security model