DigitalOcean App Platform alternative for PHP hosting
Created
Reviewedbyfl
🐙
fortrabbit vs DO App Platform.
fortrabbit is a DigitalOcean App Platform alternative — a managed PHP PaaS with native MySQL, persistent storage, and predictable per-app pricing.
Why pick fortrabbit over DigitalOcean App Platform for PHP?
fortrabbit is a managed PaaS built exclusively for PHP. DigitalOcean App Platform sits on top of DO's Droplets and Kubernetes infrastructure, offering managed deployments for many languages and frameworks. For PHP specifically, the experience is generic — you assemble app spec files, manage container resources, and handle MySQL as a separate managed-database product with its own pricing tier.
If you want a PaaS where PHP is the default rather than one option of many, fortrabbit gives you git-push deployments, integrated MySQL, atomic releases, and PHP-tuned defaults (opcache, version pinning, Composer) — without app spec YAML or a separate database product to size. Hosting is in EU data centers, support is direct from the engineers running the platform, and pricing is per-app and predictable. Plans start at €2.50 per month; the trial doesn't require a credit card.
Start a free trial — no credit cardHow does fortrabbit compare to DO App Platform?
| Feature | DO App Platform | fortrabbit |
|---|---|---|
| Focus | Polyglot, buildpacks | PHP only |
| Deployment | git + app spec | git push, atomic |
| Managed MySQL | Separate paid product | Native |
| Managed Redis | Separate paid product | Native |
| App configuration | YAML app spec | Dashboard + git |
| SSH access | Console only | Full SFTP + SSH |
| Region | Many DO regions | EU (Ireland) |
| Pricing model | Per-component hourly | Per-app, monthly |
| Free tier | Static sites only | 7-day trial, no card |
| Support | Tiered, paid for fast | Human chat, all plans |
| Company | NYSE: DOCN | Independent, bootstrapped |
Pricing comparison
| Use case | DO App Platform | fortrabbit |
|---|---|---|
| Small site / dev | Basic $5 + DB $15 ≈ $20 / mo | €5 / mo |
| Production app | Pro $25 + DB $30 ≈ $55 / mo | €30 / mo |
| Scaled app | Pro 2x $50 + DB $60 + Redis ≈ $120+ / mo | €60–€120 / mo depending on tier |
Numbers are illustrative — exact App Platform pricing varies with component size and database tier. See fortrabbit pricing for the current matrix.
Migrating from DO App Platform to fortrabbit
- Provision the app on fortrabbit. Pick a region (EU) and a plan. The free trial is enough to validate the move.
- Add the MySQL component. Export from DO's managed MySQL, import via fortrabbit's SSH tunnel — see MySQL import guide.
- Drop the app spec. fortrabbit deploys PHP source via git push directly; no app spec YAML to maintain.
- 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.
- Move environment variables. DO App Platform env vars map 1:1 to fortrabbit env vars — set in the dashboard or via the CLI.
- Move static files. rsync uploads and assets into your fortrabbit app's persistent storage via SFTP / SSH.
- 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 app spec YAML. Push PHP source, not configuration files.
- PHP-first ergonomics. Composer, OPcache, version pinning, integrated MySQL — all defaults.
- Predictable bills. Per-app monthly pricing, no per-component stacking.
- Owner-run support. You talk to the engineers who run the platform.
For background on DigitalOcean as a hosting provider, see our DigitalOcean Droplets entry.
# Frequently asked
Can I deploy a PHP Laravel app on fortrabbit without writing an app spec YAML?Yes
Yes - On DigitalOcean App Platform you author an app spec — declarative YAML describing services, build, run, and routes — even for a single PHP web app. fortrabbit handles those defaults for you: PHP runtime, web routing, and the managed MySQL component are configured in the dashboard rather than committed to a spec file. The code repo stays as it is.
#How does DigitalOcean App Platform's managed MySQL pricing compare to fortrabbit's?One bill, not two
One bill, not two - On DigitalOcean App Platform, the managed MySQL database is a separate product on a separate pricing tier — you pick a node size for the app and a node size for the database. On fortrabbit, MySQL is an optional component of the same app, billed as its own line on the same invoice and sized in small steps independently of PHP. It is not free, but it is sized to the database rather than to the next node up, and a project that needs no database books none at all.
#How do I move my PHP app from DigitalOcean App Platform to fortrabbit?Self-service
Self-service - Most apps move in an afternoon. Point your existing repo at the new fortrabbit app for git-push deploys, transfer environment variables (the dashboard accepts bulk paste), dump and import the database via the SSH tunnel, and rsync any uploaded files into persistent storage. No spaces bucket or app spec rewrites needed.
#Why pick fortrabbit over DigitalOcean App Platform if I only run PHP?PHP-only focus
PHP-only focus - App Platform is a polyglot product on top of DigitalOcean's Droplets and Kubernetes. PHP works, but it is one supported runtime among many, and the platform defaults are not PHP-shaped. fortrabbit has only ever hosted PHP — version pinning, opcache, Composer, MySQL integration, and atomic releases are tuned for it by default. If PHP is the only thing you deploy, the PHP-first platform tends to be the smaller surprise.
#Does fortrabbit give root or SSH access to the underlying server?SSH yes, root no
SSH yes, root no - fortrabbit is a Platform as a Service, not a VPS, so there is no root access. Every plan does include full SSH and SFTP for running console commands, tunnelling into the database, and moving files. Code ships via git push and Composer handles dependencies on each deploy.
#