IPFS case study: 800,000 messages a month, secured for Swiss healthcare

Originally published as a case study by IPFS: Vereign & IPFS. The video below is a conversation between Georg Greve and the IPFS team recorded for the case study launch.

HIN, the provider of secure communication for Swiss healthcare, sends more than 800,000 verified messages every month using SEAL. To do that, every message is encrypted, broken into fragments, and distributed across an IPFS swarm operated by HIN and Vereign. Nothing is reassembled until it reaches the patient’s own device: tap a link, enter a code, read the message. The doctor receives proof of delivery the moment the patient decrypts the message on the other end. Patients never touch a certificate store, a portal, or an app install, and HIN reports near-zero support load since roll-out began.

The IPFS case study explains how this works in practice, including why the swarm is public but write-restricted, why fragment boundaries do not align with GCM blocks, and how the same delivery primitive now carries documents as well as email. It also names the operational edges honestly: garbage collection on a busy IPFS node is disruptive, and aggressive corporate firewalls still distrust IPFS unless headers are stripped on the patient-facing path. Running regulated traffic on IPFS at this scale is still rare, and the case study captures what that actually takes.

The video above is a deep dive into the SEAL architecture and the HIN deployment. For the broader platform picture, see Verimesh, the communication suite SEAL is part of. Questions or collaboration inquiries: reach out to the Vereign team.