Local-First Tradeoff — Optional encrypted cloud sync for multi-device users #121
Answered
by
hijzy
renxinjian
asked this question in
Q&A
|
Memmy strictly local-only by design. Should we add end-to-end encrypted optional cloud sync (user self-hosted S3/MinIO) for users with multiple laptops? How to avoid breaking local-data-ownership promise? |
Answered by
hijzy
Jul 31, 2026
Replies: 1 comment
|
That’s a great direction. Support for user-selectable cloud storage backends is already on our roadmap, including self-hosted options such as S3 and MinIO. Our core principle will remain unchanged: Memmy will stay local-first by default, with cloud sync being entirely optional. Any sync solution will use end-to-end encryption, so storage providers cannot read users’ data. This enables multi-device use without compromising users’ ownership or control of their data. |
0 replies
Answer selected by
hijzy
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
That’s a great direction. Support for user-selectable cloud storage backends is already on our roadmap, including self-hosted options such as S3 and MinIO.
Our core principle will remain unchanged: Memmy will stay local-first by default, with cloud sync being entirely optional. Any sync solution will use end-to-end encryption, so storage providers cannot read users’ data. This enables multi-device use without compromising users’ ownership or control of their data.