Prevault
Present Product
Overview

Product Ecosystem

One Secure Platform.
Multiple Connected Layers.

The architecture behind PREVAULT — how the mobile application, secure services, data layer and administrative operations connect, and where the boundaries of private health content are enforced.

Architecture

Layered platform

Mobile Application

  • iOS
  • Android
  • Offline-safe UI state

Authentication

  • Token issue & refresh
  • Biometric unlock
  • PIN app lock
  • Session revocation

API Gateway / Backend

  • Request validation
  • Rate limiting
  • Per-user authorization
  • Audit emission

Core Services

  • User Service
  • Family Service
  • Document Service
  • Prescription Service
  • Search Service
  • Subscription Service
  • Notification Service
  • OCR Service

Data Layer

  • PostgreSQL
  • Secure Object Storage
  • Encrypted at rest
  • Scoped, expiring access

Operations

  • Admin Platform
  • Monitoring
  • Audit Logs
  • Backups

Boundaries

Where private health content stops

Administrative roles operate on account, billing and system data. Document contents remain outside routine operational access.

User-scoped data access

Every document read is authorized against the owning account and the assigned family member.

No public object URLs

Files are retrieved through short-lived, scoped access — never via a permanent public link.

Operational, not clinical

Admin surfaces expose counts, states and errors. Medical content is shielded by design.

Tech Stack

Selected technologies

Mobile

Flutter

Backend

Node.js / NestJS

Database

PostgreSQL

Cloud

AWS

Authentication

AWS Cognito or equivalent

Search

PostgreSQL FTS / OpenSearch

Admin

React / Next.js

Billing

Apple IAP / Google Play Billing

Notifications

FCM / APNs

OCR

Secure provider integration

Analytics

Privacy-conscious analytics

Environments

Separated, all the way to production

Production health data is not routinely copied into development. Everything shown in this portal is synthetic demo data.

01

Development

Feature branches, synthetic data, rapid iteration.

Synthetic data
02

Staging / UAT

Release candidates for founder acceptance cycles.

Synthetic data
03

Production

Live accounts, restricted access, monitored and backed up.

Real data

Cloud, region and provider selections are confirmed during technical architecture sign-off.

CURRENT PROJECT