Vereign: Enabling Secure and Verifiable Healthcare Communication

Vereign AG is a Swiss-Bulgarian digital authenticity company headquartered in Zug, Switzerland, with its engineering office in Sofia, Bulgaria. Founded on the principle that digital communication should be as trustworthy as face-to-face interaction, Vereign builds infrastructure that makes digital identity, data integrity, and communication provably authentic by default, without delegating that trust to a third party.

The company's SEAL system processes over 800,000 secure healthcare interactions per month across the Swiss healthcare ecosystem through HIN (Health Info Net AG). Stargate - the full decentralized trust platform - is now entering production as the Certificate Authority for HIN, replacing 30-year-old gateway infrastructure with a cryptographic identity mesh.

Vereign joined the DHI Cluster in 2025 and has quickly become an active part of the community.

In this interview, we spoke with Georg C. F. Greve, CEO and Co-Founder of Vereign, during his visit to our office in Bulgaria, to discuss the company’s vision, technology, and the role of trust in the future of healthcare.

How would you describe your company to someone who has never heard of it? What inspired you to create it?

Every digital interaction in healthcare depends on trust. Not the vague, hope-for-the-best kind, but the kind where you can actually verify that the message came from the right person, reached the right recipient, and was not altered in transit.

The problem is that today's digital infrastructure delegates that verification to third parties. Certificate authorities, identity providers, platform operators - all of them hold security on your behalf. Every one of them is a single point of failure that can be compromised, coerced, or simply shut down. Let's Encrypt alone now holds around 60% of all TLS certificates on the web: A US institution whose operational failure would take most of the internet's transport security with it.

Vereign builds the infrastructure that puts trust authority back at the endpoints themselves. Not in an intermediary. Each organization maintains its own cryptographic identity. Trust between institutions is verified directly and mathematically, without a central broker.

The inspiration was watching the same structural failure repeat for 25+ years. Centralization enables surveillance. Surveillance degrades the fabric of communication. And every generation of technology that promised to fix it ended up recreating the same dependency on the same kind of intermediary. We decided to build the version that actually breaks that chain.

What is the main need or problem you address through your products or services, and who are the main users or beneficiaries of your technology?

The structural problem with healthcare communication is that sensitive information - diagnoses, prescriptions, referrals, test results - needs to travel between people and institutions that do not share a common IT environment. A GP's practice system does not talk to the hospital's. The hospital's system does not talk to the specialist clinic's. And none of them can reach the patient directly without either exposing data to a platform provider or asking the patient to install software.

SEAL solves the patient half of this problem. Stargate solves the institutional half. SEAL delivers encrypted messages to any patient via any browser on any device: zero installation, zero accounts, zero certificates required on the recipient's side. Stargate provides the decentralized identity infrastructure that lets institutions verify each other without a shared certificate authority.

The immediate beneficiaries are the healthcare professionals in Switzerland using the HIN network, and the patients they communicate with. But the architecture is sector-agnostic. Any regulated environment where trust crosses institutional boundaries has the same structural problem.

Tell us about your main product or solution. What makes it innovative, and how is it changing the reality of healthcare?

The most useful frame for understanding SEAL is what it does NOT require. It does not require the recipient to install software. It does not require pre-exchanged certificates. It does not require a shared account on a platform.

A doctor sends a message through their existing email system. SEAL intercepts it, encrypts each part individually using AES-GCM-256, fragments the encrypted content, and distributes fragments across a distributed storage network. The recipient gets a link, opens it in their browser, and the message reassembles and decrypts on their device. No single server ever holds the complete message.

That is not a minor improvement on S/MIME or PGP. It is a fundamentally different architecture - one that eliminates the installation barrier that has kept secure healthcare communication locked inside closed networks for 30+ years.

SEAL processes over 800,000 of these interactions per month across the Swiss healthcare ecosystem. The growth over the past nine months (from roughly 440,000 interactions per month to over 800,000) shows that adoption accelerates once the barriers are removed.

Stargate is the broader platform being rolled out now. It replaces HIN's 30-year-old central gateway with decentralized identity infrastructure (Decentralized Key Management System, or DKMS), adds the capability of FHIR-based structured clinical data exchange between institutions, and provides cryptographic audit trails that answer liability questions definitively. Central Stargate at HIN launches on 18 May 2026.

In how many and which countries do you operate? What attracts you to these markets, and what challenges do you face there?

Switzerland is where we operate in production. The HIN network reaches all healthcare professionals in the country, GPs, specialists, hospitals, pharmacies, and the SEAL deployment currently processes communication between them and their patients.

