2026-05-17·5 min read·sota.io Team

Northflank EU Alternative 2026: Why UK Incorporation Changes Your GDPR Risk

Post #4 in the sota.io EU Serverless & PaaS Series

Northflank EU Alternative 2026 — UK jurisdiction and GDPR risk analysis

Northflank is a developer-favourite DevOps platform. Docker, Kubernetes, persistent volumes, managed databases — all wrapped in one clean interface. If you have tried Heroku and wanted more control, or tried raw Kubernetes and wanted less complexity, Northflank fills that gap elegantly.

But Northflank Ltd is incorporated in England and Wales. That single fact has real GDPR consequences in 2026 — consequences that Frankfurt servers and Hetzner infrastructure cannot fix.


Who Owns Northflank?

Northflank Ltd — Companies House registration CH12342786, incorporated England and Wales. Private company. No US parent — that is the good news. But post-Brexit, the UK is a third country under GDPR Art.44. And the UK has its own surveillance law: the Investigatory Powers Act 2016 (IPA 2016), which grants UK intelligence agencies far-reaching bulk data collection powers.

The CLOUD Act score is 3/25 — low compared to Heroku (22/25) or Zscaler (23/25), but the IPA 2016 creates its own category of risk that CLOUD Act analysis does not fully capture.

Key Corporate Facts

FieldDetail
Legal entityNorthflank Ltd
JurisdictionEngland and Wales (UK)
Reg. numberCH12342786
US parentNone
CLOUD Act exposure3/25 (no US parent)
Primary surveillance lawUK IPA 2016
InfrastructureHetzner Frankfurt + Amsterdam
PricingFrom $20/month (managed DB from $25)

CLOUD Act Score: 3/25

Northflank's CLOUD Act score is low because there is no US parent and no direct US law jurisdiction:

DimensionScoreReason
Legal entity0/5UK entity, no US incorporation
Intelligence-community ties1/5UKUSA/Five Eyes partner — UK GCHQ shares data with NSA under SIGINT agreements
Government contracts1/5No direct US federal contracts; UK government clients possible
Infrastructure control0/5Hetzner (German) for compute; UK data centres also offered
Compellability1/5UK Home Secretary can issue Technical Capability Notices (IPA 2016 s.252)

Total: 3/25 — far below Heroku (22/25), but not the 0/25 that a French or German entity achieves.


The Real Risk: UK Investigatory Powers Act 2016

The IPA 2016 (sometimes called the "Snoopers' Charter") gives UK intelligence agencies three major powers:

1. Bulk Interception Warrants (IPA 2016 Part 6)

GCHQ can intercept entire communications streams, not just targeted individuals. Section 136 authorises bulk equipment interference — essentially state-sponsored hacking of entire platforms or data centres if deemed necessary for national security.

2. Technical Capability Notices (IPA 2016 s.252)

The UK Home Secretary can compel any "telecommunications operator" to maintain technical capabilities for lawful interception — including decryption of end-to-end encrypted communications. A Northflank Technical Capability Notice would require them to decrypt your data on request.

3. National Security Notices (IPA 2016 s.229)

These can compel a company to maintain data in a specific form for interception. Unlike a CLOUD Act warrant, these notices carry a blanket secrecy obligation: Northflank could not even tell you a notice had been received.

Five Eyes Intelligence Sharing

The UK is a founding member of the UKUSA Agreement (Five Eyes): UK, USA, Canada, Australia, New Zealand. Under this agreement, GCHQ and NSA routinely share signals intelligence. In practice, this means a UK IPA 2016 bulk interception can make data accessible to the NSA without a CLOUD Act warrant. It is a different legal pathway to the same destination.


Why Frankfurt Infrastructure Does Not Help

Northflank offers EU regions: Frankfurt (Hetzner HEL1 and FSN1 equivalents) and Amsterdam. At first glance, this looks like a GDPR solution. It is not — for two reasons:

Reason 1: Jurisdiction follows the entity, not the server. GDPR Art.3 applies to controllers and processors established in the EU. Northflank Ltd is established in the UK. This makes Northflank a third-country processor under GDPR Art.44. You need a transfer mechanism (Standard Contractual Clauses or UK Adequacy Decision reliance) even if your data never leaves a Frankfurt data centre.

Reason 2: The UK Adequacy Decision has an expiry problem. After Brexit, the EU Commission granted the UK an adequacy decision (Art.45 GDPR) in June 2021 — valid for four years. This adequacy decision expires in June 2025 and must be renewed. As of this writing (May 2026), the UK adequacy decision has been extended, but EDPB has raised concerns about IPA 2016 compatibility with EU fundamental rights (EDPB Opinion 28/2023). Future renewal is not guaranteed. If adequacy lapses, every Northflank deployment in the EU requires immediate SCCs re-papering.

Reason 3: Control plane is UK. The Northflank dashboard, API, build system, deployment orchestration, and secrets management run from UK-controlled infrastructure. Even if your workloads run in Frankfurt, the control plane that configures and accesses them is under UK jurisdiction.


