Use case
Run team email on your own server with keys on your own devices, so nobody can lock you out.
Public materials do not yet show how users complete this job today or what they replace.
The product targets friction in this job, but public user evidence does not yet show the cost, frequency, or consequence of leaving it unsolved.
xOcto's call
Problem identified, demand strength unclear
The trend is that critical mail is leaving rented inboxes: server and keys stay in your hands. Don’t build a hobby encrypted mailbox. Enter with clinics, law firms, and cross-border teams—own domain, own server, device-side encryption. Judgement: teams afraid of lockouts pay seats before privacy hobbyists do.
Reason to use it
Why users would choose it
It promises a simpler way to complete this job: Run team email on your own server with keys on your own devices, so nobody can lock you out. The exact adoption motive and repeat use are not yet verified.
Where the easy answer breaks down
The tension worth following
An English validation note will follow from the public evidence.
If this is your job
Keep watching. It promises a simpler way to complete this job: Run team email on your own server with keys on your own devices, so nobody can lock you out. The exact adoption motive and repeat use are not yet verified.
Entry and what to borrow
The trend is that critical mail is leaving rented inboxes: server and keys stay in your hands. Don’t build a hobby encrypted mailbox. Enter with clinics, law firms, and cross-border teams—own domain, own server, device-side encryption. Judgement: teams afraid of lockouts pay seats before privacy hobbyists do.