Cloud Engineering

Cloud that holds up in finance review.

Senior cloud engineers for architecture, migration, and FinOps - EU data residency by default, infrastructure as code throughout, and a bill your CFO can actually reason about.

The brief we usually get

Two problems we are called in to fix.

Concrete starting points, each with the team we field, the stack, and what lands in the first 30 days.

Migration & landing zone

Typical problemA stalled lift-and-shift, click-ops everywhere, and no account structure to build on.

What we shipA landing zone with IaC, guardrails, and migration in waves - not one risky weekend.

Example stackAWSTerraformControl TowerEKS

First 30 daysLanding zone stood up and the first workload migrated behind IaC.

FinOps & cost engineering

Typical problemThe cloud bill is growing faster than usage and nobody can attribute it to a team.

What we shipCost allocation tags, rightsizing, commitment plans, and per-team budgets with alerts.

Example stackAWS CostTerraformKubecostAthena

First 30 daysA tagged, attributable bill and a costed plan to cut run-rate 20-35%.

Deliverables

What you get.

Cloud outputs that make architecture, cost, and ownership clear before the platform scales.

01 / FoundationLanding zone and guardrails

02 / ControlReviewable infrastructure

03 / AccountVisible cost and ownership

Plan

Cloud architecture plan

Target account structure, network design, data residency, migration waves, and risk notes.

Why it mattersThe cloud setup is understandable before money is spent.

Build

Infrastructure baseline

Reviewable infrastructure-as-code delivered with naming, tagging, and ownership conventions.

Why it mattersYour team can change the platform safely instead of clicking through consoles.

Cost

Cost visibility pack

Tagged spend, budget views, rightsizing findings, and a prioritized savings plan.

Why it mattersFinance can see where cloud cost comes from and what can be reduced.

Handover

Handover documentation

Access model, operating notes, security assumptions, and maintenance guidance.

Why it mattersThe platform is owned by your team, not locked inside our heads.

Stack we work in

Across the three big clouds.

Platforms

AWSAzureGCPHetzner

IaC

TerraformPulumiCloudFormationBicep

Containers

EKSAKSGKEFargate

Networking

VPCTransit GatewayCloudflarePrivateLink

FinOps

Cost ExplorerKubecostAthenaSavings Plans

Security

IAMVaultGuardDutySCPs

How we work

From cloud sprawl to controlled platform.

Architecture, migration, cost, and ownership are handled together instead of as disconnected workstreams.

PHASE 01

Assess

Map current footprint, cost drivers, and data-residency and compliance needs.

Time1-2 weeks

DeliverableTarget + cost model

PHASE 02

Landing zone

Accounts, guardrails, networking, and IaC foundations to build on.

Time2-3 weeks

DeliverableIaC landing zone

PHASE 03

Migrate & optimise

Workloads in waves, then rightsizing and commitment plans for run-rate.

TimeOngoing

DeliverableMigrated + costed

PHASE 04

Operate & hand off

Budgets, alerts, and IaC docs. Your team owns it, we stay reachable.

TimeMonth 4+

DeliverableOwnership handover

Who delivers this

Named engineers from the bench

A snapshot. You interview the actual people before anyone joins your team.

BesnikCloud engineer

Available now

Cloud / DevOps Engineer

10 yrs · platform & reliability

AWSKubernetesTerraformArgoCD

EnglishC1

GermanB2

InterviewsReady to interview

LuanCloud architect

Available Sep

Cloud Architect

11 yrs · migration & FinOps

AWSAzureTerraformKubecost

EnglishC2