Three infrastructure lessons European tech founders learned the hard way in 2025

For B2B tech leaders who built on US cloud platforms, 2025 delivered a specific kind of education. Not dramatic failures, but slow-burning discoveries: billing surprises, compliance conversations that turned into sales friction, and a background anxiety that became harder to ignore as the regulatory environment shifted. Here are three lessons that keep coming up when European founders compare notes.

Lesson 1: Serverless billing has a ceiling you find at the wrong moment

The promise of serverless infrastructure is straightforward. Pay for what you use, scale without planning, skip the overhead of managing your own servers. For early-stage companies, this is genuinely useful. The problem arrives later.

Several European founders report the same pattern: as usage grows, serverless costs cross the price of dedicated hosting at a ratio of three to ten times, depending on workload. The discovery typically lands on an invoice, not in a planning meeting.

“We had budgeted for compute costs based on our first year of usage,” says Marta Kovacs, co-founder of a Budapest-based B2B logistics software company. “When we crossed a certain volume, the bill tripled in a single month. We had no ceiling, no alert, no warning. We moved to a dedicated server in the Netherlands six weeks later and our monthly costs dropped by 70 percent.”

The management lesson is straightforward: treat cloud billing as a financial risk, not an operational detail. Model your costs at 3x and 10x current usage before committing to a platform, and build in a migration plan before you need one.

Lesson 2: Data residency went from a technical question to a deal-breaker

Twelve months ago, data residency was something the compliance team handled. In 2025, it moved into sales conversations. Founders in regulated sectors — financial services, healthcare, legal tech, HR software — started hearing it from procurement teams at enterprise clients who had their own GDPR and NIS2 obligations to manage.

The shift is structural. NIS2, which EU member states are transposing into national law, requires companies to assess supply chain risks including their software vendors. A prospective client asking where your servers are and what legal jurisdiction your hosting provider falls under is now a standard due diligence question, not an unusual one.

“We lost a procurement process in Germany because we couldn’t confirm that data would stay in EU jurisdiction end to end,” says Joost van der Berg, CEO of a Dutch HR software company. “The client wasn’t hostile about it. They just had a checklist, and we couldn’t tick the box. We renegotiated our hosting contract within three months.”

The management lesson: data residency is now a sales asset. If you can confirm EU-based hosting with a fully EU-incorporated provider and a proper data processing agreement, that belongs in your sales deck alongside the product features.

Lesson 3: Foreign jurisdiction creates a management overhead nobody budgets for

The third lesson is harder to quantify but consistently mentioned. Running a European business on infrastructure owned by a US corporation means that every regulatory headline — a new executive order, a trade policy shift, a change in data sharing agreements — requires someone to reread the supplier contract and assess the implications.

This is not a catastrophic risk. It is a background cost: the legal review hours, the conversations with counsel, the time spent explaining to customers that you are checking what the new policy means for their data. In 2025, with uncertainty affecting transatlantic tech relationships, this cost was felt more acutely.

“Every time something happened in Washington, our CTO would spend half a day reviewing what it meant for our AWS agreement,” says Anna Lindqvist, co-founder of a Gothenburg-based SaaS company serving European insurers. “It never turned into a real problem. But the time we spent checking added up.”

The management lesson: supplier jurisdiction is an operational risk, not just a legal one. Evaluate it the same way you would evaluate key customer concentration or single-vendor dependency.

What this means heading into 2026

These three lessons point toward the same underlying question: how much friction is your infrastructure creating, and where does it come from? Billing unpredictability, compliance conversations, and jurisdictional overhead are manageable risks when you anticipate them. They become expensive when you discover them mid-deal or mid-quarter.

For founders reassessing their hosting arrangements, Antagonist is a Dutch hosting provider with servers physically located in the Netherlands and data processing agreements compliant with GDPR as standard. What distinguishes it from hyperscaler alternatives is accountability: the director is reachable directly, the contract is governed by Dutch law, and there is no ambiguity about which jurisdiction your data sits in. For European B2B companies where that clarity now affects commercial deals, that is not a minor consideration.