Overview

Inheribase follows a four-step process: Seal, Assign, Monitor, Deliver. Each step builds on the last to create a complete digital inheritance system.

┌─────────────┐    ┌─────────────┐    ┌─────────────┐    ┌─────────────┐
│   1. SEAL   │───▶│  2. ASSIGN  │───▶│ 3. MONITOR  │───▶│ 4. DELIVER  │
│             │    │             │    │             │    │             │
│ Encrypt &   │    │ Guardians & │    │ Liveness    │    │ Heirs claim │
│ store your  │    │ heirs are   │    │ pulse keeps │    │ decrypted   │
│ assets      │    │ designated  │    │ vault active│    │ vault       │
└─────────────┘    └─────────────┘    └─────────────┘    └─────────────┘

Step 1: Seal Your Assets

Upload files through the Digital Airlock. Encryption happens entirely on your device before anything is transmitted.

Your Device                          Inheribase                  Arweave
    │                                   │                          │
    │  [1] Select files to upload       │                          │
    │  [2] AES-256-GCM encrypts         │                          │
    │      locally in your browser      │                          │
    │                                   │                          │
    │  ── encrypted blob ──────────────▶│                          │
    │                                   │  ── persist to ─────────▶│
    │  ◀── Instant Temporary Cache ───  │     permaweb             │
    │                                   │  ◀── TXID ─────────────│
    │  ◀── Arweave TXID (Later) ──────  │                          │
    ▼                                   ▼                          ▼
  Keys stay                        Never sees                 Stores encrypted
  on your device                   unencrypted data           data permanently

What happens:

Your files are encrypted with AES-256-GCM using keys derived from your credentials
Only encrypted data leaves your device
Fast UX Cache: Files are temporarily buffered in a highly available backend (Supabase) to complete your upload instantly.
Permanent Settlement: Concurrently, data is pushed to Arweave (200-year endowment). Once confirmed, the file state upgrades from temporary to permanent.
You receive an Arweave Transaction ID (TXID) as proof of permanent storage
Vault Credits are consumed based on file size ($96.50/GB)

Step 2: Assign Your People

Designate the trusted contacts who will participate in your estate plan.

                        ┌──────────────┐
                        │  VAULT OWNER │
                        │   (You)      │
                        └──────┬───────┘
                                │
                 ┌─────────────┴─────────────┐
                 │                           │
          ┌──────▼──────┐            ┌───────▼──────┐
          │  GUARDIANS  │            │    HEIRS     │
          │             │            │              │
          │ Hold key    │            │ Receive      │
          │ fragments   │            │ vault on     │
          │ (shares)    │            │ release      │
          └──────┬──────┘            └──────────────┘
                 │
    ┌────────────┼────────────┐
    │            │            │
  ┌──▼──┐     ┌──▼──┐     ┌──▼──┐
  │Share│     │Share│     │Share│
  │ 1/3 │     │ 2/3 │     │ 3/3 │
  └─────┘     └─────┘     └─────┘

 Any 2 of 3 shares can reconstruct the key

Guardians protect your vault through Shamir's Secret Sharing:

Your vault key is split into fragments (shares)
Each guardian receives one share via secure email invitation
No single guardian can access your vault alone
Choose Standard (2-of-3) or Enhanced (3-of-5) threshold presets

Heirs are your designated recipients:

Add up to 5 heirs by name and email
Heirs are not notified of their designation until release
All heirs receive full access to the entire vault upon release

Step 3: Monitor Your Pulse

Inheribase passively monitors your activity to distinguish between a temporary absence and a succession event.

  You ──── check in ────▶ Timer resets ──── ✓ Vault stays active
   │
   │ (miss check-in)
   │
   ▼
 Quiescence detected
   │
    ├── Day 0:  Alert sent to owner (email, push)
    ├── Day 3:  Second alert
    ├── Day 7:  Guardians notified to stand by
    ├── Day 14: Third escalation to owner
    ├── Day 21: Fourth escalation
    ├── Day 28: Final warning
    ├── Day 30: Contestation window closes
    │
    ▼
  Release sequence begins

How liveness is tracked:

Any authenticated action (dashboard login, upload, API call, MCP check-in) resets the timer
Configurable check-in cadence: weekly, bi-weekly, monthly, or quarterly
30-day contestation window with escalating alerts before any data is released
One-click cancellation during the contestation period

Step 4: Deliver to Heirs

When release conditions are met and the contestation period has elapsed, your heirs claim their inheritance.

  Release triggered
        │
        ▼
  ┌─────────────────────────────────────┐
  │  30-DAY CONTESTATION PERIOD         │
  │                                     │
  │  Owner can cancel at any time       │
  │  Multiple alerts sent               │
  │  No data released yet               │
  └─────────────────┬───────────────────┘
                    │ (owner does not cancel)
                    ▼
  ┌─────────────────────────────────────┐
  │  HEIR NOTIFICATION                  │
  │                                     │
  │  Secure claim links sent to heirs   │
  │  Heirs verify identity via email    │
  │  Heirs create their own passkeys    │
  └─────────────────┬───────────────────┘
                    │
                    ▼
  ┌─────────────────────────────────────┐
  │  KEY RECONSTRUCTION                 │
  │                                     │
  │  Guardian shares are assembled      │
  │  Vault key is reconstructed (SSS)   │
  │  Assets are decrypted               │
  └─────────────────┬───────────────────┘
                    │
                    ▼
  ┌─────────────────────────────────────┐
  │  VAULT ACCESS GRANTED               │
  │                                     │
  │  Heirs download decrypted files     │
  │  Full access to all vault contents  │
  │  Audit trail preserved on-chain     │
  └─────────────────────────────────────┘

Why Inheribase vs. Alternatives

Feature	Traditional Dead Man's Switch	Cloud Storage + Shared Password	Inheribase
Encryption	Varies	Provider holds keys	Zero-knowledge, client-side
Persistence	Depends on platform survival	Subscription-dependent	200-year Arweave endowment
Trigger mechanism	Must actively re-sign periodically	No automated trigger	Configurable with grace period
Key management	Single point of failure	Password can be guessed/stolen	Shamir's Secret Sharing (M-of-N)
Heir experience	Complex, technical	Requires knowing the password	Guided claim process via email
Cost model	Volatile crypto tokens	Monthly subscription	Pay-as-you-go, credits never expire

The Complete Lifecycle

┌──────────────────────────────────────────────────────────────────────┐
│                        YOUR LIFETIME                                 │
│                                                                      │
│  Create vault ─▶ Upload assets ─▶ Assign people ─▶ Set trigger      │
│       │                                                │             │
│       │         ◀── periodic check-ins ──▶            │             │
│       │                                                │             │
│       └── Modify guardians, heirs, triggers anytime ──┘             │
│                                                                      │
├──────────────────────────────────────────────────────────────────────┤
│                        TRANSITION                                    │
│                                                                      │
│  Trigger fires ─▶ 30-day contestation ─▶ Heir notification          │
│                                                                      │
├──────────────────────────────────────────────────────────────────────┤
│                        SUCCESSION                                    │
│                                                                      │
│  Guardian shares assembled ─▶ Key reconstructed ─▶ Heirs access     │
│                                                                      │
└──────────────────────────────────────────────────────────────────────┘

Get Started — Set up your first vault in 10 minutes
Guardians — How guardian key sharing works
Release & Monitoring — Configure when your vault releases
Pricing — Understand the cost model

Overview

On this page