Independent builder · Malaysia · 2026

I build
systems that work.

I'm Koglesh R. Murugan. I build full-stack products, deterministic systems and practical digital tools — from problem discovery and architecture to code, testing and deployment.

Build with purpose. Learn by shipping.

My work is centered on clear system boundaries, dependable data, explainable behavior and shipping software people can actually use.

Portfolio / 2026MY ·

10

Shipped projects

Products, experiments and creative work

03

Architecture-led builds

MIRROR · GRIDPULSE · PACE

LIVE

Public build log

The portfolio moves with the work

Selected work

Built, not imagined.

Every project is presented as a working system: what it does, how data moves, what trade-offs shaped it, and where the source lives.

TIER 01 / CORE SYSTEM ENGINES

Core architecture first.

03 SYSTEMS
01LIVE · DETERMINISTIC SIMULATION
Source

MIRROR

A deterministic decision-simulation engine for measurable, resource-constrained situations. It converts explicit scenario inputs into a structured model, runs a discrete-time simulation locally, and exposes queues, capacity, utilization, events and what-if consequences.

Next.jsReactTypeScriptSimulationVercel

System architecture

FLOW / 01
NODE / 01Scenario
NODE / 02Structured model
NODE / 03Discrete-time engine
NODE / 04State + metrics
NODE / 05What-if diff

FLOW / VERIFIED DESCRIPTION · NOT A RUNTIME TRACE

MIRROR / sandbox

Change the constraints.

LOCAL DEMO · NO API
RESOURCE POOL6QUEUEOKPROCESSED40

Capacity index

60

Work processed

40

Queue pressure

CLEAR

Illustrative control model only. It demonstrates reactive UI paths, not MIRROR’s full minute-by-minute engine or a measured benchmark.

Technical trade-off

MIRROR is deliberately deterministic and local: the same scenario and rules should produce the same result. If inputs exceed the supported single-flow model, the system must mark the case unsupported rather than inventing behavior. The interactive controls below are a portfolio demo, not a live connection to MIRROR.

02LIVE · INFRASTRUCTURE INTELLIGENCE
Source

GRIDPULSE

An evidence-first infrastructure intelligence control plane that separates observed telemetry, validation, prediction and explanation. PostgreSQL stores the evidence layer while optional Azure ML and Microsoft Foundry services provide bounded intelligence.

Next.jsPostgreSQLZodAzure MLMicrosoft FoundryVercel

System architecture

FLOW / 02
NODE / 01Human telemetry
NODE / 02Next.js API + Zod
NODE / 03PostgreSQL evidence
NODE / 04Azure ML
NODE / 05Foundry explanation

FLOW / VERIFIED DESCRIPTION · NOT A RUNTIME TRACE

GRIDPULSE / telemetry stream MOCK STREAM

SIMULATED DEMO DATA · no live endpoint, outage, score, or prediction is being reported.

Technical trade-off

Failure contract: if optional AI routes time out, are rate-limited, or return invalid data, mark the intelligence path unavailable, retain the validated evidence boundary, and withhold the inference. Never turn a failed request into a fabricated prediction. The telemetry panel below is simulated and is not connected to the live API.

03LIVE · ACADEMIC WORKLOAD
Source

PACE

A multi-user academic workload planner that combines deadlines, effort, priority and available capacity into a realistic seven-day plan, with automatic rebalancing as work changes.

Next.jsReactTypeScriptAppwriteVercel

System architecture

FLOW / 03
NODE / 01Capture
NODE / 02Understand
NODE / 03Allocate
NODE / 04Act
NODE / 05Recalculate

FLOW / VERIFIED DESCRIPTION · NOT A RUNTIME TRACE

Technical trade-off

PACE uses Appwrite authentication, TablesDB and per-user row permissions. Failure boundary: if a write is rate-limited or the network fails, the UI must not claim the task was saved until the server confirms it; any pending work should be identified as unsynced.

TIER 02 / MICRO-UTILITIES & FUNCTIONAL EXPERIMENTS

The supporting systems.

Additional shipped products, practical utilities and experiments — organized below the three core engines, not mixed into the same visual tier.

07 BUILDS
04LIVE · WORKLOAD INTELLIGENCE
Source

SYNAPSE

A local-first workload planner that turns deadlines, effort, priority and available time into a deterministic seven-day plan.

Next.jsReactTypeScriptLocal StorageVercel

System architecture

FLOW / 04
NODE / 01Tasks
NODE / 02Local state
NODE / 03Planning rules
NODE / 04Seven-day allocation
NODE / 05Next action

