{
  "name": "Yaduraj Singh",
  "age": 20,
  "role": "Full-stack engineer · AI/ML builder",
  "location": "Dehradun · Greater Noida, India",
  "tagline": "Ships production-grade systems solo — firmware on ESP32, scalable SaaS, iOS apps. Three live products with real users before 21.",
  "links": {
    "portfolio": "https://yaduraj.me",
    "github": "https://github.com/YadurajManu",
    "linkedin": "https://www.linkedin.com/in/yadurajenc",
    "email": "yadurajsingham@gmail.com",
    "resume": "https://yaduraj.me/Resume_Web.pdf"
  },
  "stats": [
    {
      "value": "2,000+",
      "label": "users in production"
    },
    {
      "value": "08",
      "label": "shipped projects"
    },
    {
      "value": "03",
      "label": "hackathons won"
    },
    {
      "value": "04",
      "label": "self-hosted servers"
    }
  ],
  "highlights": [
    "Self-hosted Linux infrastructure — Nginx, SSL, PM2, systemd. Not just Vercel deploys.",
    "Manual WebRTC: full ICE/STUN/TURN + signalling layer. No third-party video SDK.",
    "Designed multi-tenancy, RBAC, caching, CI/CD for a hospital SaaS — solo, from a blank repo.",
    "Three live production applications with real users before age 21.",
    "Hackathon-winning hardware + AI system: ESP32-S3 + FastAPI + Flutter, team of two.",
    "AI/ML pipelines: handwriting synthesis, voice + LLM + TTS cognitive OS, wearable vitals monitoring."
  ],
  "experience": [
    {
      "role": "Lead Software Developer — Intern",
      "organization": "Gautam Buddha University",
      "period": "2024 · 6 months",
      "highlights": [
        "Sole architect of a ground-up institutional ERP — ER diagrams, API contracts, to production deployment.",
        "Modules: student lifecycle, automated attendance, fee ledger, timetable engine, faculty/admin portals.",
        "Eliminated 100% paper workflows. ~60% admin overhead reduction."
      ],
      "stack": [
        "Node.js",
        "Express",
        "JWT RBAC",
        "React"
      ]
    }
  ],
  "nowBuilding": {
    "name": "Fleet OS",
    "status": "open source · mit",
    "url": "https://fleet.plastikworld.xyz",
    "repository": "https://github.com/YadurajManu/fleet-os",
    "category": "Infra · Orchestration",
    "pitch": "Git push to the hardware you already own. A Raspberry Pi, an old laptop and a spare VPS, treated as one deploy target — multi-arch builds, constraint-based placement, health-gated rollouts and automatic failover.",
    "highlights": [
      "Outbound-only Go agents — no inbound Docker socket, no SSH key, no port to forward. A Pi behind a home router is a first-class node.",
      "Weighted scheduling across CPU, memory headroom, reliability tier, tags, GPU and affinity — and the placement plan explains every node it rejected.",
      "Health-gated rollouts: the release that works keeps serving until its replacement proves it can serve too."
    ],
    "stack": [
      "Go",
      "TypeScript",
      "Fastify",
      "Drizzle ORM",
      "PostgreSQL",
      "Redis",
      "Docker Buildx",
      "React",
      "Vite",
      "nginx",
      "Cloudflare Tunnel"
    ],
    "metrics": [
      {
        "label": "Inbound ports",
        "value": "0"
      },
      {
        "label": "Agent",
        "value": "Go static"
      },
      {
        "label": "Arches",
        "value": "arm64 · armv7 · amd64"
      },
      {
        "label": "License",
        "value": "MIT"
      }
    ],
    "caseStudy": {
      "problem": "Coolify, Dokploy and CapRover are excellent single-server deployment tools, but their scheduling model assumes one stable host or a fairly uniform cluster. Balena assumes a fleet of similarly managed devices. None of them fit the hardware most people actually have lying around — a Raspberry Pi, an old laptop and a spare VPS, on different architectures, behind different networks, none of them reliably online.",
      "approach": [
        "Outbound-only Go agents: each node reports its capabilities and heartbeats over outbound HTTPS and reconciles container state locally. No inbound Docker socket, no SSH key, no port to forward.",
        "The control plane holds a reverse tunnel for ingress, so a machine on a college LAN or behind a home router can serve public traffic without a port forward.",
        "Weighted scheduling across CPU, memory headroom, reliability tier, tags, GPU, affinity and anti-affinity — with a dry-run placement plan that explains every node it rejected.",
        "Architecture-aware multi-platform builds through Docker Buildx, pushed to a registry the fleet pulls from, so an arm64 Pi and an amd64 VPS each get an image they can run.",
        "Health-gated rollouts plus heartbeat liveness, cordon/drain controls, and automatic failover for flexible services."
      ],
      "decisions": [
        "Heterogeneous, intermittently connected hardware is the design centre, not an edge case — capability discovery is reported by agents rather than assumed by the scheduler.",
        "Pinned stateful services are treated differently from movable stateless ones, because rescheduling a database is not the same as rescheduling a web process.",
        "Per-organisation GitHub App installations, so a shared control plane never lets one tenant reach another's repositories.",
        "Envelope-encrypted secrets with per-secret keys, injected only into the services that declare them.",
        "MIT with no open-core split and no enterprise fork — what is in the repository is the product."
      ]
    }
  }
}