Who we are ¶
Wintermute Core is a small engineering shop. We work on cloud platforms, custom backends, and the boring infrastructure that keeps both running. Most engagements come from teams that already have a problem in production and want someone who can read the logs, fix the cause, and not break anything else on the way out.
Our clients tend to fall in two camps: startups that outgrew their first cloud setup and need it rebuilt before it falls over, and established teams modernising older platforms without a full rewrite.
What we do ¶
We work across the stack we ship into. Cloud-native services on AWS, GCP, and OpenStack. Kubernetes on GKE, EKS, OpenShift, Rancher, and self-hosted k3s when that makes more sense. Data pipelines (batch and streaming) when raw events need to become something a business can act on. Plus the security and compliance side: DPO services, vulnerability assessments, GDPR work for teams that need it documented properly.
We pick tools to fit the team that has to run them after we leave. A managed service is usually better than a clever self-hosted one, and a small Helm chart is usually better than a custom operator.
How we work ¶
Infrastructure as Code is the default, not a phase. Terraform, Terragrunt, Ansible, Helm, all version-controlled, all reviewable. Environments are reproducible because nobody wants to debug a one-off kubectl apply at 3am.
We design for production from day one. Monitoring, alerting, backup, restore drills, capacity headroom: these go in with the first release, not in a cleanup ticket six months later. CI/CD is set up so the path from commit to production is short, automated, and obvious to whoever inherits it.
Open source ¶
We publish what we can. Tools and libraries that solved a real problem in production, kept in shape because we still use them. Repositories live at github.com/wintermute-core.
Contact ¶
Support: support [at] wintermutecore.atlassian.net
General inquiries: wintermute [at] wintermutecore.com
GitHub: wintermute-core