FLOW / VERIFIED DESCRIPTION · NOT A RUNTIME TRACE

Technical trade-off

Local-first keeps the core planning workflow independent of a backend. If browser storage reaches its quota or a write is denied, persistence can fail and recent changes may not survive a refresh. This portfolio does not claim a cloud fallback or verified quota-recovery path.

05LIVE · CIVIC TECH
Source

QueueWise

A community-powered queue tracker for everyday public services, built around fresh reports and transparent estimates rather than opaque waiting-time guesses.

Next.jsSupabasePostgreSQLOpenStreetMap

System architecture

FLOW / 05
NODE / 01Community report
NODE / 02Supabase
NODE / 03PostgreSQL
NODE / 04Location context
NODE / 05Queue estimate

FLOW / VERIFIED DESCRIPTION · NOT A RUNTIME TRACE

Technical trade-off

Fresh user reports are treated as signals. The product focuses on transparent estimates instead of presenting a queue estimate as guaranteed ground truth.

06LIVE · SOCIAL IMPACT
Source

FoodLoop

A food-rescue platform connecting surplus food with people who can use it through database-backed listings, requests and practical product workflows.

Next.jsSupabasePostgreSQLVercel

System architecture

FLOW / 06
NODE / 01Food listing
NODE / 02Database
NODE / 03Availability
NODE / 04Request
NODE / 05Rescue workflow

FLOW / VERIFIED DESCRIPTION · NOT A RUNTIME TRACE

Technical trade-off

The workflow is built around structured listings and database state so the product can represent availability changes instead of relying on static content.

07LIVE · UTILITY
Source

BeforeYouGo

A practical preparation tool for building independent checklists before visits, travel and important tasks.

Next.jsTypeScriptLocal StorageSEO

System architecture

FLOW / 07
NODE / 01Context
NODE / 02Checklist rules
NODE / 03Local state
NODE / 04Review
NODE / 05Ready state

FLOW / VERIFIED DESCRIPTION · NOT A RUNTIME TRACE

Technical trade-off

The private checklist workspace is stored in the browser for this MVP. If storage quota is exhausted or a write is denied, checklist changes may not persist across reloads; no shared-database fallback is implied. The UI should surface that failure instead of reporting a false save.

08LIVE · AI PRODUCT
Source

One Next Step

A focused decision experience designed to turn a situation into one clear, useful next action instead of an overwhelming full plan.

Next.jsTypeScriptAI

System architecture

FLOW / 08
NODE / 01Situation
NODE / 02Context
NODE / 03AI reasoning
NODE / 04Next action
NODE / 05User decision

FLOW / VERIFIED DESCRIPTION · NOT A RUNTIME TRACE

Technical trade-off

The interface intentionally narrows the output to one actionable step, reducing cognitive load rather than presenting a long generated plan.

09LIVE · WEB PRODUCT
Source

Truth Checker

An evidence-first claim investigation experience built to make online information easier to examine, question and trace back to supporting web evidence.

Next.jsTypeScriptAIEvidence

System architecture

FLOW / 09
NODE / 01Claim
NODE / 02Evidence search
NODE / 03Source context
NODE / 04Assessment
NODE / 05Explanation

FLOW / VERIFIED DESCRIPTION · NOT A RUNTIME TRACE

Technical trade-off

The product emphasizes evidence and source context so an assessment can be examined instead of being treated as an unexplained verdict.

10CREATIVE · CHALLENGE PROJECT
Source

AERO

A challenge-driven creator project built around learning, experimenting, storytelling and documenting progress through real attempts.

YouTubeEditingStorytelling

System architecture

FLOW / 10
NODE / 01Challenge
NODE / 02Attempt
NODE / 03Setback
NODE / 04Progress
NODE / 05Payoff

FLOW / VERIFIED DESCRIPTION · NOT A RUNTIME TRACE

Technical trade-off

AERO treats the attempt itself as the story: real constraints, mistakes and progression matter more than pretending every experiment succeeds immediately.

PORTFOLIO SOURCE MAP

app/page.tsx

Project contract, architecture views, command terminal, local demos, and milestone content.

app/globals.css

Global system styling, motion preferences, status shell, and print layout.

app/layout.tsx

Site metadata, font setup, and schema.org structured data.

Product-specific repository directories vary. Source links point to each real repository so internal paths are not guessed or represented as verified when they have not been inspected.

PERFORMANCE / MEASUREMENT REGISTER

Measure first. Publish second.

