Skip to content
Services

Launch & Operations

Go-live for your MVP on EU-sovereign infrastructure (Hetzner, German data center, GDPR-compliant) plus ongoing operations with monitoring, incident response and scaling. Step L of the ANVIL system – part of a fixed-price engagement (from €36,000). Your sovereignty becomes a selling point with your own customers.

Last updated: 2026-06-26

Step L takes your MVP to where it creates value: live, under EU law, in your hands. We deploy your system on EU-sovereign infrastructure (Hetzner, German data center, GDPR-compliant) and take over ongoing operations – monitoring, incident response and scaling. In operation, your MVP grows into a platform. And your sovereignty turns from a technical detail into a selling point with your own customers: your data stays in Europe, your costs stay predictable.

2.1×
cheaper: Hetzner dedicated (CCX33) vs. AWS On-Demand at the same configuration
0
CLOUD Act exposure on EU-sovereign infrastructure
99.9%
availability SLA for production-critical systems in live operations
From €36,000
fixed-price engagement including go-live and operations handover – one engagement, one outcome

Step L: No sovereign operations, no real scaling

An MVP that only runs in a staging environment creates no value. And a production system that sits on US hyperscalers under foreign law creates dependency instead of scale – with unpredictable egress costs and a latent GDPR risk.

No sovereign operations → dependency instead of scale.

That's why: we take your MVP live on EU-sovereign infrastructure and run ongoing operations with monitoring, incident response and scaling. The result: your platform runs live, sovereign and under EU law. Your data stays in Europe, your costs stay predictable.

Step L is the final step of the ANVIL system. Every engagement – whichever entry path it begins on – ends here: in a production-ready go-live and stable operations.

Go-live on EU-sovereign infrastructure

The launch runs on Hetzner in a German data center – reproducible through infrastructure-as-code and with zero downtime:

  • Compute: Containerized application on Hetzner (German data center), as a K3s cluster with health checks and rolling deployments where needed
  • Database: Self-hosted PostgreSQL on Hetzner with automated backups
  • Infrastructure-as-code: Terraform for versioned, reproducible infrastructure instead of manually assembled servers
  • Zero-downtime launch: Blue-green deployment, with staging sign-off before the DNS cutover
  • GDPR-compliant configuration: Data processing exclusively in the EU, encryption at rest and in transit, logging without PII

US government access to data held by US cloud providers "cannot be reliably ruled out," according to an internal report by the German Federal Ministry of the Interior. Igor's Lab: BMI report on US data access (2025) On EU-sovereign infrastructure, this exposure disappears entirely. If you're coming from a US hyperscaler, we handle the migration to EU-sovereign infrastructure as part of Step L.

Sovereignty as your selling point

The real payoff of Step L isn't in the technology – it's in sales: sovereignty you can pass on to your own customers.

  • Guarantee instead of disclaimer: You can contractually guarantee that customer data never leaves Europe – no third-country transfer, no CLOUD Act exposure. Igor's Lab: BMI report on US data access (2025)
  • NIS2 supply chains: Since December 2025, NIS2 has required roughly 29,500 German companies to maintain documented cybersecurity measures – including those of their service providers. A sovereign platform makes you a low-friction supplier. BSI: NIS2 Implementation in Germany
  • Planning certainty against political risk: FISA Section 702 expired on June 12, 2026, and its reauthorization remains under debate. Should that lead to a Schrems III decision, competitors on US infrastructure would be under immediate pressure to act – you would not. Brennan Center: Section 702 FISA 2026 Resource Page

For more background, see our pages on the CLOUD Act data risk and the GDPR vendor audit.

Predictable costs: Hetzner vs. AWS

Sovereignty also lowers your operating costs and makes them predictable – with no egress surprises at the end of the month:

KriteriumHetzner (DE)AWS Frankfurt
8 vCPU / 16 GB RAM~€16/month (CX43, shared)~€148/month (m6i.xlarge On-Demand)
8 vCPU / 32 GB RAM (dedicated)~€138/month (CCX33)~€296/month (m6i.2xlarge)
1 TB block storage~€57/month~€84/month (gp3)
Traffic (20 TB/month)Included~€1,584 (egress costs)
Self-hosted PostgreSQL (16 GB)~€86/month (CCX23)From ~€243/month (RDS managed)
CLOUD Act exposureNoneFull
Hetzner: Cloud pricing (as of June 2026) AWS: EC2 On-Demand Pricing (as of 2026) AWS: RDS for PostgreSQL Pricing

