Skip to main content

EU hosting → Germany

Spring Boot Hosting in Germany

German Spring Boot teams want JVM hosting that respects container memory limits, has DSGVO-clean residency, and lets ops speak German. Hostim runs Spring Boot in Falkenstein. Single-digit ms RTT to Berlin, Munich, Frankfurt.

Try Spring Boot on HostimAll Spring Boot docs
# docker-compose.yml
services:
  app:
    image: my-spring-app
    environment:
      - SPRING_PROFILES_ACTIVE=prod
      - SPRING_DATASOURCE_URL=jdbc:postgresql://db:5432/app
  db:
    image: postgres:16
  • 🇪🇺 Hosted in Germany, GDPR by default
  • 🐳 Run Docker apps (Compose supported)
  • 🗄️ Built-in MySQL, Postgres, Redis & volumes
  • 🔐 HTTPS, metrics, and isolation per project
  • 💳 Per-project cost tracking · from €2.5/month

Why Spring Boot on EU bare metal for Germany

Spring Boot is the default backend in German enterprise Java. The deployment artifact is a fat JAR or a layered Docker image; the database is usually PostgreSQL or MySQL. Hostim runs the container with managed PostgreSQL attached. Set JAVA_TOOL_OPTIONS=-XX:MaxRAMPercentage=75 so the JVM heap matches the container memory limit. JVM metrics export to Prometheus — visible in the Hostim dashboard.

Latency, residency and German regulators

Latency. Typical RTT from Berlin to our Falkenstein region is around 8 ms. Germany has the strictest interpretation of GDPR in the EU and is the largest EU market for paid hosting. Falkenstein is in Saxony, Germany — Hostim runs entirely on bare metal in this region.

Regulator. BfDI (federal data protection commissioner) and BSI (federal cyber security agency).

Local law. BDSG (Bundesdatenschutzgesetz), the German federal data protection act that complements GDPR. Hostim is operated by HOSTIM.DEV UG, a German company, with all data in Falkenstein, Germany — there is no transfer outside the EU for application data.

Local alternatives you may have considered: IONOS Cloud, Strato, OVH-DE, Hetzner Cloud (raw VPS).

How Hostim runs Spring Boot

Spring Boot apps ship as a single fat JAR or as a layered Docker image. Production deployment means running that artifact under a JVM with the right heap settings, plus a managed database. Spring Boot 3 is fully container-aware.

Deploy model

Build your image with the Spring Boot Maven or Gradle plugin (jib or buildpacks both work). Hostim runs the container, attaches managed PostgreSQL, and exposes JVM metrics via Prometheus. Set JAVA_TOOL_OPTIONS to control the heap.

Common pitfalls

The default JVM heap is not sized for the container limit. Set JAVA_TOOL_OPTIONS=-XX:MaxRAMPercentage=75 so the heap matches the container memory you reserved.

Typical env vars

SPRING_PROFILES_ACTIVE, SPRING_DATASOURCE_URL, JAVA_TOOL_OPTIONS

FAQ

Wie konfiguriere ich den JVM-Heap?

Setze JAVA_TOOL_OPTIONS=-XX:MaxRAMPercentage=75 als Umgebungsvariable. Die JVM erkennt dann das Container-RAM-Limit korrekt und passt den Heap an.

Funktionieren Spring Boot Actuator endpoints?

Ja. Spring Boot Actuator läuft wie überall sonst. /actuator/health kann als Health-Check-Pfad konfiguriert werden, damit Hostim Rolling Deploys korrekt steuert.

How is this different from a Hetzner VPS with Docker?

On a VPS you install Docker, configure HTTPS, manage backups and PostgreSQL yourself. Hostim runs the same Hetzner bare-metal infrastructure but adds a managed PaaS layer — push a Dockerfile, get a running app with managed PostgreSQL.

Stellt ihr einen AV-Vertrag bereit?

Ja. Auftragsverarbeitungsvertrag (AVV) auf Anfrage, in deutscher oder englischer Sprache.

Related pages

Ready to deploy Spring Boot?

Spin up an app in minutes. Managed database on the free tier, custom domain included.

Deploy your Spring Boot appSee pricing