I design cloud platforms that feel quiet to operate: well-proportioned, resilient by default and honest about cost. Less noise in the pager, more room for the teams building on top.
A few principles I bring to every platform, whether it's a greenfield landing zone or a fifteen-year-old system finding its way to the cloud.
Failure is designed for, rehearsed and boring when it happens.
FinOps belongs in the first diagram, not the quarterly review.
Fewer moving parts, clear ownership, documentation people actually read.
I'm Konstantin, a Cloud Solutions Architect living in Pirkkala, just outside Tampere in Finland. For more than a decade I've helped organisations move from fragile, hand-built servers to platforms that are secure, observable and pleasant to work with.
My work sits between people and systems. I spend as much time listening to product teams, security officers and finance as I do drawing diagrams, because the best architecture fits the organisation that has to live with it. I translate business goals into reference architectures, landing zones and migration roadmaps, then stay close while they're built.
Day to day that means multi-cloud strategy across AWS and Azure, Kubernetes platforms, infrastructure as code, zero-trust networking and a steady focus on cost. I've led migrations for manufacturers, fintech companies and public-sector services, always with an eye on what will still make sense five years from now.
Away from the keyboard you'll find me on the lakeside trails around Pyhäjärvi, in the sauna, or slowly getting better at woodworking, which, it turns out, rewards the same patience as good infrastructure.
A well-stocked, well-organised set of skills. The filled pills are the ones I use every week.
A few projects that show how I work: clear goals, measured outcomes, and platforms teams are glad to inherit.
Planned and led the migration of 38 production workloads from two ageing data centres to an Azure landing zone with hub-and-spoke networking, private endpoints and automated policy guardrails.
Designed a multi-region EKS platform with GitOps delivery, service mesh and active-active failover for a payments provider handling peak traffic of 4,000 transactions per second, PCI-DSS aligned from day one.
Built an internal developer platform with golden-path templates, so 20+ municipal service teams can provision compliant environments in minutes instead of filing tickets and waiting weeks.
Introduced tagging standards, cost dashboards and rightsizing automation across a 300-account AWS organisation, paired with OpenTelemetry tracing so teams see cost and performance side by side.
Each role added a layer: hands-on operations first, then platform engineering, then architecture across whole organisations.
Planning a migration, rethinking a platform or just want a second opinion on an architecture? I'm always happy to listen.
Cloud Solutions Architect
Oikotie 1