Use case — Microsoft Teams alternative

Teamwork that never leaves the building.

Legal-grade control over where data lives and who can reach it — and externals who join without an IT ticket.

Request a demoSee residency options

Animation: in a general-purpose collaboration suite, a deal team juggles duplicate channels, external counsel waits as a pending guest and files sit in a separate service. The same work in Letro: a shared workspace, external counsel verified with PostNumber and no guest tenant, an encrypted letter with the voting agreement, an access and activity trail that is exported, and projects scoped inside the workspace. Illustrative example with fictional names.

ResidencySwiss or sovereign
ExternalsJoin without an IT ticket
ScopeWorkspaces and projects
TrailTimestamped, tamper-evident
What it is

Scoped to the matter, not to the tenant.

Secure team collaboration for firms that need stronger conversation scoping than a general-purpose suite, data residency in Switzerland or on their own infrastructure, and a way to bring clients and partners in without guest accounts.

Microsoft TeamsGeneral suite
Your tenant
Team · corporateGeneralGeneral (2)Deal — privateDeal — private (old)Files → SharePoint
Guest access · IT ticket · licence
External counsel · invite pending
Residency follows the tenant, not the matterFiles and recordings spread across servicesExternals wait on IT to be let in
→
LetroFirm workspace
Workspaces and projects
Alpine Acquisition · 3 firmsClient desk · ZurichInternal · deal teamFiles and calls stay in scope
Verified principals · permissions inherit
Swiss or sovereign · your boundary
Externals join with a verified PostNumber, no guest tenantMessages, files and calls in one scopeOne timestamped, tamper-evident trail
Why it belongs in Letro

Four things a general-purpose suite cannot promise

01 — Residency

Data stays inside your boundary

Swiss hosting by default. Sovereign deployments run on your own infrastructure, including air-gapped.

02 — Access

External parties without friction

Clients and partners join with a verified PostNumber. No guest-tenant configuration, no licensing puzzle.

03 — Structure

Structured, not overloaded

Workspaces and projects keep conversations scoped. Voice and video calls run inside them.

04 — Evidence

Built for compliance

Every message, file action and access event is designed to leave a timestamped, tamper-evident trail.

Familiar frictions

The usual Teams headaches, answered

A client needs one folder, so IT opens a guest account, checks the licence and comes back in three days.

Externals join with a verified PostNumber — no IT ticket

Four channels, two of them named General, and nobody is sure where the question was asked.

Workspaces and projects mirror desks and matters

The chat is here, the file is in SharePoint, the recording is somewhere else again.

Messages, files, polls and calls in one place

Residency is a tenant setting, decided once, far from the matter it now governs.

Cloud, Dedicated or Sovereign — your risk profile

Answering one regulator question means exporting from three systems and hoping they agree.

One trail: who joined, who saw it, when

How Letro replaces Teams

Fewer channels, clearer boundaries, a record you own.

01

Create Workspaces and projects

Mirror how your firm is organised — desks, matters, client groups.

02

Bring colleagues and externals in

Everyone joins as a verified Principal; permissions follow the Workspace.

03

Collaborate in one place

Messages, files, polls and calls stay inside the Workspace.

04

Own the data

Choose Cloud, Dedicated or Sovereign hosting according to your risk profile.

Get started

Discuss your deployment model

Standard rollout, private infrastructure, or stricter residency and isolation requirements — Letro gives you a verified, evidential foundation for team collaboration.

Book a demoDiscuss deployment