DevOps

I build the platform your developers deploy onto: containers, pipelines, monitoring and the self-hosted services around them. The aim is that deployment becomes the boring part, and that problems are caught before they page anyone.

01

What I build

Container platforms

Multi-container orchestration with Docker and Podman, Kubernetes for scale, service discovery, load balancing, and automated scaling and failover.

CI/CD pipelines

Automated pipelines that deploy in minutes instead of hours, integrated with security scanning and compliance checks.

Infrastructure as code and observability

Ansible for repeatable infrastructure, and Prometheus, Grafana and the ELK stack for monitoring and logging you can act on.

Self-hosted systems

Services you run yourself, done properly: n8n behind a Cloudflare Tunnel, WhatsApp automation with OpenWA, and a from-scratch mail server with SPF, DKIM and DMARC.

02

Results from shipped work

Containerized Apps

DevOps Engineer & Container Architect · 5 months, Sep 2023 to Jan 2024

  • Deployment time cut from hours to minutes
  • 99.8% application availability
  • 60% improvement in resource utilization
  • Smoother workflow for a team of 8 developers

Sanskriti Labs

Lead Developer & AI Architect · 6 months, Jan 2024 to Jun 2024

  • 50% reduction in manual DevOps tasks
  • 99.5% system uptime through predictive maintenance

Custom Email Server

System Administrator & DevOps Engineer · 3 months, Mar 2023 to May 2023

  • 99.9% uptime over 12 months
  • 99.5% spam detection rate, with DKIM, SPF and DMARC implemented
  • 50% cost savings compared to hosted solutions
03

What I design for

These are the problems that came up on real projects, and the ones I plan for before writing code.

Inter-service dependencies

Start order, health checks and failure behavior are designed explicitly, because most outages are dependency problems.

Resource allocation

Right-sizing containers so you are not paying for idle capacity or starving a noisy neighbor.

Secure networking

Isolated container networks, and tunnels instead of opened ports where that fits.

Persistence and backups

Knowing what lives in each data volume and how to restore it, before you need to.

04

Tools I use

  • Docker
  • Podman
  • Kubernetes
  • Docker Compose
  • Ansible
  • GitLab CI
  • Prometheus
  • Grafana
  • ELK Stack
  • Cloudflare Tunnel
  • Postfix
  • Dovecot
  • n8n
05

Is it a fit?

The best fit is a team that is losing time to deployments, a pipeline that needs hardening, or a set of self-hosted services that needs a real operational plan behind it.

If the work is pure front-end styling or a one-off server setup with no ongoing operation, I'm probably not the right person, and I'll tell you so.

06

Go deeper