Projects using AWS in LahoreProjects using AWS in Lahore
Projects
People
Cover image for TecShield is a corporate website
TecShield is a corporate website I designed and developed to showcase expertise in game development, mobile and web app development, AR/VR, and custom software solutions for startups and enterprises worldwide. The goal was to create a professional digital presence that clearly communicates the studio's capabilities and converts visitors into clients. 🔹 Key Highlights: ✔️ Service Showcase – Highlights core expertise across game development (Android, iOS, Web, PC, Web3/NFT, VR) and custom software/backend solutions. ✔️ Portfolio Integration – Displays past projects and case studies to demonstrate range and credibility. ✔️ Client Testimonials – Dedicated section featuring reviews and feedback from past clients. ✔️ Responsive Design – Fully optimized layout across desktop and mobile devices. ✔️ Modern Web Stack – Built for performance, fast load times, and clean navigation. ✔️ Lead Generation – Streamlined contact flow designed to convert visitors into inquiries and clients. 🌟 Impact: The website now serves as the studio's primary digital storefront, presenting over 10 years of game development and software expertise to a global audience. It reinforces trust through visible client testimonials and portfolio work, and continues to support ongoing growth and client acquisition.
0
99
Cover image for I also designed and developed
I also designed and developed https://infinite-compute.com/, a cloud-powered platform that enables users to access high-performance GPU machines and run demanding 3D tools directly from the web without expensive local hardware. I built the complete system architecture myself including the frontend backend services and cloud infrastructure focusing on performance reliability and secure access to remote computing resources. The platform provides a responsive interface to launch and manage GPU sessions while the backend handles session orchestration user management and compute allocation. The system was designed to maintain stable remote sessions efficiently manage resources and provide secure authentication so developers designers and 3D artists can run heavy software on demand from anywhere.
0
147
Cover image for 🚀 Why I'm a big
🚀 Why I'm a big fan of Blue/Green Deployments on AWS One of the biggest challenges in software development isn't writing code—it's releasing it safely. Blue/Green deployment is a strategy where two identical production environments exist side by side: 🔵 Blue — the current live application serving users. 🟢 Green — the new version, fully deployed and tested before anyone sees it. Once the Green environment is validated, production traffic is switched over. If an issue is discovered, traffic can immediately be routed back to Blue with minimal disruption. Why this approach matters: ✅ Near-zero downtime during releases ✅ Fast and reliable rollback strategy ✅ Reduced deployment risk ✅ Better confidence for engineering teams ✅ Safer updates for customers What I appreciate most about this pattern is that it changes deployments from a stressful event into a routine operation. Instead of hoping a release goes well, you have a built-in safety net. Whether you're building SaaS products, internal platforms, or customer-facing applications, investing in a robust deployment strategy often delivers as much value as the features themselves. Modern software isn't just about shipping fast—it's about shipping safely.
1
2
160
Cover image for FinOps automation across seven environments Automated
FinOps automation across seven environments Automated scheduling and rightsizing that took roughly $280k a year out of the cloud bill. Who it was for: A large regional bank running seven cloud environments. The problem. Seven environments, most of them idle outside working hours, and no visibility into which team was spending what. Cost conversations were happening after the invoice rather than before. What I did. Established a cost baseline per environment, then automated resource scheduling so non-production stopped paying for nights and weekends. Rightsized the workloads that were provisioned for peaks that never came. Built daily and weekly cost reporting so stakeholders could see the trend without asking for it. The result. Around $280k of annual run-rate removed, with ongoing reporting that keeps the saving from creeping back.
0
50