Service 05 / 06

Operations with an honest bill.

Infrastructure as code instead of grown handiwork, and a cost calculation that knows the way back as well.

When this fits

Four situations in which this service is the right answer.

01.1
The cloud bill rises every month, and nobody can say what for.
01.2
The infrastructure was built by clicking and exists exactly once, undocumented.
01.3
A move is coming up, and the question is whether the cloud is the right answer at all.
01.4
Data protection requires certain data to stay in the EU, and the current architecture doesn't know where it lives.

How I work

Order and stance. The four steps themselves are under Process.

First the bill: what does operation cost today, what does it cost in the proposed architecture, and what does the way there cost? Cloud is not automatically cheaper, your own infrastructure not automatically dearer. The answer hangs on load, data and team. We work it out for you before anything is migrated.

Infrastructure is described as code and generated from it. That makes it repeatable, reviewable and yours. A second setup in another region or at another provider then takes hours rather than weeks.

I decide where data lives on purpose rather than leaving it to the provider's default. EU processing is the starting point.

What you get

What belongs to you at the end and lives in your accounts.

03.1
Cost and capacity planning with variants: cloud, own infrastructure, hybrid
03.2
Infrastructure as code, versioned and with a change review before every intervention
03.3
A migration plan into the cloud or out of it, with a way back at every step
03.4
Operations documentation covering access, responsibilities and recovery

When I advise against it

The cases where I advise against it, told to you before the engagement.

I recommend a provider because it fits the load, not because I happen to know it well. And I don't migrate to the cloud when a well-run server does the job for a fraction of the cost.

Questions

What is usually asked about this service.

01Cloud or your own server?

It hangs on load, data and your team. Steady load often favours your own infrastructure, strongly varying load the cloud; data protection and operational effort pull in both directions. That calculation is part of the clarification.

02Can you take over operations?

As ongoing support, yes. The goal remains that your team can run operations itself, and the documentation is written for exactly that.

03Which providers do you use?

Cloudflare, Vercel and classic Linux infrastructure most often; I reach for the large hyperscalers where their services are genuinely needed. The requirement picks the provider. From Mainz, for teams across Germany.

Let's talk.

You get an honest first assessment — including the times I tell you not to do it.

E-mail: kontakt@navigaite.de
Phone: +49 156 79701573
Response time: The same working day.
Privacy: No cookies. No trackers. No banner.
Location: Mainz, DeutschlandMainz