Skip to main content

# SERVICE 03 / 04

Cloud that's right-sized, not over-engineered

Your 'Frankfurt region' AWS account is still US-owned infrastructure — the CLOUD Act reaches it. Your bill compounds faster than your workloads. Nobody can rebuild the environment from scratch because it was clicked together in a web console. We quantify your actual CLOUD Act exposure, migrate to IaC-first architecture, and right-size spend. Typically production-ready in under 8 weeks.

≤30%

Cloud cost savings

<8 wk

Production-ready

100%

Infrastructure as Code

Mitigated

CLOUD Act risk

# THE-PROBLEM

Why this matters

Cloud costs grow but clarity doesn't. Migration was copy-paste. You're running three data warehouses across two providers and still can't answer basic questions about cost drivers or sovereignty.

The European Commission's 2024 cloud strategy explicitly warns that hosting on US-hyperscaler infrastructure creates regulatory exposure under the CLOUD Act, even when servers are physically located in the EU.

// SOUND FAMILIAR?

  1. "Frankfurt region" treated as EU-sovereign — it isn't under the CLOUD Act
  2. Cloud bill growing 30%+ per quarter with no clear driver or accountability
  3. Infrastructure clicked together in a web console — no code, no audit trail, no bus factor
  4. Locked into one vendor with no exit strategy and rising egress fees
  5. Multiple data warehouses, none of them the "source of truth"

# IS-IT-FOR-YOU

Where we fit — and where we don't.

// best fit for

  • You're on AWS/GCP in EU regions but worried about US legal reach
  • Cloud spend is growing without clear ownership or cost attribution
  • Infrastructure was built in a web console — no IaC, no audit trail
  • You want an exit strategy from vendor lock-in before it becomes urgent

// not ideal for

  • Pure lift-and-shift migrations with no architectural change
  • Companies with existing IaC, solid cost governance, and no sovereignty concerns
  • Single-application deployments that don't warrant an architecture review

# HOW-WE-WORK

Four steps, no ceremony.

  1. Assessment

    Map your actual CLOUD Act exposure, current costs, and vendor lock-in risk. "Frankfurt region" ≠ sovereign — we quantify the gap.

  2. Blueprint

    IaC-first architecture design on the right provider (AWS EU, GCP EU, Hetzner, OVH). Cost-tagged and right-sized from day one.

  3. IaC implementation

    Everything in Terraform or Pulumi. Version-controlled, peer-reviewed, rebuildable from scratch in minutes. Zero console-clicking.

  4. Migration

    Move workloads with zero downtime. Data stays in EU at every step. Kill unused resources and optimize as you go.

// TYPICAL 8-WEEK DELIVERY

assessment
wk 1

blueprint
wk 2–3

iac implementation
wk 4–6

migration
wk 7–8

Production-ready in under 8 weeks: infrastructure deployed via IaC, monitoring in place, CI/CD running, your team trained.

// typical anchors: architecture audit from €5,900 net (fixed) · fixed-scope builds from €12,000 net · fractional lead from €1,200 net/day

# THE-STACK

Production-tested tools, not a wish list.

AWSGCPHetznerTerraformPulumiSnowflakeBigQuerydbtApache IcebergDockerKubernetes

# DEFINITION

What is cloud architecture consulting?

Cloud architecture consulting involves designing right-sized, EU-sovereign infrastructure on AWS, GCP, or Hetzner with infrastructure-as-code, cost optimization, and data residency compliance. We architect and migrate data platforms with IaC, cost controls, and CLOUD Act risk mitigation.

# FAQ

Common questions.

  • Do you work with AWS, GCP, or both?
    Both. We're cloud-agnostic and choose based on your existing stack, team skills, and compliance requirements. For EU data residency, we often recommend Hetzner for non-cloud-native workloads.
  • How do you handle the CLOUD Act risk for EU companies?
    We design architectures that keep sensitive data on EU-sovereign infrastructure wherever possible. For workloads that need AWS/GCP, we use EU-only regions, encryption-at-rest with customer-managed keys, and contractual safeguards. We quantify your actual exposure and reduce it — we don't pretend the risk disappears entirely.
  • What does "production-ready in 8 weeks" actually mean?
    It means infrastructure deployed via IaC, monitoring in place, CI/CD running, documentation written, and your team trained. Not a sandbox — a system you'd trust on a Monday morning.

Ready to put cloud architecture into production?

A 30-min call. We'll bring an architecture sketch and a rough number.

 book-call

// or write: hello@saloid.com · gräfelfing · de