You don’t need a new platform. You need a .
April 14, 2026 Reading Time: 4 minutes
We moved it all to tools/monday-cleanup . Now, the on-call engineer runs: platform tools folder
# tools/find-orphaned-volumes #!/bin/bash # Lists PVCs not attached to a running pod kubectl get pvc --all-namespaces -o json | jq -r '.items[] | select(.status.phase=="Lost") | .metadata.name' Stop asking devs to install 14 different CLIs.
# Platform Makefile .PHONY: tools/% tools/%: @echo "🔧 Running platform tool: $ " @./tools/$ clean-volumes: tools/clean-orphaned-volumes db-failover: tools/db-failover You don’t need a new platform
make db-failover Instead of: Finding the wiki, clicking three links, copying a broken command, and crying. My team used to spend 2 hours every Monday morning cleaning up stale environments. One person ran kubectl get ns , another ran a Python script locally, and a third manually deleted ECR images.
What is the most useful script in your team's tools/ folder? Let me know in the comments below. One person ran kubectl get ns , another
Every platform engineering team starts the same way. You build a beautiful internal developer portal (IDP), write some Terraform modules, and set up a few CI pipelines. But six months later, you hit the wall .