What Northflank Is Great For

To be fair: Northflank's developer experience is genuinely excellent.

For UK-based companies, UK government projects, or UK-exempt data: Northflank is a strong choice. The IPA 2016 risk is your government's own law, which simplifies the legal picture.

For EU-headquartered companies handling EU personal data: the third-country status introduces compliance overhead that EU-native alternatives avoid.


GDPR Compliance Analysis

Data Processing Agreement

Northflank offers a DPA. But a DPA with a UK entity does not eliminate the transfer mechanism requirement — it implements it. You need a DPA and SCCs (or adequacy decision reliance) and a Transfer Impact Assessment under Art.44.

Transfer Impact Assessment (TIA) Requirements

EDPB recommendations 01/2020 require a TIA when transferring to third countries. For Northflank (UK):

This is not impossible, but it adds compliance overhead that a French SAS or German GmbH controller avoids entirely.

Sub-processors

Northflank's sub-processor list includes services from multiple jurisdictions. Each sub-processor used in your Northflank deployment extends the transfer chain. Review their DPA Schedule for current sub-processor geography.


DORA and NIS2 Considerations

DORA Art.28 — Third-Country ICT Providers

For financial entities subject to DORA (banks, investment firms, payment processors), using a third-country ICT provider triggers additional scrutiny under Art.28(2). Competent authorities can request exit strategy documentation. The UK's adequacy uncertainty amplifies this risk: an adequacy lapse mid-contract creates a potential DORA compliance event.

NIS2 Art.21(2)(d) — Supply Chain Security

NIS2 requires essential and important entities to address supply chain security. A UK-incorporated PaaS provider represents a supply chain dependency under non-EU jurisdiction. Article 21(2)(d) requires policies to address security in network and information systems acquisition — including provider jurisdiction assessment.


EU-Native Alternatives

These platforms achieve 0-1/25 CLOUD Act score because they have no US parent and no US incorporation:

Scalingo SAS — Paris, France 🇫🇷

Best Northflank alternative for buildpack compatibility.

If your team comes from Heroku, Scalingo has the lowest migration friction of any EU-native platform.

Koyeb SAS — Paris, France 🇫🇷

Best for containerised serverless workloads.

sota.io — Germany 🇩🇪

Best for GDPR-zero-risk EU deployment with Hetzner compute.

The key difference from Northflank: same Hetzner infrastructure, but sota.io's control plane is under EU jurisdiction — no IPA 2016, no Five Eyes, no adequacy decision dependency.


Migration Guide: Northflank → EU-Native

If you are currently on Northflank and need to migrate for GDPR compliance, the path depends on your stack:

Buildpack-based apps (Node.js, Python, Ruby, PHP, Java)

→ Scalingo is the fastest path. Scalingo supports Heroku buildpacks. Your Procfile works as-is. Environment variables map 1:1. Managed add-ons (PostgreSQL, Redis) have direct equivalents.

Steps:

  1. git remote add scalingo git@ssh.osc-fr1.scalingo.com:<app-name>.git
  2. git push scalingo main
  3. Provision add-ons via Scalingo dashboard
  4. Point DNS

Containerised apps (Docker/docker-compose)

→ Koyeb or sota.io. Both accept Dockerfile or docker-compose.yml.

For Koyeb: Connect GitHub/GitLab repo → select Dockerfile → deploy. Persistent volumes attach via NFS mount.

For sota.io: Same pattern — Docker-based deploy with persistent volume support.

Database migration

Both Scalingo and sota.io offer managed PostgreSQL with pg_restore import. Northflank allows pg_dump export from managed PostgreSQL instances.


The Bottom Line

FactorNorthflankScalingoKoyebsota.io
EntityUK LtdFrench SASFrench SASGerman GmbH
CLOUD Act3/250/251/250/25
Surveillance lawIPA 2016GDPR directlyGDPR directlyGDPR directly
Transfer mechanism neededSCCs or AdequacyNoneNoneNone
Adequacy expiry riskYes (June 2025+)N/AN/AN/A
Hetzner EU infraOutscale/OVH✓ (EU PoPs)
Managed DB
DORA third-country riskYesNoNoNo
NIS2 supply chain riskYesNoNoNo
PricingFrom $20/moFrom €7.20/moFree tier / €25+From €9/mo

Northflank is an excellent platform for teams outside EU GDPR scope. For EU companies handling EU personal data — especially those subject to DORA, NIS2, or sector-specific regulation — the IPA 2016 exposure and UK adequacy uncertainty create compliance overhead that 0/25 alternatives avoid.


See Also

Next in the series: EU Serverless PaaS Comparison Finale 2026 — Netlify, Fly.io, Heroku, Northflank, and EU-native alternatives side-by-side in a complete risk matrix.

EU-Native Hosting

Ready to move to EU-sovereign infrastructure?

sota.io is a German-hosted PaaS — no CLOUD Act exposure, no US jurisdiction, full GDPR compliance by design. Deploy your first app in minutes.