v1.2.1
A licensing shift and a self-hosting quality-of-life release. MemoryVault Community Edition moves to AGPL-3.0-or-later, and self-hosters get full data portability with vault export/import plus a choice of media storage backends.
What's new?
Open-sourced under AGPL-3.0
MemoryVault Community Edition moves from PolyForm-Noncommercial to AGPL-3.0-or-later, opening the door to standard open-source collaboration. New contribution guidelines and a community code of conduct now ship alongside the code.
Full vault export and import
Download your entire account, loved ones, memories, media, Open When messages, and digital legacy items as an encrypted zip archive, and restore it just as easily. Export and import run asynchronously through a background job queue processed every five minutes, and imports re-encrypt sensitive data and respect your existing plan limits.
Choose your own media storage
A new configurable storage layer supports local disk, S3, and Vercel Blob, detected automatically from your environment settings. A dedicated authenticated route now serves local uploads with proper session checks.
Smaller fixes and polish
Fixed a backdrop-blur clipping issue in the language selector, refined sidebar formatting, added new API routes for loved-one groups, introduced an OtpInput component, and gave the docs a substantial pass with corrected assets.
Why this release matters
- AGPL-3.0 licensing means the project can accept community contributions under standard open-source terms.
- Full vault export/import gives you a portable, encrypted backup you control, independent of MemoryVault itself.
- Pluggable storage means you are not locked into a single hosting provider for your media.
- Everything stays true to the Community Edition's founding principle: no limits, no locked features.
Updating
Users already running MemoryVault Community Edition can update to v1.2.1 to pick up the AGPL-3.0 license change, vault export/import, and the new storage backends.
After updating, pull the latest code, reinstall dependencies, run the database migration, and rebuild before restarting the app:
git pull
npm install
npm run db:migrate
npm run build && npm run start
You can view the release, browse the code, or follow future updates on GitHub.