Case StudyJan 15, 20248 min read

How We Scaled a HealthTech Startup to 1M+ Users

AM
Ali Mughal

Founder & CEO

How We Scaled a HealthTech Startup to 1M+ Users
#HealthTech#Scaling#Microservices#HIPAA#AWS

In 2022, a fast-growing HealthTech startup came to NexaSoftAI with an ambitious mission: making quality healthcare accessible to underserved communities at scale. Their product was gaining traction rapidly — but their infrastructure was not keeping up. This is the story of how we helped them scale from 100,000 to over 1 million active users while maintaining full HIPAA compliance and sub-200ms response times.

The Challenge

The startup's platform was a monolithic Rails application backed by a single PostgreSQL instance. It had served them well during early validation, but as their user base grew, the cracks became impossible to ignore. Database locks were causing appointment booking failures during peak hours. Response times were climbing past 3 seconds. And their manual compliance processes were creating serious audit exposure as regulatory scrutiny increased.

They were growing 40% month-over-month. Without intervention, their infrastructure would not survive the next two quarters.

Our Approach

NexaSoftAI began with a comprehensive architecture and compliance audit. Within the first two weeks, we had a clear picture of the technical debt, the failure points, and the compliance gaps. We designed a three-phase program: stabilize the existing system, migrate to a microservices architecture, and embed HIPAA compliance into every layer of the new platform.

Phase 1: Stabilization (Months 1–2)

Before we could rebuild, we needed to stop the degradation. We implemented a Redis caching layer for session management and frequently accessed patient data, introduced database read replicas to offload reporting queries, and deployed horizontal scaling with an application load balancer. Average response time dropped from 3.2 seconds to under 700ms within six weeks — without touching the core architecture.

Phase 2: Microservices Migration (Months 3–8)

Using a strangler fig pattern, we incrementally extracted services from the monolith while keeping the existing platform fully operational. Key services we built included:

  • Patient Identity Service: Built in Node.js, handling authentication, profile management, and consent tracking with full audit logging.
  • Appointment Service: A Python and FastAPI service managing scheduling logic, provider availability, and real-time slot allocation for thousands of concurrent users.
  • Medical Records Service: A secure document service with end-to-end encryption, granular access controls, and immutable audit trails for every record access event.
  • Notification Service: An AWS Lambda-based service delivering appointment reminders, care plan updates, and system alerts via SMS, email, and push — at scale and at near-zero marginal cost.

Phase 3: HIPAA Compliance by Design (Months 5–8)

Healthcare data demands the highest security standards, and compliance cannot be retrofitted. We embedded HIPAA controls into the architecture itself: end-to-end encryption for all protected health information at rest and in transit, role-based access control with least-privilege enforcement, comprehensive audit logging for every data access event, and automated security scanning integrated into the CI/CD pipeline. Compliance became a property of the system, not a process layered on top of it.

Technical Highlights

Performance at Scale

Our target was sub-200ms response times at the 95th percentile under full production load. To achieve this, we implemented GraphQL for efficient, client-driven data fetching, a CDN for static assets and cacheable API responses, database connection pooling, and query optimization across all high-frequency data access patterns. We validated performance targets with load testing at 3x projected peak traffic before every phase cutover.

Observability Infrastructure

We deployed a full observability stack — metrics, logs, and distributed traces — across every service from day one. Custom dashboards gave the clinical operations team real-time visibility into appointment volume, system health, and patient experience metrics. On-call incident volume dropped by 65% within the first month of the new platform going live.

The Results

  • 10x user growth: Platform scaled from 100,000 to 1 million+ active users
  • 99.99% uptime: Four nines reliability sustained across the observation period
  • 150ms average response time: Down from over 3 seconds at peak
  • Zero security incidents: Full HIPAA compliance maintained throughout
  • 40% infrastructure cost reduction: Despite 10x growth in traffic
  • 50,000+ daily appointments: Processed without performance degradation

Key Lessons

1. Stabilize before you migrate. Attempting a major architectural migration on an unstable system dramatically increases risk. Establishing a performance baseline first gave us confidence and gave the business continuity during the transition.

2. Compliance is an engineering problem. When security and HIPAA controls are automated and enforced at the infrastructure level, they stop being a bottleneck and become a durable competitive advantage in regulated markets.

3. Observability is not optional. The investment in a full observability stack paid for itself within weeks through faster incident resolution and proactive issue detection before they reached patients.

What's Next

The startup is now expanding into three new markets. NexaSoftAI continues to partner with their engineering team on AI-powered diagnostic assistance tools, predictive health analytics, and a provider network platform designed to support tens of thousands of clinicians.

AM

Written by Ali Mughal

Founder & CEO · NexaSoftAI

Ali Mughal is the Founder & CEO of NexaSoftAI. He has led engineering strategy for startups across FinTech, HealthTech, and SaaS — from seed-stage MVPs through Series A.

Insights that drive growth

Get the latest on AI, strategy, and engineering delivered to your inbox once a month.