Welcome to Cloudwards
Cloud Native consulting: AWS & Kubernetes, voice/VoIP in the cloud and team cloud enablement.
Cloudwards is my independent consultancy for teams that need to make solid cloud and platform decisions and run them reliably in production. Think AWS and Kubernetes (often EKS), Infrastructure as Code, and the operational side: observability, incident response, and resilience.
I focus on engagements where I help teams prepare software for the cloud and migrate towards cloud-native. I can also help with migrations away from hyperscalers towards European managed cloud, Kubernetes, or on-premises.
What I help customers with
- Low-risk modernization and migrations (roadmap, milestones, rehearsed cutover)
- Kubernetes/EKS platform setup and delivery patterns (GitOps, multi-env, policies)
- AWS foundations: networking, security, connectivity (VPN/Direct Connect/TGW), cost/performance
- Infrastructure as Code: repeatable environments with Terraform/Terragrunt
- Observability baseline: metrics/logging/tracing, dashboards, alerting, and incident response routines
Voice / VoIP in the cloud
Voice is often mission critical: it must scale, keep latency low, and behave predictably under peak load. I help companies with:
- Architecture and migrations from (on-prem) voice/telephony to cloud
- Reliable SIP/RTP/WebRTC chains (including NAT, scaling, and failover)
- Operability: monitoring, capacity planning, incident response, and rehearsals
- Troubleshooting audio issues, call flows, and performance bottlenecks
Autonomy and cloud sovereignty
For me, autonomy here is primarily about freedom of choice: not getting stuck with a single cloud provider. Sovereignty and autonomy are about control: where workloads run, where data lives, who controls the keys, and how practical it is to move when needed.
Many companies see data sovereignty as strategically important and view dependency on US hyperscalers as an increasing risk. Moving workloads “back to Europe” is rarely a simple lift-and-shift: dependencies on managed services, identity, and networking make it complex. This is exactly the kind of transition I help with.
In practice, I help with:
- Portability by design: open standards, Kubernetes, IaC, and GitOps as a baseline
- Lock-in aware choices: what must stay portable, and where managed services are the right tradeoff
- Mapping hyperscaler dependencies: what your platform truly uses, and what realistic alternatives look like
- Exit readiness: migration paths, restore tests, runbooks, and rehearsals so switching is feasible
How I work
My default is enablement first: pair, ship reference implementations, and transfer knowledge so teams can move forward independently.
Experience and impact (short)
A few examples of outcomes from previous roles:
- Scaled operations to 6,000+ agents and 10,000 concurrent calls during peak load
- Executed a telephony-critical migration to AWS within a 15-minute downtime window
- Reduced call-center onboarding from months to days through repeatable platform patterns
- Led an EC2 to EKS evolution and service rewrites to Go for reliability and maintainability
Get in touch
Want to sanity-check a roadmap, platform choices, or a migration that feels risky? Reach out via /en/contact/.