Cloud infrastructure
Design, migration, cost review and operation on AWS, Google Cloud, Azure and European bare metal. Infrastructure as code, one named engineer, and a written plan before anyone touches production.
Three ways to start
Every one of them ends with documentation you own. Starting prices are the ones we invoice. Anything larger gets a written estimate before work starts.
One week in one cloud account or cluster. Security, cost, reliability and a prioritized to-do list with estimates. The report is yours to keep and to build with, whoever does the building. Larger estates are quoted after a short call.
A new platform, a move between clouds, or the move from a data center. Delivered in milestones with a named engineer, infrastructure as code and a hand-over your team can operate.
We keep the platform patched, backed up and observed, and respond to incidents within business hours at an agreed response time. Improvement work is billed by the day on top, so the monthly fee stays predictable.
What the work looks like
Inventory what runs, what it costs and what is fragile. The missing documentation is a by-product of the assessment.
From a data center to a cloud, between clouds, or from a cloud to European servers when the bill or the data residency says so. Milestones, rehearsals, a cut-over plan.
Right-size, reserve, delete. A cost review ends with the before and after in one table, so the saving is visible before you decide what to change.
Terraform or CDK for everything, CI/CD for every change, backups that have been restored at least once.
Patching, backups, monitoring and business-hours incident response on a monthly retainer, with improvement days on top.
Runbooks, decision records and a hand-over session. If Labb disappeared tomorrow, your team could keep going.
Tools we reach for
From the work
A Volkswagen group platform on AWS, operated and improved across four years: infrastructure as code, CloudWatch dashboards and alerting, CI/CD on GitHub, and incident response within the agreed hours.
Before you call
Yes, and it is a common starting point. The assessment inventories what is running, what it costs and what is fragile, and produces the missing documentation as a by-product.
Any EU region on the three big clouds, and German or Finnish data centers on Hetzner. We have built set-ups where all data stays inside the EU, including the AI components.
With it. Most engagements pair a Labb engineer with your developers so the knowledge stays in the company. Where the team is still being built, we run the platform on a retainer and document it for the people who come next.
We hold an AWS certification and a Microsoft partnership, and we recommend Hetzner when it is the right answer. The recommendation follows your workload, your team and your bill.
Talk to an engineer
Thirty minutes with a senior engineer. Reply within one business day.