Practice 01 / Platform engineering
GÜRAY YILDIRIM / INDEPENDENT PRACTICEI help teams find and remove the operational friction hiding across Kubernetes, cloud infrastructure, Terraform, CI/CD, observability, security controls and developer experience.
When this helps
Recurring incidents with no durable learning loop.
Release paths held together by undocumented knowledge.
Terraform drift, duplicate modules and unclear state ownership.
Kubernetes complexity absorbed by every product team.
Observability that collects data but does not shorten diagnosis.
Security controls that arrive late and block delivery.
Kubernetes, workload boundaries, resilience and recovery.
Terraform modules, state, policy and repeatability.
CI/CD paths, release safety and rollback.
Metrics, logs, traces and actionable service ownership.
Identity, secrets, supply chain and policy as code.
Golden paths that reduce cognitive load without hiding reality.
Specialist track / IoT & edge
For connected products, I work on the software delivery and operations layer around gateways and fleets: secure release paths, containerised edge workloads, telemetry, rollout health, rollback and edge-to-cloud observability.
This is DevOps and platform work for connected systems. It is not an embedded hardware or firmware-development service.
Focused engagements
For a team that sees recurring failure but lacks a defensible sequence of improvements.
A focused diagnosis for a live or reproducible cluster problem. This is scheduled technical work, not 24/7 incident cover.
For teams repeatedly assembling the same infrastructure and release paths across products.
Customer evidence
20 / 20Every public customer rating is five-star. The repeated themes are speed of diagnosis, clear communication, Kubernetes and AKS problem-solving, and intent to work together again.See selected evidence ↗
Start with the real problem
Share the architecture, current symptoms, relevant incidents and the decision you need to make. I will propose a bounded first engagement.