Case Study // Enterprise System•Software Developer (KeyAbroad Consultants)

KeyAbroad 2.0

Educational Consultancy Operations Platform & Student Application Engine

Endpoint Telemetry: /admin/applications/dossier-review
ACTIVE RUNTIME CONTEXT

monorepo=TURBO • playwright=PASSING • signed_url=EXP_900S

Status: Internal Production • Category: Enterprise System
Executive Overview

KeyAbroad 2.0 modernized core operational workflows at KeyAbroad Consultants (Faisalabad, Pakistan). It transitioned admissions counselors and compliance officers from fragmented spreadsheets to a centralized, auditable case management ecosystem.

Problem Addressed

International educational admissions demand strict adherence to university intake deadlines, language proficiency minimums, and visa documentation. Handling student credentials across WhatsApp and spreadsheets created serious data leak risks and delayed filings.

Target Users & Real Use Case

Educational counselors, compliance officers, branch managers, and international university applicants.

My Role & Engineering Contributions
  • Architected the monorepo structure using Turborepo to unify student application forms and internal counselor portals.
  • Designed Supabase relational schema migrations covering students, university dossiers, and verification stages.
  • Constructed encrypted document storage integration with cryptographic signed URLs expiring in 15 minutes.
  • Wrote automated end-to-end Playwright tests verifying the application progression pipeline.
  • Created OpenAPI 3.0 route documentation and structured deployment configurations.
Technical Stack & Framework Breakdown
Monorepo & Build System
Turborepo (turbo.json)npm workspacesapps/ and packages/ architecture
Frontend & Portals
Next.js App RouterReactTypeScriptTailwind CSS
Backend & Data Storage
Supabase Auth & StoragePostgreSQL databaseSupabase MigrationsOpenAPI 3.0
Quality Assurance & Testing
Playwright E2E SuiteAutomated Test Results Reporter
Architecture Blueprint & System Topology

KeyAbroad 2.0 System Architecture

A Turborepo monorepo separating student intake web applications from administrative counselor dashboards, sharing core TypeScript types, validation logic, and Supabase client bindings.

Legend:
Verified / Current Component
Planned / Roadmap Component

01. Monorepo Frontend Applications

Distinct web applications within apps/ sharing centralized design tokens.

Tier 1
Student Intake PortalCurrent

Public-facing application flow for students to register and upload transcripts

Next.js App Router
Counselor Operations DashboardCurrent

Internal portal for admissions staff to review dossiers and assign university matches

Next.js + Tailwind CSS
Shared UI & Validation PackageCurrent

Monorepo library for shared forms, validation schemas, and types

packages/ui & packages/types

02. Backend Services & Access Control

Supabase authentication and documented RESTful API endpoints.

Tier 2
Role-Based Auth MiddlewareCurrent

Separates counselor, manager, and student access boundaries

Supabase Auth
OpenAPI Service LayerCurrent

Formally documented route interface for applicant mutations and stage tracking

openapi.json specification

03. Secure Storage & Database

PostgreSQL relational persistence and secure object storage.

Tier 3
Encrypted Document VaultCurrent

Stores academic transcripts, bank letters, and passports with signed URL access

Supabase Storage (Signed URLs)
Relational Application DatabaseCurrent

PostgreSQL storing student dossiers, intake deadlines, and counselor audit trails

PostgreSQL + Migrations
Verified Components in Repository (5)
  • Turborepo monorepo setup
  • Playwright automated E2E test suite
  • Supabase schema and migrations
  • OpenAPI specification
  • Secure document upload workflows
Documented Future Roadmap (2)
  • Automated WhatsApp Business status notifications
  • Automated university portal scraping engine
Key Engineering Decisions & Architectural Trade-offs

#1: Turborepo Monorepo Architecture for Portal Separation

Decision Record
Context & Constraints

Counselors and students required drastically different interfaces, yet needed identical data models and validation logic.

Architectural Decision

Structured the codebase as a Turborepo monorepo with apps/ (intake app and admin dashboard) and packages/ (shared types, UI tokens, and validation schemas).

Trade-offs Accepted

Increased initial configuration complexity, but eliminated code duplication and guaranteed synchronized API contracts.

Evidence: Verified by presence of turbo.json, apps/, and packages/ in the GitHub repository (ranairtaza/Keyabroad).

#2: Time-Limited Cryptographic Signed URLs for Sensitive Documents

Decision Record
Context & Constraints

Transcripts, financial affidavits, and passport scans are confidential and must never be exposed via public static URLs.

Architectural Decision

Stored files in private storage buckets and generated short-lived (900-second) HMAC signed URLs exclusively upon authenticated staff request.

Trade-offs Accepted

Requires requesting a fresh URL each time a counselor views an attachment, but eliminates the risk of indexing or credential leakage.

Evidence: Implemented in Supabase storage integration policies and verified in repository documentation.

#3: Playwright Automated End-to-End Regression Testing

Decision Record
Context & Constraints

Admissions workflows involve multi-step form submissions; manual testing during deployment was prone to human error.

Architectural Decision

Implemented automated Playwright tests covering critical user flows, including registration, document upload, and status transitions.

Trade-offs Accepted

Tests take longer to run than pure unit tests, but provide definitive proof that user-facing workflows operate correctly.

Evidence: Verified through committed playwright.config.ts, playwright-report/, and playwright-results.json in the repository.
Security & Reliability Controls
Data Protection & Cryptography

Time-limited signed URLs expiring in 15 minutes; private access control lists on all document buckets.

Verification Scope:Verified via Supabase storage policies and integration test cases.
Authentication & RBAC

Strict separation of student, counselor, and administrator role capabilities enforced at both middleware and database levels.

Verification Scope:Verified through Supabase auth checks and Playwright authenticated testing.
Auditability & Logging

Every stage transition, counselor note, and verification stamp is logged with timestamps and user identifiers.

Verification Scope:Logged in internal database tables for operational compliance.

Repository Audit & Evidence // KeyAbroad 2.0

Verified software artifacts and production verification scope for KeyAbroad 2.0

Public GitHub Monorepo (179 Commits)
Verified Commits179 commits
Core LanguageTypeScript
Automated TestsVerified
Inspected Files & Structural Manifest
turbo.jsonapps/packages/supabase/migrations/openapi.jsonplaywright.config.tsplaywright-results.jsonDEPLOYMENT.mdCHAT_SUMMARY_AND_HANDOVER.md
Quality Assurance & Testing Evidence:End-to-End test automation configured via Playwright (playwright.config.ts, playwright-report/, and playwright-results.json committed).
Integrity & Scope Disclosure:

Live student portal access is restricted to verified KeyAbroad staff and enrolled students; public access to internal database is withheld for data privacy.

Core Engineering Challenges Resolved
High-Volume Document Uploads and Network Dropouts

Implemented client-side chunked upload logic with sha256 checksum validation to allow resume capability on weak internet connections.

Strict Access Boundaries Between Branches and Counselors

Enforced declarative Row-Level Security policies in PostgreSQL restricting counselors to dossiers assigned to their branch.

Current Implementation Status & Technical RoadmapInternal Production

Shipped and operating in production for internal workflows at KeyAbroad Consultants. Codebase actively maintained with 179 commits in GitHub repository.

Documented Upcoming Milestones
  • Direct university portal API integrations.
  • Real-time WhatsApp notification webhooks for applicants.

Related Systems in RANA.OS

View All Projects →