The stack behind the work.
Not a frequency tier list. Not a list of every tool I’ve ever opened. Just the core toolkit, the actual stack of each shipped product, and what I’m sharpening next.
Currently shipping · May 2026
KMS
v2 attendance flow
Portfolio
Phase 1 honesty pass · WebGL groundwork
Knowledge Minds Scheduler
constraint solver iteration
01 · The constants
Core toolkit
The always-on layer that runs through every project I ship. Six tools. Six reasons.
Next.js
App Router, server components, image optimization, file-based routing — the SSR baseline I default to.
Used in
React
Component-driven UI as the default mental model — pairs natively with Next.js or stands alone with Vite.
Used in
TypeScript
Type safety isn’t optional. Every new project starts in TS — no JS escape hatches.
Used in
Tailwind CSS
Utility-first; design system lives in tailwind.config.ts, not in a hundred .css files.
Used in
Git & GitHub
Every project, every commit. Branches for features; main stays deployable.
Used in
Vercel
Deploy target for the Next.js work. Preview URLs, CI, edge — zero infra to think about.
Used in
02 · The receipts
What I actually composed
One row per product. The exact stack each one is built on — no aspirational entries.
Dengue Connect
LiveGovernment Android health-surveillance app
Key Manpower Supervision (KMS)
Live · PrivateWorkforce-management SaaS · paying clients
Knowledge Minds Scheduler
In dev · PrivateUniversity timetable optimizer
Nivarthi
In devHealthcare appointment booking SaaS
VirtuBooks
In devSmall-business bookkeeping SaaS
Portfolio
LiveThis site
03 · The edge
What I’m sharpening
Each one named with the project it’s heading toward, not just “exploring”.
Docker
Dockerize VirtuBooks for self-hosted deploy at small businesses without Vercel access.
First ship
Q3 2026
Testing (Jest · Playwright)
Regression suite for KMS — protect the attendance and billing flows.
First ship
Alongside KMS v2
WebGL · Three.js
Portfolio Phase 5 — interactive project planes replacing static cards.
First ship
This year
04 · How I choose
Three rules I follow when picking tools
Use proven tools first
Next.js, Postgres, Firebase — mature and well-documented. The surprises in a project should come from the product, not from whether the framework can render a list.
Stay in the same stack across projects
Five of the six projects on this site share the same core: Next.js + TypeScript + Tailwind. Switching stacks every time means relearning, not shipping.
A tool counts only after it ships
I don’t list Docker or Three.js as skills yet — they’ve only seen demos. They get added once a live deployment actually depends on them.
05 · Where I trained
Education
M.Sc. Integrated Computer Science
Pondicherry University
Five-year integrated program · graduated 2026.
Higher Secondary Certificate (HSC)
Computer Science Stream
Foundation in programming, math, and logic.