Separate access by role
Admin, Student, and Assistant experiences are isolated across dedicated subdomains and permission boundaries.
Selected work
Featured software case study
AHLC
A production academic platform designed around role separation, transactional integrity, and dependable operation.
RoleLead Developer & Architect
SystemMulti-tenant web platform
FocusArchitecture + operations
StatusPrivate production system
Protect important workflows
Academic evaluations and tuition-fee processing are designed around reliable session and transaction handling.
Operate the full stack
Application code, databases, caching, containers, reverse proxying, and Cloudflare are treated as one system.
System record
The system problem
An academic platform serves people with very different permissions and responsibilities. Students need dependable access to learning and payment workflows. Assistants need constrained academic tools. Administrators need operational control. The architecture has to make those boundaries explicit without turning the system into disconnected products.
Three dedicated portals
Role-specific subdomains reduce ambiguity and support clearer privilege segregation.
PostgreSQL + Redis
Persistent records and fast session or cache state serve different responsibilities.
Containerized services
Docker provides repeatable environments and isolates application services.
Caddy + Cloudflare
The public edge and reverse proxy limit direct service exposure and organize secure traffic flow.
What this project demonstrates
AHLC is evidence of end-to-end ownership: translating user roles into system boundaries, building application workflows, selecting infrastructure, deploying services, and maintaining the production environment. Because the platform is private, the case study focuses on verified architectural decisions rather than exposing code or operational data.