Europa-only Alternative zu Oracle Cloud (OCI).
Oracle Cloud Infrastructure is the smallest of the major hyperscalers in EU mid-market but punches above its weight in regulated industries because of the Oracle Database lock-in. Oracle Corporation is a US company; OCI EU regions (Frankfurt, Amsterdam, Marseille, Milan, Madrid, Stockholm, Zurich) are EU-located but US-controlled under the CLOUD Act. Oracle has marketed "EU Sovereign Cloud" since 2023 — operationally separated EU regions with EU-resident staff — but the parent jurisdiction is unchanged. For Schrems II–strict analyses, that is not full sovereignty.
"EU-Region" ist keine Souveränität. Vier Fragen entscheiden.
Datenresidenz sagt, wo die Daten liegen. Souveränität sagt, welches Rechtssystem Zugriff erzwingen kann. Die Antwort muss in allen vier Punkten stimmen — sonst ist der Stack nicht souverän.
Wo sind die Daten physisch gespeichert?
Nicht "in der Cloud" — welches Rechenzentrum, in welchem Land, unter welcher Rechtsordnung.
Wer ist sonst noch in Ihrem Datenpfad?
Jeder Anbieter, der die Daten berührt: das CDN, das E-Mail-Relay, der Error-Tracker, die Analytics-Pipeline.
Wessen Gesetze können die Offenlegung erzwingen?
Ein Anbieter mit US-Hauptsitz unterliegt FISA 702 und dem CLOUD Act — auch wenn die Daten in Frankfurt liegen.
Wer hält tatsächlich die Verschlüsselungsschlüssel?
Wenn der Cloud-Anbieter sowohl die Daten als auch die Schlüssel besitzt, sind die Daten für ihn lesbar — unabhängig von einer AVV.
Scheitert an Rechtsmacht und Schlüsselverwahrung.
EU-Daten, US-Mutterkonzern, US-Subprozessoren im Standardpfad, vom Anbieter verwaltete Schlüssel.
Besteht in allen vier Punkten.
EU-gehostet auf Infrastruktur mit EU-Hauptsitz. Null US-Subprozessoren im Standardpfad. Kunden- oder EU-KMS-Schlüssel. Namentlich in Ihrer Artikel-28-AVV aufgeführt.
Warum Teams aussteigen Oracle Cloud (OCI)
Oracle exits we have run almost always involve a database migration in addition to infrastructure — typically Oracle DB → PostgreSQL, which is a substantial project on its own. The triggers: a financial services audit under DORA flagging Oracle as a US-jurisdictional concentration risk, a cost review that uncovered the true Oracle DB licensing exposure on cloud, or a strategic decision to remove the Oracle dependency entirely. The mid-term saving is dramatic when both the OCI infrastructure cost and the Oracle DB licence cost are eliminated.
Oracle Cloud (OCI) Dienste und ihre EU-only Äquivalente
Eine Migration ist nicht "eine Box gegen eine andere tauschen". Die Zuordnung unten ist das, was wir für Kunden ausführen, die Folgendes verlassen: Oracle Cloud (OCI) aus Schrems-II-Gründen — volle EU-Rechtsmacht, keine US-Mutter im Datenpfad.
| Oracle Cloud (OCI) Dienst | EU-only Alternative | Engineering-Hinweis |
|---|---|---|
| Compute Instances | Hetzner Cloud, OVH Public Cloud, Scaleway, IONOS Compute | Standard VM migration; image rebuild and rebase. Oracle Linux can be replaced with Rocky or Alma without application impact. |
| Object Storage | OVH Object Storage, Wasabi EU, Bunny Storage, MinIO self-hosted | OCI Object Storage has a non-S3-compatible API; the rewrite is small but requires SDK changes. |
| Autonomous Database | PostgreSQL on EU managed (OVH, Aiven) or self-managed; for compatibility-critical workloads, EnterpriseDB Postgres EU | The longest single migration task. Tools like ora2pg and Cybertec's migrator have improved significantly. Plan a 3–9 month parallel run depending on schema complexity. |
| OKE (Oracle Kubernetes Engine) | Scaleway Kapsule, OVH Managed K8s, Talos on Hetzner | Helm charts and YAML transfer cleanly; OKE-specific features (Container Engine for Kubernetes managed nodepools) replaced with standard equivalents. |
| Block Volumes | Hetzner Volumes, OVH Block Storage, Scaleway Block Storage | Volume migration via snapshot + restore. |
| Virtual Cloud Network (VCN) | Hetzner private networks, OVH vRack, Scaleway Private Networks | OCI VCN concepts (subnets, route tables, NAT gateways) map directly to standard cloud networking. |
| Functions (FaaS) | Scaleway Serverless Functions, OpenFaaS or Knative on EU K8s | Migration is mechanical; OCI Functions is built on Fn Project so the runtime model is portable. |
| Streaming (Kafka-compatible) | Aiven Kafka EU, self-managed Apache Kafka on EU compute, Redpanda | Kafka migration is a producer/consumer redirect; data replication via MirrorMaker. |
| API Gateway | Kong (self-hosted), Tyk (UK with EU options), KrakenD (ES) | KrakenD is Spanish-headquartered and a strong sovereign choice. |
| Load Balancer | Hetzner LB, OVH Load Balancer, HAProxy self-managed | Standard L4/L7 load balancing. |
| Vault (KMS) | Hashicorp Vault on EU infra, HSM-backed key management | Vault is the production-grade sovereign answer. |
| Logging / Monitoring | Self-hosted Prometheus + Grafana + Loki, Grafana Cloud EU | OpenTelemetry instrumentation makes the application-side migration mechanical. |
Wie wir migrieren von Oracle Cloud (OCI)
Eine typische Mittelstand-Migration läuft in drei Phasen. Die Zahlen unten gehen von einem 6–10-köpfigen Engineering-Team und einem mäßig komplexen Anwendungs-Stack aus.
Database scope decision
Map every Oracle DB-specific feature in use (PL/SQL, Oracle Text, partitioning, materialized views, hierarchical queries, Oracle Spatial). Decision point: full migration to PostgreSQL or hybrid (compatibility-critical workloads on EnterpriseDB Postgres EU). This is the schedule-defining task.
Infrastructure migration
Compute, networking, storage moved to EU sovereign stack. K8s workloads moved. Object storage migrated with API rewrites where needed. CI/CD repointed.
Database cutover
Schema converted with ora2pg. Data migrated with logical replication or change-data-capture for live workloads. Application code reviewed for Oracle-specific SQL. Cutover window scheduled with full rollback plan.
5-year TCO on full Oracle exits (infrastructure + database): typically 50–70% cheaper. The largest savings come from eliminating Oracle DB licensing (per-core enterprise pricing is brutal) followed by EU IaaS being ~40% cheaper than OCI on equivalent specs. The database conversion project itself is the largest one-time cost but pays back inside year 2.
Häufig gestellte Fragen
What about Oracle EU Sovereign Cloud?
Oracle EU Sovereign Cloud (launched 2023, regions in Madrid and Frankfurt) is operated by EU-resident Oracle staff with operational separation from non-EU Oracle. It is an improvement on the documentation story for many regulated workloads — but Oracle Corporation remains the legal owner of the data. For Schrems II analyses that turn on parent jurisdiction, it is not full sovereignty.
Can we keep Oracle DB and just leave OCI?
Yes. EnterpriseDB Postgres Advanced Server (EU-hosted) maintains Oracle compatibility at the SQL/PL-SQL level for most workloads. For mid-complexity Oracle DB applications, EDB on EU infrastructure is a viable path that doesn't require a full database migration.
How big is the database migration project really?
For a typical mid-market Oracle DB (50–500GB, modest PL/SQL surface, no Oracle-specific features beyond standard SQL): 3–6 months parallel-run, 2–4 weeks for the cutover itself. For a heavy PL/SQL or Oracle-feature-dependent application: 9–18 months. The honest scoping is best done by people who have done it before.
What about Oracle Fusion Apps and Oracle ERP Cloud?
These are SaaS, not infrastructure — same conversation as Microsoft 365 or Salesforce. The decision to move off them is strategic, not infrastructural. We focus on the OCI infrastructure layer; the SaaS migration is typically a separate project run by a business-systems consultancy.
Is OCI actually competitive on pricing?
OCI's headline IaaS pricing is competitive vs AWS/Azure/GCP. Where OCI gets expensive is the database licensing on cloud (Oracle DB BYOL costs are high). For pure compute, the EU sovereign stack is still 30–40% cheaper. For Oracle DB workloads, the comparison is dominated by the licence, not the compute.
How long does an Oracle exit take end-to-end?
For infrastructure-only (no DB migration): 8–14 weeks. For full exit including PostgreSQL migration: 6–18 months elapsed time depending on database complexity. The schedule risk is entirely on the database side.
Plane deinen Exit von Oracle Cloud (OCI).
30-minütiges Scoping-Gespräch. Wir bilden Ihren Stack auf EU-only Alternativen ab, schätzen den Migrationsaufwand und sagen Ihnen, ob es die richtige Entscheidung ist.