PharmaRockIT - Multi-tenant Pharma Platform

Architected a secure, multi-tenant pharmaceutical platform on AWS - and hired the team that built it.

Client: APS Compliance Consultants
Industry: Pharma / life sciences
Role: Technical Lead & architect
Timeline: Jul 2020 - Dec 2025

5engineers

hired, onboarded and led

5½years

from ALLEYE to PharmaRockIT

3modules

admin panel, LIMS, e-workbook (planned)

Context

A suite of compliance applications for pharmaceutical companies: admin panel, LIMS (laboratory information management) and planned electronic workbook modules. It started with ALLEYE, a CMMS for instrument validation, built from scratch.

Leadership

I hired and onboarded the team, owned technical decisions and mentoring, and took part in UX design to align the architecture with user needs.

Architecture · fig. 02

fig. 02 - multi-tenant platform on AWS

01 Modules
- Admin panel
- LIMS
- e-Workbookplanned
02 Front endReact + TypeScriptMaterial UI
03 API · multi-tenantASP.NET 8serverless on AWS Lambda
04 Data
- PostgreSQLRDS
- RedisRDS
- S3
05 AccessIAMFargate for long-running work

Infrastructure as codeReusable Terraform modules across multiple repositories
CI/CDAzure DevOps pipelines
ALLEYE phase · 2020ASP.NET Core + React + SQL Server on dockerized AWS ECS

01 ModulesAdmin panel · LIMS · e-Workbooke-Workbook planned
02 Front endReact + TypeScriptMaterial UI
03 API · multi-tenantASP.NET 8serverless on AWS Lambda
04 DataPostgreSQL · Redis · S3PostgreSQL and Redis on RDS
05 AccessIAMFargate for long-running work

What I built

Secure, scalable multi-tenant architecture on AWS, designed for an admin panel, LIMS and future electronic workbook modules.
ASP.NET 8 serverless APIs on AWS Lambda; PostgreSQL and Redis on RDS; IAM, S3 and Fargate.
Reusable Terraform modules across repositories; CI/CD with Azure DevOps.
React + TypeScript + Material UI front ends.
ALLEYE: audit trail, role/permission-based auth (ASP.NET Identity + JWT), Hangfire recurring jobs, inactivity lockout, automated deployments.

In the product

Template builder with a component palette, a standard-weight field's range and workbook links, and the method's workflow steps — fig. 03e-Workbook template builder - A design for the planned e-Workbook module: a method author builds the template from components, sets acceptable ranges and links fields to cells in the calculation workbook.

Experiment execution screen with the step list, a sample-preparation step, linked workbook cells and an out-of-range error — fig. 04Experiment execution - Analysts work through the method step by step; values flow to the linked workbook cells, and an out-of-range weight blocks the step until it's corrected.

Change history listing step events by time, including an edited sample weight with its reason; names are blurred — fig. 05Change history - Every step start, completion and edit is logged; an edited value keeps the old value and the reason for the change.

Experiment step list with three parallel sample preparations, one in progress, and two locked steps — fig. 04Experiment steps - From the execution design: parallel sample preparations, and later steps locked until the steps they wait for are done.Show full screen ↗

Outcomes & role

My most significant accomplishment: a platform architected end to end, and the team that built it.
A team of 5 developers hired and onboarded from scratch.

Technical Lead and architect - architecture, hiring, mentoring and technical decisions, plus hands-on work across the stack.

C#
ASP.NET 8
AWS Lambda
Fargate
RDS (PostgreSQL)
Redis
S3
IAM
Terraform
Azure DevOps
React
TypeScript
Material UI
Docker

Stack

C#
ASP.NET 8
AWS Lambda
Fargate
RDS (PostgreSQL)
Redis
S3
IAM
Terraform
Azure DevOps
React
TypeScript
Material UI
Docker

NextNext case study - 01AI Underwriting PlatformExcedr · Solutions Architect & sole engineer · 2026