Data sovereignty & residency

Choose where the data lives — and who governs it

Communication data, its identities and its metadata stay in the environment you choose — with federation only where you approve it.

Request a security briefing Discuss deployment
Deployment boundaryDegree of control
Letro cloudSwitzerland
Swiss infrastructure, operated by a Swiss company
DedicatedSingle-tenant
Your own homeserver — no shared tenancy, no shared keys
SovereignYour infrastructure
Your geography, your administrators, your jurisdiction
Air-gappedNo external path
Nothing leaves the network. Federation stays off
Deployment boundary · degree of control
Letro cloud
Swiss, shared
Dedicated
Single tenant
Sovereign
Your infrastructure
Air-gapped
No external path

Residency is location

Where the data sits at rest.

Sovereignty is control

Who operates it, which law applies, who can administer it, and where it may move.

01Letro cloud

Swiss ground, Letro-operated

Shared Swiss infrastructure. Your rooms stay in Switzerland.

Swiss data centresLetro-operatedShared tenancy
02Dedicated

Your own homeserver

Single tenancy. Separate keys, separate storage.

Dedicated keysIsolated storageOperated by Letro
03Sovereign

Your infrastructure, your jurisdiction

You run it. Federation opens only where you approve it.

Your adminsYour jurisdictionFederation by approval
04Air-gapped

No external path

Nothing leaves the network. Federation stays off.

No inbound pathYour infrastructureOn-site only
See air-gapped deployment

Discuss residency requirements

Tell us your geography, your regulator, and who you need to talk to.

Security briefing