ReMemory is an Apache-2.0 licensed encryption tool written in Go that seals your files with age encryption, splits the decryption key into separate pieces held by people you trust, and lets a threshold of those people unlock the archive together without any server being involved.

What it is

ReMemory is a file-encryption and key-management tool built on the age encryption format. You encrypt your files, then split the resulting key into a chosen number of pieces and distribute them to people you select. Each recipient receives a self-contained bundle containing a browser-based recovery tool called recover.html, which runs offline and requires neither a server nor the ReMemory project itself to exist at the moment of recovery. The split is mathematical rather than commercial: any threshold number of pieces can reconstruct the key, while a single piece reveals zero information.

The concrete problem it solves is the single-point-of-failure of ordinary secret storage. Password manager recovery codes, cryptocurrency seeds, important documents, and instructions for loved ones normally sit behind one key held by one person, which means one failure — death, incapacity, a lost device — can destroy access permanently. ReMemory replaces that single holder with a group you define, whether that is 2-of-2 for a couple, 2-of-3 for a small circle, or 3-of-5 for a wider group, and it belongs to the age-encryption, digital-estate-planning, and disaster-recovery space.

Key capabilities

• Encrypts files with age encryption, producing a MANIFEST.age archive.
• Splits the decryption key across a configurable number of recipients with a configurable unlock threshold.
• Ships a self-contained recover.html recovery tool of roughly 300 KB that runs in any browser, works offline, and needs no server or project dependency.
• Produces ZIP bundles containing README.txt with each person's unique piece and a contact list, plus a print-formatted README.pdf.
• Embeds the encrypted archive directly inside recover.html for smaller archives; only archives over 10 MB ship MANIFEST.age separately.
• Supports recovery by dragging README files onto the page, or by dragging an entire bundle.
• Offers time-locked archives on an experimental basis, which require a brief internet connection at recovery time.

Who uses it and how

• Couples and small circles configure 2-of-2 or 2-of-3 so that no single person can open the archive alone.
• Wider groups such as families use 3-of-5, distributing bundles across people who may not know each other.
• People doing digital-estate planning seal password manager recovery codes, cryptocurrency seeds, and instructions for loved ones.
• Disaster-recovery planners rely on the offline-first design, where recipients recover files without network access or any running service.
• Self-hosters and automation users run the Docker image on port 8080 with a rememory-data volume, or drive the CLI from scripts.

Getting started

Install with Homebrew via brew install eljojo/rememory/rememory, download the rememory-linux-amd64 binary, run nix run github:eljojo/rememory, or run the self-hosted image with docker run -d --name rememory -p 8080:8080 -v rememory-data:/data ghcr.io/eljojo/rememory:latest. Browser users can create bundles directly at eljojo.github.io/rememory/maker.html, where everything runs locally and files never leave the device.

How it compares

No list of paid products being replaced is provided for ReMemory, and no similar tools are named in the facts. On the evidence available, it stands alone in this registry, with its distinguishing property being that recovery depends on none of the project's own infrastructure.

When to use it — and when not to

Choose ReMemory when the threat you care about is loss of access and you are willing to operate something yourself: a self-hoster must run and maintain the Docker container and its rememory-data volume. Do not choose it if you want a hosted service with central account recovery, because bundle custody belongs entirely to your recipients and a lost bundle cannot be regenerated by anyone else. The time-locked feature is explicitly experimental and breaks the offline promise by requiring internet access at recovery time, so treat it as unproven compared with the standard path.

graph TB
    subgraph seal["① SEAL (you do this once)"]
        A[Your Files] --> B[Encrypt with age]
        B --> C[Split key into 5 pieces]
        C --> D1[Alice's bundle]
        C --> D2[Bob's bundle]
        C --> D3[Camila's bundle]
        C --> D4[Dominique's bundle]
        C --> D5[Elias's bundle]
    end

    subgraph recover["② RECOVER (friends do this together)"]
        R1[Alice opens recover.html] --> R2[Her piece is pre-loaded]
        R2 --> R3[Drags Bob's file]
        R3 --> R4[Drags Camila's file]
        R4 --> R5{3 of 5 pieces}
        R5 -->|Threshold met| R6[Files unlocked]
        R6 --> R7[Download files]
    end

    D1 -.-> R1
    D2 -.-> R3
    D3 -.-> R4

# macOS (Homebrew)
brew install eljojo/rememory/rememory

# Linux (x86_64)
curl -Lo rememory https://github.com/eljojo/rememory/releases/latest/download/rememory-linux-amd64
chmod +x rememory
sudo mv rememory /usr/local/bin/

# Docker (self-hosted)
docker run -d \
  --name rememory \
  -p 8080:8080 \
  -v rememory-data:/data \
  ghcr.io/eljojo/rememory:latest

# Nix
nix run github:eljojo/rememory