Bulgaria is where we build. The engineering office in Sofia - led by Kalin Canov and Zdravko Iliev - is where the core product development happens. Which makes the DHI Cluster context particularly relevant: Bulgaria is not just an engineering location for us. It is a European market with exactly the same cross-institutional trust challenges that we have spent five years solving in Switzerland.

The European Health Data Space (EHDS) creates the regulatory push that will make this infrastructure necessary across all EU member states. We are also members of the European Health Data Alliance (EHDA), which allows HIN's verification reach to extend beyond Swiss borders. The next markets are wherever the EHDS regulatory requirements land first - and that is all 27 EU member states on a timeline that is no longer theoretical.

The main challenge is the same everywhere: healthcare IT procurement is slow, cautious, and consensus-driven. The answer to that challenge is production evidence. 800,000 interactions per month in Switzerland is the answer to every "can this work at scale?" question.

In your view, what are the most serious challenges facing healthcare systems today, and how does your solution help address them?

Three structural problems define the crisis in healthcare IT.

First: data that cannot move. Clinical information sits in institutional silos because the trust infrastructure to exchange it securely across institutions does not exist at scale. This is not a data format problem. FHIR has largely solved the API question. It is a trust and data semantics problem: Institution A has no reliable way to verify that it is actually talking to Institution B, and not to someone pretending to be Institution B. And even within the organizations it can be very hard to make sense of data that is more than a week old.

Second: communication systems not designed for sensitivity. Email infrastructure was built for the public internet. It was not designed to carry a patient's psychiatric history or an HIV diagnosis. Patching it with certificates and encryption layers creates complexity that ends in either non-adoption or security theater.

Third: the binary choice between security and accessibility. Systems secure enough for healthcare professionals typically require software installation, certificate management, or proprietary client applications - none of which work for patients. The result is that the last mile of healthcare communication, the part that actually reaches the patient, is systematically the least secure part.

SEAL eliminates the third problem. Stargate eliminates the first. Together, they are building the infrastructure for a healthcare system where data flows as freely as it needs to, with cryptographic proof of authenticity at every step.

What made you join the DHI Cluster?

Because Vereign is a Bulgarian-Swiss company, and the DHI Cluster is where that intersection actually matters.

The engineering team that built everything we have deployed in Switzerland - SEAL, the early Stargate implementation, the preparation of our FHIR integration work is in Sofia. Bulgaria punches significantly above its weight in software engineering talent, and that talent has spent the last five years solving problems that will land on every European healthcare system's desk as the EHDS rollout accelerates.

The DHI Cluster is the connective tissue between that engineering capability and the healthcare institutions and policymakers who need to understand it. For us, membership is not a branding exercise. It is the practical means of building the relationships in the Bulgarian and broader Southeast European healthcare ecosystem that we are going to need as the next phase of deployment begins.

What are your goals for the next 1-3 years?

Central Stargate at HIN launches on 18 May 2026. That is the immediate milestone: The date on which Stargate becomes the Certificate Authority for HIN, replacing 30-year-old gateway infrastructure with a decentralized identity mesh. Hospital and technical partner deployments on OpenShift, Kubernetes and VM platforms begin the following week.

Over the following 18 months, the phased rollout extends to GP offices across Switzerland. FHIR-based structured data exchange - currently in preparation with some of Switzerland's largest university hospitals — enters production. The platform that started as encrypted communication for patients becomes the data exchange infrastructure for the entire Swiss healthcare sector.

Beyond Switzerland, the EHDS regulatory requirements create a 2026-2027 window where every EU member state needs the kind of cross-institutional trust infrastructure we have already proven in production. The partner program, we already have our first Authorised Partners in Cyberware and DAASI International, scales through that window. Vereign does not need to be in every country directly. The infrastructure does.

How do you imagine the future of healthcare in 10 years, and what role will your company play in it?

In 10 years, clinical data moves the way it should always have moved: securely, verifiably, and without requiring anyone on either end to negotiate a bilateral trust agreement with a shared certificate authority first.

A referral from a GP in Basel to a specialist in Munich carries cryptographic proof of who sent it, what it contained, and whether it was altered in transit. If there is a liability question - did the referrer communicate the patient's allergy? - the answer is not a matter of institutional memory or log file interpretation. It is mathematically provable.

AI agents cross institutional boundaries with verifiable identities. Devices in remote patient monitoring carry autonomous identifiers that rotate cryptographic keys without requiring firmware replacement. The trust infrastructure scales to billions of interactions without centralizing into a dependency on any single platform.

Vereign's role is building the layer beneath all of that. The decentralized key management infrastructure that makes digital authenticity the default rather than the exception. Not because regulation demands it, though it increasingly will. But because it is simply the right way to build digital systems that need to be trusted.