
OpenVault
A SaaS platform that lets companies share internal data with employees securely, with role-based access and audit logs. Dockerized Django backend.
I’m a Lahore-based Cloud & DevOps engineer. I keep Linux backends running in production on AWS, using Terraform, Docker, Nginx and CI/CD pipelines, with Django and TypeScript in the toolbox. In plain terms: I set servers up, keep them online, and make deploys boring and repeatable.
Hi, I’m Saad. I’m a cloud and DevOps engineer from Lahore. I run Linux backends in production on AWS, and I like them predictable: infrastructure you can rebuild from code, pipelines that deploy themselves, and clear steps to follow when something breaks.
So far that has meant fixing out-of-memory builds on small servers, moving a live site to a new server with DNS and SSL handled over a weekend, wiring up Terraform and GitHub Actions end to end, and shipping Django and Node.js services other people can actually run. I’m finishing a BSc in Computer Science (2027) and open to full-time and freelance work.

A timeline, oldest to most recent. Pick a point to see the role.
FlyRank AI · Remote
Building and maintaining backend services for an AI product: REST APIs and data flows, and supporting the cloud deployment. Working with the team to ship features and keep the backend reliable.
Three builds from 2025–2026, each deployed and kept running. Scroll to flip through them.

A SaaS platform that lets companies share internal data with employees securely, with role-based access and audit logs. Dockerized Django backend.

A site that deploys itself. Every push to GitHub runs the build and ships it to AWS automatically, with no manual steps.

The full AWS stack for a SaaS app, written in Terraform: compute, database, container registry and networking. Rebuildable from scratch.
Short write-ups on real problems I ran into and how I solved them.
A deploy kept failing with no clear error. It turned out the 908 MB server was running out of memory mid-build. Here is how I spotted it and the one change that fixed it.
Read →Swapping servers without taking a site offline is mostly about doing DNS and SSL in the right order. My checklist for a clean cutover.
Read →Storing infrastructure state on your laptop is a trap. A short note on remote state, locking, and why your team will thank you.
Read →If a deploy makes you nervous, something is wrong. A few habits that turn releases into a non-event.
Read →Production AWS: compute, storage and networking I can stand behind when something goes wrong at night.
If I have to do it twice by hand, I turn it into a pipeline. Infrastructure and deploys written as code.
Boring servers on purpose: hardened, supervised, logged and easy to recover.
APIs other people can run: typed, documented and migrated safely.
Currently strengthening: Kubernetes and container orchestration.
Work out the requirements, the architecture and the cost before anything is built. Boring questions now prevent emergencies later.
Terraform modules, containers and pipelines. Everything is reproducible, nothing lives only on one laptop.
Monitor, log, patch and back up. The goal is a stack so calm that silence is the normal state.
Every incident becomes a written runbook, and every runbook becomes automation. Reviews without blame.
Open for full-time and freelance work, and usually replies within 24 hours.