About
Deepak Sagar
Freelance DevOps & Cloud Engineer
3+ Hands-On Cloud & Automation Experience
Building infrastructure that scales reliably. Not just on day one.
I'm Deepak Sagar — a freelance devops & cloud engineer focused on cloud-native infrastructure, CI/CD automation, and Kubernetes operations. I work hands-on with founders and engineering teams to design, build, and stabilize infrastructure that supports fast delivery without accumulating operational debt.
3+
Years hands-on cloud & automation
50+
Production deployments
2
Cloud platforms (AWS & Azure)
12+
Clients worked with directly
I'm not an agency. When you book a call, you're talking to the engineer who does the work.
There's no account manager, no handoff to a junior, and no communication overhead. Every architecture decision, every Terraform module, every production incident — I'm the person on it.
- No middle layers — you speak directly with the person doing the work
- No junior delegation — every implementation is done by me personally
- Consistent context — I carry full project knowledge from day one to handover
Technical strengths
What I work with
Hands-on experience across the core tools of modern cloud infrastructure — not surface-level familiarity.
AWS & Azure
Production workloads across EC2, EKS, RDS, Lambda, IAM on AWS; AKS, DevOps Pipelines, Azure Firewall on Azure. Both platforms in hybrid setups.
Kubernetes
Multi-cluster deployments, GitOps with ArgoCD and Flux, custom operators, RBAC design, and cluster upgrades without downtime.
CI/CD
Pipeline architecture for GitHub Actions, GitLab CI, and Jenkins. Build caching, artifact promotion, and environment gating across stages.
Terraform
Modular IaC at scale — remote state, workspace strategies, Atlantis for PR-driven applies, and provider version governance.
Ansible
Configuration management for cloud VMs and on-prem fleets. Idempotent playbooks, role-based structure, AWX/Tower for scheduling.
Monitoring Stack
Full observability with Prometheus, Grafana, Loki, and OpenTelemetry. Alert routing through Alertmanager, dashboards aligned to SLOs.
My approach
How I think about infrastructure
Four principles that guide every engagement, regardless of stack or scale.
Infrastructure as Code first
Every resource — network, compute, policy, secret rotation — is defined in version-controlled code. Clicking through consoles is not a deployment strategy.
Observability built in
Metrics, logs, and traces are part of the architecture, not an afterthought. Systems that cannot be observed cannot be reliably operated.
Security by default
Least-privilege IAM, network segmentation, secrets management, and automated compliance checks are baseline requirements, not add-ons.
Documentation that ships
Runbooks, architecture decision records, and onboarding guides ship alongside code. Future operators should not need to reverse-engineer the system.
Working model
How an engagement works
All projects follow the same four-phase structure. Scope and duration vary; the process does not.
Phase 01
Discovery
1 – 2 weeks
Audit of existing infrastructure, tooling, and deployment workflows. Identification of failure points, bottlenecks, and compliance gaps. No assumptions — everything is verified.
Phase 02
Architecture & Design
1 – 3 weeks
Proposed target-state architecture with alternatives documented. ADRs written for key decisions. Scope, timeline, and risks agreed before any implementation begins.
Phase 03
Implementation
Scoped per project
Iterative delivery in two-week cycles. Infrastructure changes applied through reviewed pull requests. Rollback paths defined and tested alongside forward deployments.
Phase 04
Handover & Enablement
1 – 2 weeks
Structured knowledge transfer to your team. Runbooks, dashboards, and alerting tuned to your on-call rotation. Engagement ends when your team can own it confidently.
Engagement types
Embedded or advisory
Work directly inside your engineering team (embedded) or as a technical advisor reviewing architecture and unblocking decisions. Both models available.
Async-first
Communication through written proposals, documented decisions, and async reviews. Meetings are scheduled for decisions, not status updates.
Fixed scope or retainer
Project-based engagements with a defined deliverable list, or a monthly retainer for ongoing infrastructure work and incident support.
Get started
Let's talk about your infrastructure.
If you have a specific problem — a slow release pipeline, an unreliable cluster, infrastructure that no one fully understands — book a free 30 min call and I'll give you direct, technical feedback. No sales pitch.