According to Flexera, organizations estimate that an average of 27% of their IaaS and PaaS cloud spend is wasted – for example on idle or oversized resources. Flexera: 2024 State of the Cloud Report Our infrastructure-as-code approach on Hetzner avoids that waste through precise capacity planning and a transparent cost structure you can lay out for investors and customers. See the details in our Hetzner vs. AWS comparison.

Ongoing operations: monitoring, incident response, scaling

The go-live leads into an ongoing operations partnership – no handover vacuum, but a stably operated system:

  • Monitoring with OpenTelemetry, Grafana and Prometheus: health checks, distributed tracing and automated alerts on anomalies
  • Incident response with defined escalation tiers and response times
  • Regular security updates and dependency patches – the hardening from Step I is preserved in operation
  • Scaling and capacity planning based on real usage data, handled by the same senior team that built the system

Following Google's SRE principles, we set an error budget of 0.1% (99.9% availability) for production-critical systems. Google: SRE Book – Embracing Risk

In operation, your MVP grows into a platform

The terms follow a clear ladder: your prototype is the starting point, the MVP from Step I is the production-ready first version – and in live operation, that MVP grows into a platform. The system is designed from the outset to grow with you: from the first real customers to an established platform.

A full-scale expansion to enterprise architecture – horizontal scaling with K3s, read replicas, a dedicated team – is explicitly not a fixed part of the engagement and not a "Phase 6". It's an optional next step that you decide on from within operations, based on real load data, if and when your growth justifies it. You only pay for expansion once you actually need it.

Who is Step L for?

Every project begins with the paid analysis (Step A), whose fee is credited toward the engagement. Depending on what already exists, clients come in at different points – but all four entry paths ultimately run through Step L:

  • Idea → entry at A, then the full path through to a sovereign launch
  • Concept/design → entry at the new design (V)
  • Prototype → entry at implementation & hardening (I), the typical core case
  • Platform (broken or insecure) → direct entry at I/L: this is where Step L applies most directly, often as a migration to EU-sovereign infrastructure followed by operations

In every case the result is the same: a live, sovereign platform under EU law.

We take your system live on EU-sovereign infrastructure and run ongoing operations. Send us a short project description – we'll get back to you within 24 hours. The intro call (30 minutes) is free and no-obligation.

Frequently asked questions

What does launch and operations on EU infrastructure cost?
Launch and operations handover are part of our fixed-price engagement – one engagement, one fixed price, one outcome (fixed price from €36,000). There are no tiers or packages. Every project begins with the paid analysis (Step A), whose fee is credited toward the engagement. The exact scope and the binding price come out of the free initial consultation.
How much do I save with Hetzner compared to AWS?
At a comparable configuration, Hetzner is roughly 2.1× cheaper than AWS On-Demand. A dedicated server with 8 vCPU / 32 GB RAM costs ~€138/month on Hetzner vs. ~€296/month on AWS. On top of that come substantial traffic savings: 20 TB/month is included with Hetzner, while on AWS it costs ~€1,584.
Do I need EU infrastructure for GDPR compliance?
If you process personal data on US cloud infrastructure (AWS, Azure, GCP), you have a GDPR risk regardless of where the servers sit. The CLOUD Act obliges US providers to hand over data to US authorities. Operating on EU-sovereign infrastructure in a German data center removes that legal risk.
What happens after go-live?
Go-live leads into an ongoing operations partnership: monitoring with automated alerts, incident response with defined response times, regular security updates, architecture reviews and capacity planning. Not a support contract with a block of hours, but a stably operated system with clear SLAs.
Does my MVP grow into a full-fledged platform in operation?
Yes. The MVP is built to grow with you in operation – from the first real customers to an established platform. The further full-scale expansion to enterprise architecture (horizontal scaling, a dedicated team) is not a fixed part of the engagement and not a 'Phase 6,' but an optional next step that you decide on from within ongoing operations, based on real usage data.
Is sovereignty really a selling point?
Yes. A platform that demonstrably runs under EU law in a German data center is something you can sell to your own customers as a guarantee – especially in regulated industries, the public sector and NIS2-obligated supply chains. Data sovereignty thus turns from a compliance checkbox into a measurable competitive advantage.

Sources

Ready to start?

Book a free initial consultation. We assess your project and tell you exactly what it needs.