# Render alternative for PHP hosting

> 

## Render alternative for PHP at a glance

**fortrabbit is a managed PaaS built exclusively for PHP.** Render is a polyglot PaaS with a beautiful UI and reasonable defaults for Node, Python, Go and Docker — PHP works, but as a generic Docker workload, not a first-class environment. Persistent disks are paid-only, build timings can be slow, and pricing leans toward larger apps.

If you're hosting PHP — Laravel, Symfony, Statamic, Craft CMS, Kirby, or plain PHP — fortrabbit gives you the same git-push workflow without the Docker step in the middle. PHP versions, opcache, Composer, atomic deploys, and integrated MySQL just work. Hosting is in EU data centers, and pricing is per-app and predictable. Plans start at €2.50 per month; the trial doesn't require a credit card.

## Render vs fortrabbit — feature comparison

<table>
<thead>
  <tr>
    <th>
      Feature
    </th>
    
    <th>
      Render
    </th>
    
    <th>
      fortrabbit
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Focus
    </td>
    
    <td>
      Polyglot, Docker
    </td>
    
    <td>
      PHP only
    </td>
  </tr>
  
  <tr>
    <td>
      Deployment
    </td>
    
    <td>
      git + Dockerfile
    </td>
    
    <td>
      git push, no Docker
    </td>
  </tr>
  
  <tr>
    <td>
      Managed MySQL
    </td>
    
    <td>
      —
    </td>
    
    <td>
      Native
    </td>
  </tr>
  
  <tr>
    <td>
      Managed Postgres
    </td>
    
    <td>
      Yes
    </td>
    
    <td>
      —
    </td>
  </tr>
  
  <tr>
    <td>
      Persistent disks
    </td>
    
    <td>
      Paid plans only
    </td>
    
    <td>
      Included
    </td>
  </tr>
  
  <tr>
    <td>
      SSH access
    </td>
    
    <td>
      Limited
    </td>
    
    <td>
      Full SFTP + SSH
    </td>
  </tr>
  
  <tr>
    <td>
      Region
    </td>
    
    <td>
      US, EU, Asia
    </td>
    
    <td>
      EU (Germany)
    </td>
  </tr>
  
  <tr>
    <td>
      Pricing model
    </td>
    
    <td>
      Per-service hourly
    </td>
    
    <td>
      Per-app, monthly
    </td>
  </tr>
  
  <tr>
    <td>
      Free tier
    </td>
    
    <td>
      Cold starts
    </td>
    
    <td>
      30-day trial, no card
    </td>
  </tr>
  
  <tr>
    <td>
      Support
    </td>
    
    <td>
      Community, paid fast
    </td>
    
    <td>
      Human chat, all plans
    </td>
  </tr>
  
  <tr>
    <td>
      Company
    </td>
    
    <td>
      Venture-backed
    </td>
    
    <td>
      Independent, bootstrapped
    </td>
  </tr>
</tbody>
</table>

## Pricing comparison

<table>
<thead>
  <tr>
    <th>
      Use case
    </th>
    
    <th>
      Render
    </th>
    
    <th>
      fortrabbit
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Small site / dev
    </td>
    
    <td>
      Starter $7 + DB $7 ≈ <strong>
        $14 / mo
      </strong>
    </td>
    
    <td>
      <strong>
        €5 / mo
      </strong>
    </td>
  </tr>
  
  <tr>
    <td>
      Production app
    </td>
    
    <td>
      Standard $25 + DB $20 + disk ≈ <strong>
        $50+ / mo
      </strong>
    </td>
    
    <td>
      <strong>
        €30 / mo
      </strong>
    </td>
  </tr>
  
  <tr>
    <td>
      Scaled app
    </td>
    
    <td>
      Pro $85+ DB $90+ ≈ <strong>
        $175+ / mo
      </strong>
    </td>
    
    <td>
      <strong>
        €60–€120 / mo
      </strong>
      
       depending on tier
    </td>
  </tr>
</tbody>
</table>

Numbers are illustrative — exact Render pricing varies with region, instance size, and add-on choice. See <content-link href="/pricing" text="fortrabbit pricing">



</content-link>

 for the current matrix.

## Migrating from Render 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.** If you were on Render Postgres, plan a schema port; if you brought your own MySQL externally, `mysqldump` and import via fortrabbit's SSH tunnel — see <content-link href="/guides/general/mysql-import" text="MySQL import guide" prefix="docs">



</content-link>

.
3. **Drop the Dockerfile.** fortrabbit deploys PHP source via git push; you don't need to maintain a container image.
4. **Connect your git provider.** Install the fortrabbit GitHub App (or connect GitLab / Bitbucket) and link your existing repo to the new fortrabbit app — see <content-link href="/platform/deployment/intro" text="deployment intro" prefix="docs">



</content-link>

. Pushes to your branch trigger an automatic deploy; Composer install runs as part of it.
5. **Move environment variables.** Render env vars map 1:1 to fortrabbit env vars — set in the dashboard or via the CLI.
6. **Move persistent files.** rsync from the Render disk into your fortrabbit app's persistent storage via SFTP / SSH.
7. **Cut over DNS.** Add the domain in the fortrabbit dashboard, update the CNAME, and watch the certificate issue automatically via Let's Encrypt.

## Why teams switch

- **No Docker overhead.** Push PHP source, not container images.
- **PHP-first ergonomics.** Composer, OPcache tuning, PHP version pinning, integrated MySQL.
- **Predictable bills.** Per-app monthly pricing, no per-service stacking.
- **Owner-run support.** You talk to the engineers who run the platform.

For background on Render itself, see our <content-link href="/hosting-guide/providers/paas/render" text="hosting guide entry">



</content-link>

.

<content-button property="dashboard" route="/signup" text="Start a free trial — no credit card">
<content-button property="www" route="/pricing" text="See pricing" variant="secondary">



</content-button>
</content-button>