I build and deploy applications, including the infrastructure behind them.
Here are three projects I've built and deployed. Each one includes its architecture, the decisions I made and why, and the problems I hit along the way.
- Cloud / DevOps
- India
- Open to work
Systems
Stranger Club
A cricket-match registration platform that replaced a Google Form, a UPI QR code, and WhatsApp screenshots with one system that handles live slot availability, a FIFO waitlist, and organiser-reviewed payments.
registration → capacity check (BEGIN IMMEDIATE) → SQLite → SSE broadcast
React · Vite · FastAPI · Python · SQLite · SQLAlchemy · Server-Sent Events · Docker
Self-Service Deployment Portal
An internal dashboard for deploying Dockerized applications without SSH access — register a version, click deploy, and roll back safely if it fails.
deploy request → background task → Docker CLI → container → audit log
FastAPI · Python · PostgreSQL · SQLAlchemy · Alembic · JWT · bcrypt · Docker · Docker Compose
AWS Log Monitoring & Archival System
A small scheduled pipeline that pulls error lines out of an EC2 application log and archives them to S3 every hour, authenticated through an IAM instance role instead of stored keys.
app.log → filter ERROR → S3 upload (IAM role) → hourly via cron
Python · Docker · AWS EC2 · AWS S3 · AWS IAM · cron · GitHub Actions
A decision
Every project here is written up like this.
This one is from Stranger Club. It's the part of that system where the order of database writes actually matters, because getting it wrong means two players end up in the same slot.
Concurrency: BEGIN IMMEDIATE on capacity-sensitive writes
- Registering a player, confirming a payment, and promoting a waitlisted player each open their transaction with BEGIN IMMEDIATE, taking SQLite's write lock up front instead of discovering a conflict after the fact.
- Without it, two players could both be confirmed into the same last open slot if their requests landed close together.
- This has nothing to do with performance. It's the one place in the system where getting the write order right is what stops the match from being oversold.
Architecture diagram with 8 layers. Clients: Player (no account) and Organiser (session and CSRF). These connect to API surface: Public API and Protected API. These connect to Application: FastAPI. This connects to Domain services: Events, Registrations and Payments. These connect to Persistence: SQLite (BEGIN IMMEDIATE on capacity-sensitive writes). This connects to Live updates: Domain state change. This connects to Transport: SSE. This connects to Clients: Connected browser tabs.
Not supported URL scheme http+docker
- Docker SDK for Python incompatible with the host Docker daemon across environments.
- Replaced all container operations with direct Docker CLI invocations via subprocess.
- The CLI, wrapped carefully, turned out more portable and easier to debug than the official SDK.
password cannot be longer than 72 bytes
- passlib's bcrypt backend enforcing a length limit unexpectedly.
- Dropped passlib, hashed passwords directly with the bcrypt library.
- Even a wrapper around something as simple as bcrypt can introduce its own bug.
unknown flag --detach on docker create
- Incorrect assumption about which Docker CLI subcommand accepts which flags.
- Switched to docker run --detach.
- CLI-wrapping needs exact command shapes. Nothing catches a wrong flag before runtime.
Contact
I'm open to work in cloud, DevOps, or backend roles.
I'm based in India. The project write-ups above go into more detail than a CV would.