Skip to main content

02 / About

About Aryan Kapoor

Cloud & Systems Engineering

Infrastructure automation, distributed applications and computational systems. Each line below points at a repository that can be read, and at the dated check that was run against it.

01 / Evidence

The record, with receipts

The 4 claims below stayed because a file, a running endpoint or a CI pipeline could be pointed at. What could not be checked was left out.

  1. A chapter site with a dated deployment probe and a source-recorded role

    Built for the IEEE Computer Society student chapter at HKBK College of Engineering: public event, announcement, achievement, membership and newsletter pages over a managed Postgres, with an admin CMS behind the auth provider. The Web Master role is quoted from the repository's own team data rather than claimed here.

    How it was checkedSource read on 2026-11-09 (data/team.ts, eight schema files under docs/, the admin layout's redirect) and the homepage probed at HTTP 200. Route protection is layout-only because the middleware is a no-op, so the case study says so.

    Where to check it

    cs-website ↗

  2. Database-backed loan safeguards, with a dated health check

    The retained census records a React front end on Vercel and an Express 5 API on Render. A partial unique index covers active loans with an ObjectId itemId, excluding null/manual entries. Loan creation, loan return and request approval use MongoDB transactions; the session cookie is httpOnly with a server-side revocation claim.

    How it was checkedThe health endpoint returned {"status":"ok","database":"up"} on the 2026-11-09 probe, not a current availability check. Six node:test files are committed, comprising unit-style configuration tests and five integration test files; not executed in this audit. Reminder mail runs on a preview driver unless a real transport is configured.

    Where to check it

    LendLoop ↗

  3. Verification committed to the repository, not described in it

    Anchor is an Android enforcement system — an accessibility service plus a tun-level DNS sinkhole — whose rules are backed by a Room database, ten JUnit classes with real assertions, and a workflow that runs the Gradle check and a debug assembly.

    How it was checkedSource read on 2026-11-09 (.github/workflows/ci.yml configures the Gradle check and debug assembly; the test classes contain assertions). Tests and CI were not executed in this audit. Encrypted backups are advertised in settings with no cipher in the tree, and that is stated on the entry.

    Where to check it

    Anchor ↗

  4. This site itself, priced against measured frame cost

    The Futuristic experience is the practice exhibit: browser 3D, scroll choreography, reduced-motion and no-WebGL paths, all inspected in a real browser at 1440, 768 and 390 rather than assumed from a screenshot.

    How it was checkedBoot and interaction timings, with the Playwright commands that produced them, are recorded in audit/futuristic/FUTURISTIC-AUDIT.md. No figure on this page is a benchmark that was not run.

    Where to check it

    audit/futuristic/FUTURISTIC-AUDIT.md

02 / Census

What the archive contains

Counted over the systems this site names, so the distribution describes the work rather than a self-assessed skill list.

Systems named here
29
Public repositories, forks excluded
36

By engineering area

  • Cloud infrastructure14
  • Distributed systems6
  • Backend & full-stack4
  • Developer tools3
  • Security7
  • Simulation & research6
  • Experiments5

By primary language

  • Python10
  • JavaScript5
  • TypeScript5
  • HCL3
  • Go1
  • HTML1
  • Java1
  • Kotlin1
  • PHP1
  • Shell1

Counts run over the 29 systems named on this site. Areas are tags rather than buckets: one system can carry several, so the 45 area marks belong to those 29 systems while each language is counted once. The 36 repositories are the GitHub census of 2026-11-09, forks excluded.

03 / Non-claims

What this record does not claim

  • No employment, seniority or credential. The work is academic, student-organisational and self-directed unless an entry names a verified role.
  • No user counts, traffic, revenue or uptime. Nothing on this page measures adoption.
  • No benchmark that was not run. Performance figures live in the audit record, with the command that produced them.
  • No README claim taken at face value. Where a repository documented more than its source proves, the gap is stated on the case study.
  • Hosted-state labels are probes dated 2026-11-09. An instance can be down today and reachable next week.

See the work behind the skills

Explore the repositories or get in touch.

View Projects →Research →Choose Your Résumé →Get In Touch →