Data sovereignty without the enterprise price tag

For a growing number of teams — especially in the EU, DACH and Switzerland — where data lives is no longer a nice-to-have. Regulators, clients and boards increasingly ask a blunt question: can a foreign government compel access to our communications?

If your collaboration tool is operated under the US CLOUD Act, the honest answer is uncomfortable. So data residency has become a buying criterion, not a footnote.

Three levels of control

Whatping gives you a ladder, so you can pick the level of sovereignty you actually need:

1. EU / Swiss hosting. Run on infrastructure in the jurisdiction you choose. The media SFU can be pinned per region, so calls stay where your rules require.
2. Single-tenant. One application server and one database dedicated to you — no shared multi-tenant surface, cleaner data-processing story.
3. Self-host. Run the entire stack inside your own perimeter: app, database and SFU. No phone-home, air-gap friendly. Your infrastructure, your keys, your audit boundary.

Sovereignty and E2EE are complementary

End-to-end encryption already means we can’t read your content. Residency adds where the ciphertext and metadata physically sit and who has legal reach over it. Together they answer both halves of the question a regulator asks: who can read it (no one but the room) and whose laws apply (yours).

Honest about certification

We won’t pretend to hold certifications we don’t. The crypto core builds on the MLS standard and is continuously tested; formal external audit and SOC 2 / ISO 27001 are on our roadmap as we onboard design partners. If a specific attestation gates your procurement, ask us — we’ll tell you exactly where we are, and where we’re headed.

Data sovereignty shouldn’t require a six-figure enterprise contract. Building it in from day one is how we keep it accessible to the small, serious teams who need it most.