Technology Stack

Layer Technology Why we chose it
Frontend React + TypeScript Industry-standard modern frontend. Capgemini has deep experience delivering React applications. Gives us a clean, fast UI for both Owners and Next of Kin with excellent long-term maintainability.
Backend Java + Spring Boot Capgemini’s strongest and most common enterprise backend stack. Extremely well understood by their teams, battle-tested at scale, and easy for them to support and extend.
Database PostgreSQL on Amazon RDS The most widely adopted serious open-source relational database. Capgemini teams know it thoroughly. RDS gives us automated backups, scaling, security patching and high availability with almost no operational overhead.
Primary Storage Amazon S3 The default, most reliable object storage on AWS. Zero learning curve for Capgemini, extremely durable, cheap for our small encrypted payloads, and simple to integrate.
Permanent Backup Filecoin (FilOne or Lighthouse) Provides a decentralised, long-term copy of every encrypted Message plus a CID. Gives real survival capability if KinPhrase the company ever disappears, while still being manageable via an S3-compatible or simple API.
Authentication Amazon Cognito (Email + Password + 2FA) AWS-native, production-grade user management. Handles sign-up, login, password resets and two-factor authentication securely. Capgemini implements and runs Cognito regularly, keeping risk and complexity low.
Email AWS SES or Resend Reliable transactional email for Dead-Man Switch check-ins and Next of Kin notifications. SES is native AWS; Resend is a strong modern alternative if preferred.
Message Encryption AES-256-GCM + Argon2id (client-side) Encrypts the actual Message content on the Owner’s device before it is uploaded. This is the core protection for the data itself. KinPhrase never sees plaintext.
Quantum-Resistant Key Protection Hybrid ML-KEM (NIST FIPS 203) + AES-256 (client-side) After the Message is encrypted with AES-256, the AES key itself is protected using ML-KEM. This is the post-quantum layer. It can be enabled from day one or shortly after launch and does not change the user experience or Secret Key format.
Cloud Platform Amazon AWS Capgemini’s primary cloud platform. Using pure AWS keeps infrastructure, security, compliance and handover as simple as possible.
Recovery Tool Static open-source page (GitHub + IPFS) A lightweight recovery interface that can work even if KinPhrase’s servers no longer exist. Hosted independently so Next of Kin retain a path to their Message.

Technical Points

Dual Storage for KinPhrase (S3 + Filecoin/IPFS)

Goal

Every encrypted KinPhrase must be stored in two places at launch:

  1. Amazon S3 — primary, fast, familiar
  2. Filecoin / IPFS (via FilOne or Lighthouse) — permanent / decentralised copy

This allows normal recovery to be fast while still giving a real survival path if KinPhrase the company ever disappears.

High-Level Flow

  1. Owner saves or updates their KinPhrase in the browser.
  2. Browser encrypts the message client-side (AES-256-GCM + Argon2id).
  3. Encrypted blob is sent to our backend.
  4. Backend performs two uploads in parallel:
  5. Backend stores both references against the Account Number:
  6. Normal recovery (while we are live) serves the file from S3.
  7. Open-source recovery tool uses the CID and fetches directly from IPFS/Filecoin.

Effort Estimate

Task Effort Notes
Abstract the storage layer Low–Medium Create a simple storage interface so the rest of the code does not care about the underlying provider
S3 integration Low Standard AWS SDK – Capgemini already knows this well
Filecoin/IPFS integration (FilOne or Lighthouse) Medium Use their official SDK/API. Single upload call after encryption
Save both S3 key + CID against Account Number Low Two extra fields in the database
Open-source recovery tool that reads from CID Medium Static page that takes CID + Account Number + Secret Key and decrypts client-side
Dual-write testing & fallback behaviour Medium Ensure one failure does not block the other
Monitoring & alerting Low–Medium Alert if Filecoin uploads start failing
Total estimated extra effort 1.5 – 3 weeks Assuming one experienced backend developer