Documentation
Aegis DMS alpha: legacy-release infrastructure for self-hosters, families, and future platform integrations.
Overview
Aegis DMS is a dead man's switch system for digital legacy. It monitors that you are still active and, if you stop checking in, releases pre-configured information to designated contacts.
Use cases include: distributing passwords and account access to family, notifying executors of estate details, or delivering sensitive instructions that should only be shared after your death or incapacitation.
Aegis is in alpha. All pricing is a placeholder. Do not rely on it for legally binding document delivery.
Products
Aegis Hosted
Fully managed · No server required
A complete managed service for non-technical users. Aegis Hosted handles storage, switch monitoring, and contact notification. Release material is encrypted server-side, so you are trusting Aegis with server-managed encryption in v1.
Aegis Relay
SaaS add-on · For self-hosters
Heartbeat monitoring for a self-hosted Aegis Core instance. Relay detects missed check-ins and can alert you. Monitoring alone does not release estate material; Relay Escrow must be explicitly configured before it can hold material or start a release.
Aegis Core
Planned open-source package · AGPL-3.0
The self-hosted Aegis Core package is planned under AGPL-3.0 but is not published in this alpha release. When available, it will let you manage legacy-release data on infrastructure you control; Relay will remain optional.
DeadDrop API
Coming soon · Platform layer
A future infrastructure API for developers and platforms who want to build legacy-release functionality into their own products. Not yet available, and design is in progress.
Key Concepts
Dead man's switch
A mechanism that triggers an action when you stop actively preventing it. Aegis requires periodic check-ins. If you miss your window, it considers you incapacitated and begins the release process.
Release runs
A release run is the event where Aegis delivers your estate information to your contacts. Only one active release run can exist per account at a time. Release runs are irreversible once contacts have been notified.
Estate items
Structured records of your digital assets and accounts, including access credentials, important locations, and executor notes. Estate items are encrypted at rest.
Contacts
Trusted recipients who receive your release material. Contacts receive a claim link through a configured, verified email or Telegram channel and must verify their identity before accessing your estate information.
Relay Monitoring vs Relay Escrow
Relay Monitoring tracks heartbeats from your self-hosted Aegis Core instance. Relay Escrow holds release material on your behalf for delivery when a trigger fires. These are distinct features: monitoring alone does not release anything.
Getting Started
Aegis Hosted
- Create an account at /register
- Complete the onboarding flow: choose Hosted, review the trust model, and acknowledge it
- Add at least one contact and one estate item
- Enable your dead man's switch and set a check-in interval
- Check in regularly to prevent a release run from triggering
Aegis Relay (self-hosters)
The public Aegis Core package is not available in this alpha release. These steps apply to an existing/private Core deployment or become actionable when the package is published.
- Use an existing/private Aegis Core deployment, or wait for the public package
- Create an account and subscribe to the Relay plan
- Generate an API key in your Aegis Core instance
- Connect Core to Relay via the Relay settings panel
- Send a test heartbeat to confirm the connection
Security Model
All PII fields (names, emails, account details, executor notes) are encrypted at rest using AES-256-GCM. Audit logs never contain plaintext PII. Passwords are hashed with Argon2id. Password reset tokens are SHA-256 hashed and single-use with a 15-minute expiry.
Sessions use HttpOnly cookies with SameSite=Lax. CSRF protection is required on all state-changing requests. Rate limiting applies to auth endpoints.
For Aegis Hosted v1, encryption keys are server-managed. There is no client-side or zero-knowledge encryption in v1. The planned Aegis Core package is intended for deployments that need full key control, but it is not published in this alpha release.
Trust & Limitations
Aegis is in alpha. We do not claim:
- Guaranteed delivery, because email delivery depends on third-party infrastructure
- Legal equivalence to a will or estate document
- Zero-knowledge encryption, since Hosted v1 uses server-managed keys
- Bank-level security, though we apply reasonable security practices for an alpha product
- Shamir secret sharing, which is not implemented
Aegis is infrastructure. It does not provide legal, financial, or estate-planning advice. Consult a professional for legally binding arrangements.