The portfolio does not yet publish measured bundle, cold-start or client-calculation numbers. These require a reproducible test environment; a successful build is not a performance benchmark.

Bundle size

Not measured

Cold start

Not measured / route dependent

Client compute

Not instrumented

Method: record commit, device/browser, repeated samples and median; distinguish lab measurements from real-user Core Web Vitals.

DATA CONTRACT / PORTFOLIO INDEX

The portfolio uses one shared TypeScript project model. Product-specific API and database schemas belong in each source repository and are shown only when verified.

[VIEW_DATA_SCHEMA.JSON]

PORTFOLIO CONTRACT · shared project index

TYPESCRIPT / SOURCE-VERIFIED
type Project = {
  number: string;
  title: string;
  label: string;
  description: string;
  architecture: string[];
  tradeoff: string;
  tags: string[];
  href: string;
  source: string;
  featured?: boolean;
};

This is the exact typed contract used by this portfolio to render the project index. It is not presented as the internal Zod or database schema of the linked product.

Engineering principles

Make the system
understandable.

01

Model the problem

Start with the system, constraints and the actual user need.

02

Make the data trustworthy

Keep state, permissions, evidence and assumptions explicit.

03

Expose the trade-offs

A useful system should make important engineering decisions understandable.

04

Ship and iterate

Production feedback is part of the engineering loop, not the end of it.

Stack

Tools I ship with.

The stack changes with the problem. The consistent part is the focus on typed code, clear state, useful interfaces and deployable products.

Next.jsReactTypeScriptJavaScriptTailwind CSSSupabasePostgreSQLAppwriteAzureAI productsGit & GitHubVercel

Out-of-band achievements

Milestones &
Runtimes.

A bounded record of competitive results, published submissions, shipped experiments, and creator analytics. Every metric has a time window; every external claim has a source for context to verify execution where available.

ARCHIVE / 06 RECORDS

SPORT / 001

[RESULT: GOLD]

VIFA Gewinn India Open International Taekwondo Championship

Peddem Multipurpose Indoor Sports Complex (Peddem Indoor Stadium) · Mapusa, Goa, India

Dates
28–29 Sep 2024
Result
Gold medalist

SPORT / 002

[RESULT: BRONZE]

10th MBC Cup Open International Taekwondo Championship

Korea · 2025

Scope
International
Result
Bronze medalist

International competition experience. Preparation, technical precision, timing, and composure under tournament pressure.

SPORT / 003

[RANK: BLACK BELT]

Taekwondo Black Belt

Rank milestone · Competitive Taekwondo

Sustained practice in technical execution, conditioning, timing, and composure under competitive pressure.

DISCIPLINE / REPEATABILITY

CREATOR / AERO

Audience signal, measured.

YouTube Studio snapshot · 12 Sep–09 Oct 2026 · 28-day window

Open channel ↗
Views
35,550
Watch hours
125.3
Subscribers
+42

Top Short in this window

I Tried Making a Zack D. Films Style Short

6 Oct 2026 · 8,435 views in the snapshot

[FORMAT: SHORTS]

Multiple editing, skill, and student-life Shorts also crossed 1,000 views. These are dated historical analytics, not a live counter or a forecast.

BUILDER / GRIDPULSE

[STATUS: SUBMITTED]

NextStep Hacks 2026

GRIDPULSE was submitted as a public hackathon project. This records participation and shipped work, not a prize or finalist result.

BUILDER / FOODLOOP

[BUILD MODE: PHONE-ONLY]

Mobile-first execution

Built the initial FoodLoop MVP entirely on a phone, then published the product and source. Real-world adoption and impact remain separate from the build milestone.

Build log

What shipped recently.

PUBLIC / ACTIVE
08 SEP 2026MIRROR

Finished the deterministic decision-simulation engine and documented its model boundaries.

07 SEP 2026PACE

Shipped the academic workload planner with Appwrite authentication, per-user permissions and a production deployment.

06 SEP 2026SYNAPSE

Shipped the workload planner into the portfolio and prepared the competition submission.

05 SEP 2026GRIDPULSE

Hardened the infrastructure control plane, telemetry flow and evidence boundary.

04 SEP 2026Portfolio

Reframed the portfolio around shipped products, architecture, proof of work and active engineering.

04 SEP 2026FoodLoop

Continued product relaunch work with a focus on useful, dependable workflows.

Contact

Have a real problem
worth building for?

I'm interested in thoughtful products, engineering challenges and opportunities to turn a clear problem into something useful.

LinkedIn