v1.2.0
This release is mostly about what happens after you share something: messages that deliver themselves on time, and loved ones who can now keep what they receive instead of relying on a single one-time link.
What's new?
The biggest addition in v1.1.0 is support for Open When messages in the Community Edition.
Open When messages can now send themselves automatically
Previously, Open When messages only went out as part of a full legacy release. Now you can set a message to a specific date, and MemoryVault delivers it on its own, with a private link and access password for the loved one, while your account stays active. This runs on a daily background job, so there's nothing extra to do.
Recipients get a place of their own
Anyone who receives a link to shared memories or an Open When message can now create an account (or log in) to keep that content permanently, instead of depending on the one-time link. The sidebar now has a toggle between "My vault" and a new recipient view showing "Shared vaults."
Trusted contact status on the dashboard
The dashboard now clearly shows whether your legacy protection and trusted contact are properly set up, with a direct link to finish it if not.
Smaller improvements
The sidebar and account page were redesigned with usage indicators for storage, memories, and Open When messages (always "unlimited" in the Community Edition, of course), and the onboarding tours were updated to match the new navigation.
Why this release matters
- Open When messages now deliver exactly when you planned, with no manual step required.
- Loved ones are no longer dependent on a single link that can expire or get lost, they can keep everything in their own account.
- A local ZIP export means the content stays recoverable, independent of MemoryVault itself.
- Everything stays true to the Community Edition's core idea: no limits, no locked-away features.
Updating
Users already running MemoryVault Community Edition can update to v1.2.0 to get automatic Open When delivery, recipient accounts, and the latest fixes.
After updating, it's a good idea to reinstall dependencies, run the database migrations, and restart the app.
You can view the release, browse the code, or follow future updates on GitHub.