Digital Legacy

Digital Legacy is a self-hosted beta console for planning a digital legacy, letting the owner sign in, check in on their plan, and rehearse the release…

  • Security
  • Tools & Utilities
Digital Legacy is a self-hosted beta console for planning a digital legacy, letting the owner sign in, check in on their plan, and rehearse the release process with isolated dry runs, while the actual beneficiary release is not yet implemented.

Platform availability

Available on 1 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score

Not enough data yet for a health score. It needs at least 2 of 4 factors: maintenance, popularity, ease of install, resource needs.

Availability: platform listings confirmed today

GitHub stars
0
Open issues
0
Last commit
2026-10-14
License
MIT
Activity
rising

Checked today - source: GitHub (gabryk91/digital-legacy-unraid)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install the React package first Run `npm install @migov/digital-guidelines-core-react` in your project before using these components. Without it, your app can't load the Digital Guidelines UI parts and your build will fail. source
  • Use the button after setup Once the packages are installed, add `<som-button button-type="default" color="primary">call to action</som-button>` to your HTML to get a standard button. Skipping the setup means the button element may not render correctly. source
  • Unraid template requirements The template requires local persistent storage for SQLite and keys, an HTTPS reverse proxy, a public host name, the proxy IP, and a random bootstrap token for the first administrator; review every field before installing. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does Digital Legacy automatically release information to beneficiaries?

No. The real release flow and beneficiary portal are not implemented, and the app does not automatically release information to beneficiaries.

What persistent data is required for the Unraid template?

It requires local persistent storage for SQLite and keys.

Can it be served without an HTTPS reverse proxy?

No. The template requires an HTTPS reverse proxy, the public host name, and the proxy IP.

What does the repository license cover?

The MIT license covers only the template, metadata, icon, and documentation. The container image and application code have separate licensing.

Answers sourced from github.com

Community

Collected today - public community threads