Health · AI · Payments

SwipeHealth

A subscription health platform with an AI data layer.

Role · Lead Engineer & ArchitectYear · 2025

1 ledger

unified Stripe (web) + RevenueCat (mobile)

01 — The problem

Subscriptions split across Stripe on web and RevenueCat on mobile drift out of sync, and billing edge cases multiply with every platform.

02 — The decision

One unified subscription model as the single source of truth; every webhook reconciles back to it. Async jobs absorb the edge cases instead of the request path.

03 — Architecture

client

Web app

Next.js on Amplify

client

Mobile app

external

Clerk

auth

service

NestJS API

ECS

queue

BullMQ

async jobs

LLM pipelines

extract · validate · enrich

external

Stripe

web billing

data

Subscription ledger

single source of truth

external

RevenueCat

mobile billing

React Flow

AWS via Pulumi: ECS · ECR · VPC · CloudFront + S3 · bastion accesshovertap a node to trace it · drag to rearrange

Unified subscription architecture spanning Stripe + RevenueCat
Webhook handling across the full payment lifecycle
BullMQ async jobs; LLM pipelines for data extraction, validation, and enrichment
Clerk auth; Next.js on AWS Amplify, backend APIs on ECS with images in ECR
Pulumi (TypeScript) infrastructure: VPC, CloudFront + S3, and bastion-host access

04 — Outcome

Payment state stays consistent across web and mobile, while LLM pipelines clean and enrich data automatically.

Stack

NestJSNXNextJSStripeRevenueCatBullMQClerkAWS ECSPulumi

NextSuprahuman→