Competitive Analysis
The industry is still selling digital filing cabinets.
We built a sovereign estate protocol.
Heir Tight, Everplans, and Estateably organise files and share links. Legacy Vault Protocol anchors proof, enforces multi-party release conditions, and writes every event to an immutable chain. These are not the same product category.
What the competition offers
Heir Tight
$0 – $11.99/moVirtual vault for documents
- •Centralized cloud file storage
- •Folder sharing via email
- •10 MB max file size (Plus plan)
- •5 GB total storage (Plus plan)
- •HIPAA-compliant claim
- •"Bank-grade" E2EE (unverified)
- •No blockchain, no audit trail
- •No release protocol
- •No identity verification
- •No guardian quorum
A Dropbox for estate documents. Nothing more.
Everplans
Free + PremiumLife organizer with estate docs
- •Consumer life-organisation app
- •HIPAA + SOC 2 certified
- •Reminders and article content
- •Deputy access sharing
- •Centralized cloud storage
- •No cryptographic proof
- •No blockchain, no audit trail
- •No release protocol
- •No wallet / crypto asset support
- •No identity assurance (IAL)
A well-designed digital binder. No protocol layer.
Estateably
Enterprise (B2B)Probate workflow for attorneys
- •Probate & trust administration tool
- •SOC 2 Type II certified
- •3,000+ court-approved forms
- •AI-driven workflow automation
- •Fiduciary accounting + reporting
- •For attorneys & trust officers
- •Not a consumer vault product
- •No blockchain anchoring
- •No public wallet registry
- •No consumer guardian quorum
Excellent for law firms. Wrong category for consumers.
Why Legacy Vault Protocol is different
8 pillars no one else has
Cryptographic Trust
Every document is encrypted with AES-256-GCM before it leaves your device. The server never sees plaintext. CIDs, hashes, and policy references are all that live in the database.
Blockchain-Anchored
Vault registration, manifest updates, and status transitions are written to a private chain. No competitor anchors audit events on-chain — that's a fundamental architectural difference.
Private IPFS
Documents live on a private swarm-keyed IPFS node, not in a vendor's S3 bucket. Content-addressed storage means tamper-proof retrieval — the CID is the proof.
Guardian Quorum
N-of-M guardian approval before any release. No single person — executor, attorney, or beneficiary — can force a release unilaterally. This is unmatched in the consumer estate space.
Multi-Proof Release
Five conditions must be simultaneously satisfied: identity verification, death proof, attorney attestation, guardian quorum, and waiting period. Each is cryptographically recorded.
W3C Identity Standards
DIDs and Verifiable Credentials (VC 2.0) for executor and attorney authority. NIST SP 800-63-4 IAL 2/3 required for release-critical roles. No competitor operates at this level.
14-Model Data Architecture
14 purpose-built Prisma models covering 6 user roles, 10 asset categories, 13 document types, 22 audit actions, and 9 claim states. Not a generic file tree.
Built for What's Next
Crypto wallets, multi-chain assets, DID-based identity, on-chain governance — Legacy Vault Protocol is architected for the digital asset era, not the era of scanned PDFs.
Feature Matrix
Side-by-side: every feature that matters
| Feature | Legacy Vault Protocol | Heir Tight | Everplans | Estateably |
|---|---|---|---|---|
| Architecture | ||||
| Storage layer | Private IPFS (content-addressed) | Centralized cloud | Centralized cloud | Centralized cloud |
| Immutable audit registry | Activity log only | |||
| Private blockchain anchoring | ||||
| Self-hostable / operator-owned nodes | ||||
| Open protocol (not SaaS lock-in) | ||||
| Encryption & Security | ||||
| AES-256-GCM per-vault encryption | E2EE claimed | At-rest | At-rest + TLS | |
| Zero server-knowledge (encrypt before upload) | ||||
| Content-hash integrity verification (SHA-256) | ||||
| SOC 2 Type II | Roadmap | |||
| HIPAA compliant | Roadmap | |||
| Identity & Access | ||||
| W3C DID + Verifiable Credentials (VC 2.0) | ||||
| NIST SP 800-63-4 IAL 2/3 identity assurance | ||||
| Role-scoped access (owner / executor / attorney / beneficiary / guardian / auditor) | 6 distinct roles | Owner + shared contacts | Owner + deputies | Attorney + staff roles |
| Cryptographic proof of executor authority | ||||
| Estate Release Protocol | ||||
| Multi-proof release engine (5 conditions) | ||||
| Death certificate upload + cryptographic hash | ||||
| Attorney / notary attestation workflow | Probate only | |||
| Guardian N-of-M quorum approval | ||||
| Configurable waiting / dispute period | ||||
| Dispute filing with on-chain evidence | ||||
| RUFADAA-aligned fiduciary access model | Awareness only | |||
| Asset Coverage | ||||
| Public blockchain wallet registry (ETH, SOL, XRPL…) | ||||
| 10 asset categories (crypto, real estate, business equity…) | Generic folders | Financial accounts | ||
| 13 document types (will, trust, deed, advance directive…) | Generic files | Guided categories | ||
| Zero private key / seed phrase collection (by design) | ||||
| Data Integrity | ||||
| Append-only tamper-evident audit log | Activity feed | |||
| Manifest versioning with hash verification | ||||
| On-chain event anchoring for audit events | ||||
| Storage Model | ||||
| No arbitrary file size caps | ||||
| No file count caps | ||||
| Content-addressed (CID — not filename-based) | ||||
| Technology | ||||
| Built on Web3-native standards | ||||
| Fully typed TypeScript / Next.js 15 App Router | ||||
| 33-test verified, production build clean | Unknown | Unknown | Unknown | |
Competitor features sourced from public documentation. "Partial" denotes partial or claimed (not independently verified) coverage. Legacy Vault Protocol features reflect the open-source production build.
The gap is not incremental — it is architectural
What they built
- Cloud file storage with a folder tree
- Email-based sharing with access controls
- Centralized databases vulnerable to single-point failure
- Manual processes with no enforcement mechanism
- Trust based on the vendor's word ("bank-grade" with no proof)
- Release triggered by whoever has login credentials
What we built
- Encrypted blobs on private IPFS — the CID is the proof
- W3C DIDs + Verifiable Credentials for cryptographic authority
- Private chain registry — every state change is immutable
- 5-condition release engine enforced in code, not policy
- SHA-256 manifest hashing — tamper is mathematically detectable
- Release requires death proof + attorney + quorum + waiting period
Ready for a vault that proves itself?
Your estate deserves cryptographic certainty.
The competitors sell peace of mind. Legacy Vault Protocol delivers mathematically verifiable proof — on an immutable chain, encrypted before it leaves your hands.