Cookies ahead

Our support chat tool "Intercom" would like to collect some more data on you. See the related link for more details.

Docs

Hetzner alternative for PHP hosting

Reviewed

Created

Markdown ↓

πŸ‡©πŸ‡ͺ

fortrabbit vs Hetzner.

fortrabbit is a Hetzner alternative for PHP teams who want managed hosting instead of a bare Linux VPS to maintain.

Hetzner alternative for PHP at a glance

fortrabbit is a managed PaaS built exclusively for PHP. Hetzner is excellent value for raw infrastructure β€” German-based, reasonably priced VPS, dedicated servers, and cloud compute. But Hetzner gives you a bare Linux server and root access; everything above the OS is your responsibility: web server, PHP-FPM, MySQL, SSL, patches, monitoring, backups.

If you want German / EU hosting without the sysadmin work, fortrabbit gives you a tuned PHP environment on top β€” git push deploys, integrated MySQL, atomic releases, persistent storage, SSL by default, and human support. You trade some control for far less operational overhead. Plans start at €2.50 per month; the trial doesn't require a credit card.

Hetzner vs fortrabbit β€” feature comparison

FeatureHetzner Cloudfortrabbit
AbstractionVPS, root accessManaged PaaS
PHP runtimeDIYPre-tuned, version-pinned
Web serverDIYManaged
Managed MySQLβ€”Native
DeploymentSSH, own scriptsgit push
SSL certificatesDIYAutomatic Let's Encrypt
Patching / updatesDIYManaged
BackupsDIYBuilt-in
RegionEU + USEU (Germany)
SupportEmail / docsHuman chat, all plans
Pricing modelPer-VPS, hourlyPer-app, monthly
Time-to-first-deployHoursMinutes

Pricing comparison

Use caseHetzner Cloud (DIY)fortrabbit
Small site / devCX11 €4 + your time setting it up€5 / mo
Production appCX21 €6 + your time maintaining it€30 / mo
Scaled appCCX or dedicated + sysadmin hours€60–€120 / mo depending on tier

Hetzner's monthly fee looks lower β€” until you count the engineering hours spent on stack setup, patching, monitoring, backups, and incident response. See fortrabbit pricing for the current matrix.

Migrating from Hetzner to fortrabbit

  1. Provision the app on fortrabbit. Pick a region (EU) and a plan. The free trial is enough to validate the move.
  2. Add the MySQL component. From your Hetzner server, mysqldump and import via fortrabbit's SSH tunnel β€” see MySQL import guide.
  3. Connect your git provider. Install the fortrabbit GitHub App (or connect GitLab / Bitbucket) and link your existing repo to the new fortrabbit app β€” see deployment intro. Pushes to your branch trigger an automatic deploy; Composer install runs as part of it.
  4. Move environment variables and secrets. Set them in the fortrabbit dashboard.
  5. Move uploads and assets. rsync from your Hetzner server into your fortrabbit app's persistent storage via SFTP / SSH.
  6. Cut over DNS. Add the domain in the fortrabbit dashboard, update the DNS record, and watch the certificate issue automatically via Let's Encrypt.
  7. Decommission the VPS. Once cutover is verified, retire the Hetzner server.

Why teams switch

  • No server maintenance. No patches, no firewall rules, no NGINX configs to debug at 11pm.
  • PHP-first ergonomics. Composer, OPcache, PHP version pinning, integrated MySQL.
  • Human support. You talk to engineers, not a ticket queue.
  • Predictable bills. Per-app monthly pricing, no per-hour math.

For background on Hetzner itself, see our hosting guide entry.

Start a free trial β€” no credit card

Written by AI, lectured by a human.

AI usage policy