Independent cloud architect · Google Cloud & Azure
I’m Ryan Susana, an independent cloud architect in the Netherlands. I help large organisations and the Dutch public sector fix them, hands-on down to the Terraform.
Clients include
Services
Fixed scope, fixed price
For a platform that is too expensive, too fragile or too slow to change. Over three to four weeks, part-time, I read the code, the Terraform, the bills and the incident history, and talk to the people who run it.
Days a week, directly or through your broker
For a platform being built or rebuilt. I join for a set number of days a week as the cloud architect, the tech lead, or the hands-on engineer who builds the Terraform and pipelines with your team.
Selected work
−70%team cloud costs, so far
A data platform handling 5K–50K events a second, with a cloud bill far higher than it needed to be and a pipeline that went down every week. I helped cut the team’s cloud costs by 70% so far, partly by making that pipeline stateless; it has had no outage in over a month (October 2026).
23microservices, one shared database
A quote platform responsible for hundreds of millions in revenue a year. I designed its move to Azure Kubernetes Service, worked on it hands-on with the team of about 30 developers, and architected splitting the shared database, partly completed during the engagement.
3,000+applications depend on it
A middleware team of about 150 people moving to Google Cloud and Azure. I architected solutions that more than 3,000 applications depend on, and delivered six enterprise Terraform modules used across 1,000+ applications and integrations.
Also: modernisation for the Dutch government at DICTU, data engineering at Bol.com, and payment integrations under PCI-DSS at ReBound.
About
I’m an independent cloud architect based in the Netherlands, fourteen years into building software. The work I like best starts with a tangled system: a database shared by 23 services, a pipeline that falls over every week, a cloud bill far higher than it needs to be. I help take it apart until the better design is obvious, and I can usually show why the old one was worse.
I set a clear direction and write the decisions down, so the people building it can decide without waiting for me. And I stay hands-on. An architecture nobody can build is just a drawing, so I still write the code, the Terraform and the pipelines.