> ## Content Index
> Fetch the complete content index at: https://corelab.tech/llms.txt
> Use this file to discover other available public pages before exploring further.

# The Homelab Digital Estate: Building an End-of-Life Disaster Response Plan (From Markdown to ReMemory)
- URL: https://corelab.tech/homelab-end-of-life-disaster-response-plan/
- Published: 2026-11-10T12:15:00.000Z
- Updated: 2026-11-10T12:15:00.000Z
- Description: What happens to your homelab and encrypted family photos if you die tomorrow? How I built a two-tier digital estate response plan, combining plain-language family runbooks with offline Shamir threshold cryptography using ReMemory.
- Author: Core Lab Joe
- Tags: Homelab, Self-Hosting, Personal Security, #table-of-content

Every self-hoster knows the quiet pride of a tuned homelab. I spend hundreds of hours configuring multi-stack Docker architectures, custom OPNsense firewall routing, ZFS storage arrays, and private cloud replacements like Immich. But late at night, a sobering question haunts every homelab engineer: 

> **What happens to all of this if I die tomorrow?**

For most households, the answer is terrifying. If I am hit by a bus or suffer a sudden medical emergency, my homelab transforms overnight from an engineering project into an incomprehensible, blinking wall of anxiety for my family. Does the house Wi-Fi collapse the moment a DHCP container restarts? Are 15 years of irreplaceable family photos trapped inside an encrypted Immich container that nobody else knows how to access? Who stops the recurring cloud bills, and who safely powers down the server rack without corrupting family data?

