Released in v2.0.15-Stable

Pod-to-Pod

Send files straight from one trusted Pod to another. Pod-to-Pod helps people and businesses exchange data without dropping every file into another shared cloud folder.

Direct sharing

Send to a trusted Pod, not just another inbox.

Email addresses change. Inboxes get messy. Links get forwarded. Pod-to-Pod is designed around a stable PodID, so a trusted transfer relationship can continue even if someone changes their email address.

The plain-English goal is simple: get the right file to the right pod with fewer standing copies left behind on other services.

Less cloud baggage

Direct pod-to-pod exchange means less cloud custody, fewer forgotten copies, and a smaller target than traditional shared file links.

Transfer flow

Address, verify, transfer.

The desktop client already frames Pod-to-Pod around receiver Pod IDs, generated transfer tickets, a shared 4-digit safety code, and encrypted background transfer.

1

Sender Pod

The sender chooses a file and addresses the transfer to the receiver’s PodID.

2

Safety Check

Both sides compare a shared 4-digit safety code before accepting the transfer.

3

Receiver Pod

The receiver accepts the ticket and the encrypted background transfer completes between pods.

What this enables

For people and businesses that need data without cloud sprawl.

ID

Stable PodID

The relationship can be anchored to a PodID rather than an email address, so communication can survive email changes.

P2P

Peer-to-peer exchange

Sensitive data can move between pods without becoming a standing copy in a central PokoPod cloud database.

GM

Ghost Mode and trust

Trusted sender controls and non-discoverable modes can help users decide who is allowed to initiate transfers.

Privacy posture

Designed to reduce server-side exposure.

Traditional file sharing often leaves data on a service provider’s server, inside a company inbox, or in a cloud link that can be forwarded, indexed, breached, or forgotten. Pod-to-Pod aims to reduce that exposure by making the pod itself the destination.

No central file storeThe design goal is no persistent PokoPod-hosted copy of the transferred file.
No email dependencyThe PodID can remain stable even if the user changes email address.
Direct relationshipBusinesses and users can exchange data pod-to-pod instead of through a central database.