Automated CI/CD Platform for Unity Game Studio
Pugstorm is the Unity studio behind Core Keeper. When the engagement started, builds were made on someone's local machine and uploaded to Steam by hand. I owned the architecture and the full implementation of what replaced that.
Fully automated GitHub Actions pipelines, designed as modular workflows so several games and both platforms (Windows and Linux) share one build system rather than one per title. Scheduled builds, dedicated server compilation, and automated Steam deployment across release branches for internal and public testing.
Self-hosted runners on AWS, managed by Terraform as ephemeral auto-scaling instances that scale to zero and terminate themselves. The AMIs are built with Packer and come pre-loaded with Unity packages, so a fresh runner is useful within moments of booting rather than spending the first ten minutes downloading an engine. A game studio's build load is spiky by nature; this pays for exactly the spikes.
A Unity license server so builds can run in parallel, and a Discord bot so anyone at the studio can trigger a build from where they already are. Adoption is a user-experience problem, not a pipeline one. I am in the Core Keeper end credits under Tech, credited as DevOps, under my former name.
Principal Engineer
GitHub Actions / AWS / EC2 / S3 / Terraform / Packer / Unity / Steam / CI/CD / Discord
Managed Dart hosting on GKEPrincipal Engineer
Managed Cloud Platform for the Dart Backend Framework
GCP / GKE / Kubernetes / Go +10
Several hundred players a nightDeveloper & System Architect
Interactive Festival Multiplayer Game
AWS / MQTT / Next.js / Vercel +2
Zero to self-service CI/CDDevOps Architect & Engineer
DevOps Transformation from Ground Zero
Kubernetes / AWS EKS / Terraform / Terragrunt +9
Next step
Send me a short description of the problem and I'll tell you whether I'm the right fit, what it would cost, and how long it would take. No pitch deck.