After several readers asked how to prepare for this exact scenario, pointing to two remarkable open-source projects (thank you for the request!): Chrissy LeMaire's [potatoqualitee/eol-dr](https://github.com/potatoqualitee/eol-dr?ref=corelab.tech) and Jose Albornoz's [eljojo/rememory](https://github.com/eljojo/rememory?ref=corelab.tech), I sat down to design a battle-tested **End-of-Life Disaster Response Plan** for my own setup.

I have structured this guide into two logical tiers so you can implement what **fits your comfort level today**:

- **Part 1: The "Easy Button" (The Plain-Language Markdown Runbook):** A completely non-technical, human-first guide designed for a grieving partner, parent, or trustee. Inspired closely by Chrissy LeMaire's crowd-sourced `checklist.md`, it covers everything from social media memorialisation and master passwords down to Immich photo rescue and graceful server shutdown. It lives as a simple `.md` file that you can print and place into a physical fireproof safe.
- **Part 2: The Cryptographic Fortress (ReMemory & Shamir's Secret Sharing):** How to take that runbook, bundle it with your password vaults and recovery codes, and divide the digital keys among trusted friends using **ReMemory**. In an emergency, any designated threshold (e.g., 3 of 5 friends) can unlock the archive using an offline browser file, with zero servers, zero command line, and zero installation required.

---

---

## 1\. The Continuity Matrix: Evaluating Disaster Response Methods

Before writing runbooks or generating keys, it helps to evaluate how different continuity strategies stack up in real-world emergencies. When grief strikes, your family cannot navigate complex terminal syntax or parse raw configuration files:

The conclusion is straightforward: A physical paper or Markdown runbook is the **non-negotiable *baseline* everyone must have**. But coupling it with an offline cryptographic threshold tool like ReMemory solves the single-point-of-failure and snooping risks without placing an impossible technical burden on non-technical loved ones.

***If nothing else***, have a buddy you trust, accept an envelope with some basic info such as links and ip addresses and your master password(s) or key passwords. The idea is they only open it if you pass, and in there, is a brief description of what you'd like them to handle for your family.

### The Three-Tier Homelab Continuity Framework

From immediate emergency triage to long-term multi-party cryptographic estate recovery

Tier 1: Emergency Powerdown & Wi-Fi Triage (Immediate Action) HOUR ZERO 

- Zero Technical Barrier: Family can fall back to standard ISP modem Wi-Fi in 5 minutes by unplugging the OPNsense firewall.
- Graceful Halting: Single tap on the server chassis power button safely initiates ACPI Linux shutdown to prevent disk damage.

Tier 2: The Plain-Language Family Runbook (Day 1 to Month 1) TRANSITION PHASE 

- Human-First Documentation: Written for grieving non-techies; lists trusted tech contacts, phone numbers, and simple instructions.
- Memory Preservation: Clear steps on exporting Immich photo albums to USB drives, plus subscription cancellation roadmaps.

Tier 3: Cryptographic Threshold Succession (Month 1+) LONG-TERM SETTLEMENT 

- Shamir's Secret Sharing: ReMemory 3-of-5 threshold distributes encrypted keys across trusted family, friends, and legal trustees.
- Zero-Install Browser Decryption: Works 100% offline via self-contained `recover.html` without cloud reliance or software installs.

---

## 2\. Part 1: The Plain-Language Markdown Runbook (eol-dr Inspired)

The single most important rule of an End-of-Life runbook is **radical empathy**. When your partner or family opens this document, they are going through the worst days of their life. Technical jargon, condescending instructions, or walls of cryptic IP addresses will cause immediate panic.

### The Andy Story: Why This Project Exists

The inspiration for this framework originates from Chrissy LeMaire's open-source project [potatoqualitee/eol-dr](https://github.com/potatoqualitee/eol-dr?ref=corelab.tech). Back in 2012, Chrissy worked in Belgium alongside a brilliant VDI engineer named Andy. When Andy passed away unexpectedly, Chrissy reached out to his widow six months later. His widow confessed that she avoided his home office at all costs: terrified that the house Wi-Fi or TV would suddenly fail, and dreading the emotional agony of calling a technician to disassemble her late husband's passion project.

That heartbreaking reality resonated deeply across the homelab community. It spurred the creation of an open-source, crowd-sourced runbook: a living document that gives non-technical families the exact instructions, passwords, and permission they need to transition, preserve, or gracefully power down a homelab.

### Structure of the Markdown Runbook

My Markdown runbook is divided into 11 human-first sections. Here is what each section accomplishes:

### 1\. First Hours: Immediate Notification List

Before posting anything publicly on social media, your partner needs to know which close friends and family members must be notified first. List their full legal names, relationship to you, phone numbers, and time zones.

### 2\. Emergency Contacts: The "Trusted Tech Cabal"

Your partner should not have to debug a failed ZFS array or OPNsense gateway alone. Name two or three trusted, technically capable friends who have permission to assist. Explicitly document what they are authorized to access: *"Marc has full permission to log into my servers, extract family photo archives to USB drives, and wipe drive pools before hardware is sold."*

### 3\. Devices & Passcodes: The Digital Keys

Document the unlock PINs for your daily devices (phone, laptop, tablet). Modern two-factor authentication (2FA) is inextricably bound to mobile phones; if your family cannot unlock your phone, they are locked out of banking, email, and cloud accounts.

### 4\. Social Media & Memorialisation Accounts

Provide direct links and clear instructions on what to do with your digital footprint: Facebook legacy contacts, Google Inactive Account Manager, LinkedIn profile closure, and GitHub account succession.

### 5\. Passwords & Master Credentials

Explain how to access your password manager (Bitwarden, 1Password, or KeePass). **Never write master passwords digitally in plain text inside this file.** Instead, leave an explicit blank line for you to handwrite the master password in pen:

```TEXT
Master Password (handwritten in pen): ________________________________________ DATE: ____________________
```

> Additionally, if you use Bitwarden or Vaultwarden, configure **Emergency Access** for your designated trustee with a 7-day waiting period as a digital safety net.

### 6\. Subscriptions: What to Cancel vs. Keep

List recurring subscriptions in an easy-to-read table. Clarify which services to cancel immediately (developer SaaS, VPS cloud nodes, Discord Nitro, commercial VPNs) versus services to keep active temporarily (home internet, domain renewals, Spotify Family, and offsite cloud photo backups while data is recovered).

### 7\. Homelab & Local Storage: The Hardware Layout

Demystify the server closet. Clearly label and describe each piece of hardware: *"The tall black tower is CoreLab Main; the small fanless metal box with blue LEDs is the OPNsense router; the white square on the shelf is the Philips Hue bridge."* Document who is allowed to inherit the hardware, and highlight the critical storage sanitation rule:

> **CRITICAL WARNING: PREVENTING IDENTITY THEFT** Never sell, donate, or dispose of hard drives, SSDs, or NVMe sticks at an e-waste depot without cryptographic wiping. Homelab drives contain years of tax returns, medical scans, and private keys. Have a tech friend perform an ATA Secure Erase (`blkdiscard` or multi-pass `shred`), or physically drill holes through the drive platters.

### 8\. Rescuing Family Memories: The Immich Photo Vault

Irreplaceable family memories must never remain trapped behind container walls. Provide two distinct methods for family to rescue photos:

- **Method 1 (Web Interface Export):** Navigate to `http://10.0.0.25:2283/`, log in with the master family account, click each *Album*, select all photos, and click *Download* to generate zip files.
  - Might have to create a new album, add ALL pictures to it, and download that.
- **Method 2 (Direct USB/External Disk Dump):** For tech friends, document the exact raw filesystem path: `/ssd/containers/photos/library/`. The files are standard JPEG, HEIC, and MP4 files organized chronologically by year and month, with no proprietary software required.

![Immich Album View where you can select each album to download. Might be a lengthy process!](https://corelab.tech/content/images/2026/11/Immich-Download-Album.webp)

Immich Album View where you can select each album to download. Might be a lengthy process!

### 9\. Home Network Survival & The "Nuclear Option"

If a custom OPNsense router or DNS container fails, the house loses internet. Provide a 60-second power cycle guide. Then provide **The 5-Minute Nuclear Option**: Explain how to call the ISP, enable the built-in Wi-Fi on the stock ISP modem, set the SSID to `CoreLab-Home` with the home Wi-Fi password, and unplug the OPNsense firewall. Every phone, tablet, and TV in the house will instantly reconnect to the internet without touching a single server, allowing the family to unplug the homelab forever.

### 10\. Graceful Server Shutdown Procedures

Explain how to safely shut down the servers without corrupting data:

1. **Web GUI Path:** Navigating to OpenMediaVault at `http://10.0.0.10/`, clicking the power icon, and selecting *Shut Down*.
2. **Physical Chassis Button:** Clearly explain that briefly tapping the front power button once sends an ACPI shutdown signal to Linux, allowing all 60+ Docker containers to terminate cleanly and unmount disks within 45 seconds. Warn them never to yank power cords out of the wall while disks are spinning.

### 11\. Home Automation, 2FA, Finances, Legal & Final Wishes

Follow Chrissy LeMaire's template to complete the remaining critical sections:

- **Home Automation / IoT:** Document how Hue bulbs, Sonos speakers, and smart plugs behave on the fallback Wi-Fi SSID.
- **2FA / MFA:** Document mobile authenticator cloud backups, physical YubiKey locations (keychain vs. safe), and paper backup recovery sheets.
- **Financial Inflow & Outflow:** Primary joint bank accounts, life insurance policies through employers, residual affiliate income, and auto-pay household utility schedules.
- **Legal & Final Wishes:** Locations of original signed wills, estate attorney and accountant phone numbers, physical safe combinations, and designated guardians for pets.

---

## 3\. The Complete Sample Markdown Template

Below is the complete, production-ready 230-line sample runbook based loosely on `eol-dr` project above! It uses sanitized fictitious contacts, sample private IP subnets, and realistic homelab services. You can copy it directly and modify to your needs of course:

```markdown
# End-of-Life Disaster Response & Homelab Continuity Checklist
> **Author Note for Family & Trustees:** If you are reading this, I am no longer around to fix the Wi-Fi or tinker in the server room. First, take a deep breath. You do not need to figure any of this out today, tomorrow, or even this month. Everything in this house is running on automatic pilot, and nothing in this rack will break if you leave it completely alone.

---

## 1. First Response: Who to Contact Directly
Before posting anything publicly on social media, open my phone or laptop, create a simple note, and send direct messages to the following close friends and family:

- **Primary Homelab Contact & Sysadmin:** Marc Tremblay (`marc.tremblay.sample@corelab.tech` / +1-555-019-2831)
  - *Context:* Marc runs an identical Docker and OpenMediaVault setup and knows my network architecture inside and out. Hand him this document or your ReMemory key bundle. He will help with zero judgment.
- **Secondary Family Trustee & Co-Executor:** Sarah Jenkins (`sarah.jenkins.sample@corelab.tech` / +1-555-014-9922)
  - *Context:* Co-trustee who holds the second ReMemory key bundle and has access to our physical safe.
- **Close Friends to Notify Directly:**
  - *Signal / iMessage:* Alex Chen (+1-555-018-7744), Dave Miller (+1-555-012-3399)
  - *WhatsApp:* Family Group Chat
  - *Discord:* Check my recent DM list & notify user `Claudette#1234` and `DevGroup`
  - *Workplace / Employer:* HR Department contact at `hr.sample@company.com`

Once immediate family and close friends are aware, feel free to post an announcement on X (Twitter), LinkedIn, and Facebook if you wish.

---

## 2. Tech Stack & Digital Accounts

This section covers website logins, emails, password vaults, and what to do with the homelab hardware.

### Emails
I primarily use `me.sample@corelab.tech` and my personal backup `sample.homelabber@gmail.com`. You can access both through my phone or laptop.
- **CRITICAL:** Keep my personal mobile phone and laptop active and charged for at least **one full year**. Do not wipe or cancel my cellular plan right away, as many banking, domain, and 2FA authentication alerts require access to my phone number or email.
- Forwarding rules are set so all server alert emails land in `sample.homelabber@gmail.com`.

### Social Media Accounts
- **KeePass / Bitwarden:** All passwords and TOTP two-factor codes are stored in the password manager.
- **X (Twitter):** Leave the account open for at least 1-2 years. If you decide to close it, ask Marc or a trusted friend to archive old posts first.
- **Facebook & Instagram:** Facebook can be turned into a memorial page or exported and closed via Settings -> "Memorialization Settings". Instagram has vacation photos that you may enjoy looking back on.
- **GitHub:** I have designated Marc Tremblay as my GitHub Successor under Settings -> Account -> Successor settings. He can maintain or archive my open-source repositories.
- **LinkedIn & Discord:** Cancel any paid Nitro or Premium tiers and request account closure.

### Domains & Blogs
- **Registrar:** All domains (`corelab.tech` and personal project domains) are registered via **Porkbun** and routed through **Cloudflare**.
  - Porkbun auto-renews annually on our joint credit card.
  - Keep `corelab.tech` active or transfer domain ownership to Marc Tremblay so tutorials and technical guides remain online.
- **Blog Hosting (Ghost CMS):** The blog runs as a self-hosted Docker container in the homelab. If you shut down the homelab, Marc can help export the Ghost database to an affordable static web host or archive it.

### Password Managers
Our entire digital life is documented inside the password vault.
- **Application:** KeePassXC database (backed up on my laptop desktop as `vault_backup.kdbx`) and synchronized with Bitwarden.
- **Master Password:** Stored only in human handwriting on this printed page and inside the physical fireproof safe:
  - `Master Password: _________________________________________________________________`
- In an emergency, our Bitwarden vault also has **Emergency Access** configured for Sarah Jenkins with a 7-day waiting period.

### Subscriptions (What to Keep vs. What to Cancel)
Recurring subscriptions auto-debit from our joint account. Cancel the non-essentials:
- **Streaming & Entertainment:**
  - YouTube Premium: Keep for commercial-free living room TV, or cancel and resubscribe under your own email.
  - Netflix, Spotify Family, Amazon Prime: Keep if you use them; cancel add-on channels.
  - Discord Nitro, Twitch subscriptions: Cancel immediately.
- **VPNs & Privacy Services:**
  - Commercial VPN (e.g. ProtonVPN / Mullvad): Cancel.
- **Apple / Google Subscriptions:**
  - On my iPhone: Open *Settings -> [My Name at Top] -> Subscriptions*. Cancel individual app subs.

---

## 3. Homelab & Local Storage (The Core Lab)

### The Hardware Layout
The server rack / shelf in the utility room consists of:
1. **The Main Server Node ("CoreLab Main"):** High-spec Intel tower running 60+ Docker containers and storage pools.
2. **The NAS Storage Node (OpenMediaVault):** Dedicated data server hosting our network drives.
3. **The Firewall Mini-PC (OPNsense):** Small fanless black metal chassis with dual Ethernet ports connected directly to the ISP modem.
4. **The Network Switch & Access Points:** Managed PoE switch providing wired ports and Wi-Fi throughout the home.

### Hardware Disposition & Who Gets What
- Marc Tremblay has permission to take the managed network switch, patch panel accessories, and server chassis.
- Mini-PCs and spare monitors can be gifted to family or sold on Marketplace  -  **BUT ONLY AFTER DISKS ARE SANITIZED** (see warning below).
- Any Apple Mac mini or MacBook: Peter or Sarah can have them. Follow Apple's official instructions to sign out of iCloud and disable "Find My" before resetting, or the device will remain activation locked forever.

> [!CAUTION]
> ### The Hard Drive Sanitation Warning (DO NOT GET IDENTITY STOLEN)
> **NEVER SELL, DONATE, OR THROW OUT HARD DRIVES OR SSDS IN THE TRASH OR E-WASTE.**  
> Our drives contain 15 years of personal financial taxes, mortgage documents, family scans, and cryptographic keys. A simple Windows "Format" does NOT erase data on solid-state drives.
> - Have Marc Tremblay perform a hardware cryptographic ATA Secure Erase (`blkdiscard` on NVMe SSDs or multi-pass `shred` on HDDs).
> - If nobody is available to securely wipe the drives, **keep the physical drives in a drawer** or physically drill through the drive platters with a metal drill press.

---

## 4. Rescuing Our Family Memories (Immich Photo Vault)
**Do not worry: Every family photo, vacation album, and home video from the past 15 years is safe.**

Our photos are managed by **Immich**, our private self-hosted photo vault.

### Method 1: Exporting via the Web Browser (Simple)
1. On any home computer or laptop, open `http://10.0.0.25:2283/` in your browser.
2. Log in with the master family account (credentials in KeePass/Bitwarden).
3. Click **Albums** in the left sidebar.
4. Select any album (or select all photos on the timeline), click the **Three Dots (...)** in the top right corner, and select **Download**.
5. Your browser will download a standard `.zip` archive containing the original full-resolution JPEG, HEIC, and MP4 files.

### Method 2: Direct USB Drive Dump (Fastest for Bulk Backup)
If Marc or a tech friend is assisting you:
1. All original master photos reside on the storage pool at `/ssd/containers/photos/library/` (mirrored on `/brain/media/photos/`).
2. The folder structure is completely standard: `YYYY/YYYY-MM-DD/filename.jpg`. They are regular files and do not require Immich, Docker, or any database to open.
3. Plug a 2TB or larger external USB hard drive into the server and copy the entire folder directly.

---

## 5. Home Network & Wi-Fi Survival

### "The Internet is Down and I Just Want Wi-Fi Working"
1. Unplug the power cord from the black internet modem provided by the ISP (Bell / Rogers / Telus).
2. Wait 30 seconds, then plug it back in. Wait 5 minutes for the status lights to turn solid white/green.
3. If internet is still offline, locate the small fanless OPNsense firewall mini-PC. Unplug its power cable for 10 seconds, then plug it back in.

### The 5-Minute "Nuclear Option" (Dismantling the Homelab Entirely)
You do NOT need to keep my server rack running to have Wi-Fi in this house:
1. Call our ISP (phone number on our monthly bill or inside the safe).
2. Tell technical support: *"I need to enable the built-in Wi-Fi on my modem/gateway."*
3. Ask the technician to set the Wi-Fi Network Name (SSID) to `CoreLab-Home` and set the password to our regular home Wi-Fi password (written in our physical safe).
4. Once the ISP modem Wi-Fi is active, simply unplug the Ethernet cable running between the ISP modem and the OPNsense firewall.
5. Every phone, TV, laptop, and smart tablet in the house will instantly reconnect to the internet without touching a single server.
6. You can now power down the entire server rack and never touch it again.

### Graceful Server Shutdown Procedures
- **Via Web Browser:** Open `http://10.0.0.10/` (OpenMediaVault) -> Click the **Power Icon** in the top right -> Click **Shut Down**.
- **Via Physical Button:** Walk up to the server chassis and **tap the front power button once** (do NOT hold it down). Linux will cleanly unmount all drives, stop Docker containers, and shut down within 45 seconds. Never yank power cords out of the wall while disks are spinning.

---

## 6. Home Automation & IoT Devices
If you switch to the ISP's built-in Wi-Fi, the following devices will reconnect automatically if the network name and password match:
- Philips Hue Bridge (white square box plugged into the switch)
- Sonos living room soundbar and bedroom speakers
- Smart TVs, Apple TV, and Roku streaming sticks
- Robot vacuum and smart air purifiers
- Security cameras and smart doorbells

If smart light bulbs become unresponsive, flip the wall switch off and back on to restore normal manual lamp operation.

---

## 7. Two-Factor Authentication (2FA / MFA)
- **Primary MFA Apps:** I use **Microsoft Authenticator** and **Authy** on my mobile phone.
  - Microsoft Authenticator is backed up to the cloud under `sample.homelabber@gmail.com`. If my phone is damaged, you can restore all 2FA codes by signing into the app on a replacement phone.
- **Physical Hardware Security Keys (YubiKeys):**
  - Primary black YubiKey 5C NFC: On my keychain.
  - Backup blue YubiKey: Stored inside the physical fireproof safe.
  - These keys plug into any USB-C port to authorize account logins.
- **One-Time Recovery Backup Codes:**
  - Paper sheets containing printed 8-digit emergency recovery codes for Google, Apple ID, GitHub, and Cloudflare are stored in the envelope inside the fireproof safe.

---

## 8. Cloud Infrastructure & Hosting Subscriptions
These bills charge credit cards automatically. Cancel high-cost items quickly:
- **Cloudflare:** Free tier. Keep active so domains resolve.
- **Hetzner / VPS Cloud Compute:** ~$8-15/mo. Cancel immediately via the web console.
- **Backblaze B2 (Encrypted Offsite Backup):** ~$5-8/mo. **Keep active for 6 months** while you ensure all family photos and documents are safely in your possession.
- **GitHub Copilot / Developer SaaS:** Cancel immediately.

---

## 9. Input (Finances, Inflow & Money)

### Bank Accounts & PayPal
- **Primary Joint Checking / Savings (Royal Bank / TD / Chase):**
  - Account numbers and card PINs are stored in KeePass/Bitwarden.
  - Joint account: Funds remain immediately available to surviving spouse upon death certificate submission.
- **Secondary / Online Bank:**
  - Checking account used for online subscriptions and foreign purchases.
- **PayPal:**
  - Login via `me.sample@corelab.tech` with 2FA code from Authenticator app. Transfer balances to primary joint checking.

### Life Insurance
- **Employer Group Life Insurance:**
  - Policy through Sun Life / Manulife / Fidelity.
  - Standard payout is 2x annual salary, plus additional accidental death & dismemberment (AD&D).
  - HR contact: `benefits.sample@company.com`.

### Residual & Affiliate Inflow
- Core Lab blog affiliate commissions (Geniuslink / Linkshare / Amazon Associates) deposit directly to primary joint checking monthly.
- GitHub Sponsors / Patreon: Close or redirect after notifying community supporters.

### Investments & Retirement
- 401(k) / RRSP / TFSA / Vanguard accounts: Call our financial advisor or the 1-800 support line listed in the physical safe. Beneficiaries are designated directly on the accounts.

---

## 10. Output (Bills, Utilities & Auto-Pay)
All major home expenses are configured for automatic monthly withdrawal:
- **Home & Auto Insurance:** State Farm / Intact. Auto-debited monthly. Call to adjust vehicle coverage.
- **Home Utilities:** Hydro / Electricity, Natural Gas, Municipal Water & Waste. Auto-debited.
- **Cellular & Home Internet:** Auto-debited. Keep active during estate transition.
- **Property Taxes & Mortgage:** Auto-withdrawn on the 1st of each month.

---

## 11. Miscellaneous & Legal

### Legal Documents & Will
- Original signed copies of our **Wills, Powers of Attorney, and Healthcare Directives** are stored in the safe deposit box at our local bank branch, with copies in our home fireproof safe.
- **Estate Attorney:** David Sterling, Sterling & Partners Legal (`dsterling.sample@lawfirm.com` / +1-555-019-4400). Contact them early; they will guide you through probate and estate settlement.
- **Accountant:** Tracey Calendar, CPA (`tracey.sample@calendarcpa.com`). Tracey has handled our tax filings for years and has complete records.

### Physical Security & Safe Access
- **Home Fireproof Document Safe:**
  - Location: Master bedroom closet shelf.
  - Combination / Key location: Key is on my main key ring; digital combination is recorded in KeePass.
- **Toolbox / Server Rack Cabinet Keys:**
  - Located in the small ceramic bowl on my office desk.

### Answers to Common Security Questions
Check KeePass first: almost all of my security question answers are randomly generated strings stored in the notes field. For legacy accounts that used honest answers:
- First childhood pet: *Barnaby*
- Mother's maiden name: *Tremblay*
- Street I grew up on: *Maplewood Avenue*
- High school mascot: *Falcons*

---

## 12. Final Wishes & Pets

### Memorial Preferences
- Notes for my obituary and preferred charitable donations in lieu of flowers are in the blue folder inside the fireproof safe.
- I prefer simple cremation and an informal gathering with good food, great music, and laughter over solemn ceremonies.

### Our Pets
- **Veterinarian:** Oakridge Animal Hospital (+1-555-017-8822 / Dr. Henderson).
- **Diet & Medications:** Details pinned to the inside of the pantry door.
- **Designated Pet Guardian:** Sarah Jenkins has explicitly agreed to take in our pets if caring for them becomes overwhelming.

```

Once you customize this template with your own details, **print a physical copy on paper, write your master password in pen**, and store it inside your family's fireproof lockbox. 

> That is Part 1 complete: your "**easy button**" is active!

---

## 4\. Part 2: Cryptographic Threshold Delivery with ReMemory

A paper runbook in a physical safe is effective, but it introduces distinct security vulnerabilities: a burglar can steal the safe, a house fire can incinerate the paper, or a single person with safe access can inspect your master passwords prematurely. Conversely, cloud-based "dead man's switches" rely on third-party servers that may shut down or misfire.

This is where [ReMemory](https://github.com/eljojo/rememory?ref=corelab.tech) provides an elegant cryptographic breakthrough. Built by Jose Albornoz, ReMemory combines **Shamir's Secret Sharing (SSS)** with modern **age encryption** (by Filippo Valsorda) to create a multi-key digital vault designed specifically for non-technical recovery.

### How Shamir's Secret Sharing Works

Instead of giving one person a master password, ReMemory mathematically divides the encryption key into *N* separate pieces (shares), requiring an *M-of-N* threshold to reconstruct it:

- For example, in a **3-of-5 threshold** scheme, you designate 5 trusted trustees (e.g., your partner, your sibling, your tech friend Marc, your executor, and your lawyer).
- Any individual trustee holding a single bundle has **mathematically zero information** about your secrets. Not "hard to crack": absolute, mathematical zero.
- To unlock the vault, any 3 of the 5 trustees must physically or digitally come together and combine their pieces. If one person loses their file, or another is unavailable, the remaining trustees can still successfully restore your estate.

### The ReMemory Offline Superpower: recover.html

Most Shamir implementations (like classic Unix `ssss` or HashiCorp Vault) require running complex CLI tools in terminal shells. Non-technical partners cannot do this.

ReMemory solves this by generating a standalone, self-contained HTML file called `recover.html` (\~300 KB) inside every trustee's zip bundle. It contains the entire decryption engine written in client-side JavaScript. **It requires zero internet connection, zero web servers, and zero software installation.** Any trustee simply double-clicks `recover.html` in Chrome, Firefox, Safari, or Edge on any computer, drags in the required shares from the other trustees, and the decrypted files unlock immediately in their browser.

---

## 5\. Deploying ReMemory via Docker Compose

You can generate bundles using the public static web creator at `eljojo.github.io/rememory/maker.html` (which executes 100% locally in your browser memory). However, as self-hosters running private homelabs, I run the official ReMemory container on my own infrastructure.

Here is my production Docker Compose configuration:

```yaml
services:
  rememory:
    container_name: rememory
    image: ghcr.io/eljojo/rememory:latest
    restart: unless-stopped
    ports:
      - "8080:8080"
    environment:
      - PUID=1000
      - PGID=100
      - TZ=America/Toronto
      - REMEMORY_ADMIN_PASSWORD=corelab # Example only! CHANGE!
    volumes:
      - /ssd/containers/security/rememory/data:/data
    deploy:
      resources:
        limits:
          memory: 1G (512m minimum!)

```

Spin up the stack from your compose workspace:

```bash
docker compose up -d rememory

```

---

## 6\. Creating and Distributing Your Estate Bundles (Step-by-Step)

### Step 1: Gather Your Sensitive Payload

Prepare a clean directory containing the assets you need to protect:

1. Your completed `homelab-disaster-response-checklist.md`.
2. An exported, encrypted copy of your password manager vault (e.g. `vault_backup.kdbx` or Bitwarden encrypted JSON).
3. One-time 2FA recovery backup codes for Google, Apple ID, and domain registrars.
4. A scanned copy of your legal will and power of attorney documents.

📡

The official docs are really good and simple to use!  
  
[https://eljojo.github.io/rememory/docs.html#creating](https://eljojo.github.io/rememory/docs.html?ref=corelab.tech#creating)

### Step 2: Configure Trustees and Thresholds in the Web UI

1. Open the ReMemory interface at `http://10.0.0.65:8080/maker.html` (or navigate directly to your local instance).
2. Add your trusted contacts. For each person, enter their Name, Email, and Phone number. ReMemory includes these contact details on everyone's instructions so trustees know exactly whom to call when coordinating recovery.
3. Set your **Threshold**. For a circle of 5 people, a `3-of-5` threshold provides the balance between fault tolerance (two people can lose their bundles) and security (no two people can collude prematurely).
4. Attach your payload files or zip archive.
5. Click **Generate Bundles**.

![](https://corelab.tech/content/images/2026/11/ReMemories-Bundle-Creator.webp)

### Step 3: Inspecting What Trustees Receive

ReMemory outputs individual zip bundles for each designated contact (e.g. `bundle-alice.zip`, `bundle-marc.zip`, `bundle-sarah.zip`). Inside each bundle is:

- `README.txt` & `README.pdf`: Formatted printable instructions explaining what the file is, the contact list of fellow trustees, and their personal secret share string.
- `recover.html`: The self-contained offline browser recovery tool with their share pre-loaded.
- `MANIFEST.age`: The encrypted archive payload (bundled natively inside `recover.html` if under 10MB).

### Step 4: The Fire Drill (Testing Offline Recovery)

Before storing bundles, perform a recovery drill with a test archive:

1. Disconnect your laptop from Wi-Fi and ethernet (test 100% offline).
2. Open `bundle-sarah/recover.html` in any web browser. Notice that Sarah's piece is automatically recognized.
3. Drag the `README.txt` or bundle files from two other trustees (e.g. Marc and Brother) directly onto the browser window.
4. The moment the 3rd piece touches the screen, the threshold is met: the JavaScript engine reconstructs the age key, decrypts the payload, and displays your files ready for download!

flowchart TD
    subgraph Prepare ["Phase 1: Encrypt & Divide (ReMemory + age)"]
        Runbook["Homelab Runbook (.md)
+ Encrypted Vault Backup
+ 2FA Recovery Codes"]
        AgeEnc["age Encryption Engine
(Filippo Valsorda)"]
        Shamir["Shamir's Secret Sharing
(M-of-N Threshold: 3 of 5)"]
        Runbook --> AgeEnc --> Shamir
    end

    subgraph Distribute ["Phase 2: Distribution to Trusted Circle"]
        Shamir --> B1["Bundle 1: Partner
(recover.html + PDF)"]
        Shamir --> B2["Bundle 2: Tech Friend Marc
(recover.html + PDF)"]
        Shamir --> B3["Bundle 3: Sibling
(recover.html + PDF)"]
        Shamir --> B4["Bundle 4: Legal Trustee
(recover.html + PDF)"]
        Shamir --> B5["Bundle 5: Close Friend
(recover.html + PDF)"]
    end

    subgraph Recover ["Phase 3: Emergency Offline Recovery"]
        B1 -.->|Share 1| WebRecovery
        B2 -.->|Share 2| WebRecovery
        B3 -.->|Share 3| WebRecovery
        WebRecovery["Offline recover.html in Browser
(Zero Install / Zero Cloud)
Threshold Met: 3 of 5"]
        WebRecovery --> Unlocked["Decrypted Markdown Runbook
& Master Passwords"]
    end

    subgraph Action ["Phase 4: Family Action Plan"]
        Unlocked --> Shutdown["1. Safe Homelab Powerdown
(WebGUI or ACPI Chassis Button)"]
        Unlocked --> Photos["2. Immich Photo Vault Rescue
(Export to USB Hard Drive)"]
        Unlocked --> Subs["3. Cancel Unneeded VPS/Cloud Bills
(Keep Domains Active)"]
        Unlocked --> Network["4. Swap to ISP Gateway Wi-Fi
(Zero Ongoing Complexity)"]
    end

---

## 7\. Security Blueprint: Paper vs. Shamir Threshold

Why go through the effort of ReMemory when you could just write down a master password on an envelope? The visual comparison below highlights why threshold cryptography is dramatically superior for digital estates:

### Shamir's Secret Sharing vs. Master Password Hazard

Why mathematical threshold splitting eliminates both premature snooping and single-point-of-failure loss

ReMemory M-of-N Threshold (The Golden Standard) MATHEMATICALLY ZERO LEAKAGE 

Holding 1 or 2 pieces out of 5 yields **zero information**. No single person can snoop on your passwords while you are alive, yet if 2 trustees lose their keys, the remaining 3 can still unlock your digital estate offline.

Single Master Password on Paper / Envelope SINGLE POINT OF FAILURE 

If the physical paper is lost, damaged by water/fire, or stolen during a home burglary, total compromise or irreversible lockout occurs. Also creates awkward social trust dilemmas.

Cloud Dead Man's Switches FRAGILE CLOUD DEPENDENCY 

If an automated email pings during a long camping trip or hospital stay, the switch can accidentally trigger, emailing your passwords prematurely. If the cloud vendor shuts down, your recovery plan silently dies.

---

## Summary: Leave Clarity, Not Chaos ❤️

Building a sophisticated homelab is a deeply rewarding endeavour. But that responsibility extends to ensuring the systems I build do not become an insurmountable burden for my family if the unexpected happens. Taking a single afternoon to prepare for the unthinkable ensures that your homelab remains a source of cherished memories rather than an overwhelming burden.

Start with **Part 1** this weekend: customize the provided `.md` checklist, print it out, write your master vault credentials by hand, and lock it in your physical safe. Then, when you have an hour to spare, deploy **ReMemory** in Docker, generate your 3-of-5 threshold bundles, and distribute them to your inner circle. Your future self and your family will thank you.

For more architectural guides on resilient storage, mini-PC hosting, and private cloud deployments, explore my [DIY NAS Build Guide](https://corelab.tech/diy-nas-build-guide/), read through my [Advanced Docker Deployments](https://corelab.tech/advanced-docker-architectures-mastering-multi-stack-deployments/), or browse curated hardware in the [Core Lab Hardware Store](https://corelab.tech/shop/).