Best Heroku alternatives for PHP teams in 2026

Heroku is a Platform-as-a-Service (PaaS) that has hosted PHP applications for over a decade. It runs PHP through the official Heroku PHP buildpack, with Composer, Apache or Nginx, and Git-based deploys. Laravel, Symfony, WordPress, and Drupal teams run production workloads on it.

Heroku still does several things well. The buildpack supports recent PHP versions, the deploy model is predictable, and a mature add-on marketplace covers databases, search, monitoring, and scheduling. 

The trade-offs are structural. The 30-second router timeout (H12) terminates long CMS exports, Magento reports, and Composer admin tasks. The ephemeral filesystem loses files written to a dyno, including WordPress media and Drupal uploads. Add-on billing fragments a production PHP setup across several vendors. 

Key takeaways

• This guide covers Platform-as-a-Service (PaaS) and developer platforms that PHP teams move to when they outgrow Heroku, as of 2026.
• Upsun is the strongest fit for production PHP teams running CMSes or multi-framework portfolios that need native PHP, persistent storage, an integrated managed services catalog, and preview environments with real production data.
• Other alternatives suit specific PHP profiles: Laravel-only teams (Laravel Cloud), low-friction buildpack migration (DigitalOcean App Platform), container-native teams (Render), and edge-latency workloads (Fly.io).
• Every platform is evaluated against six consistent criteria: PHP runtime support, persistent storage, managed services, background workers, preview environments, and multi-cloud or migration path.

Why PHP teams look beyond Heroku in 2026

Three Heroku design choices push PHP teams to reassess. 

• A 30-second router timeout. Heroku terminates any web request that takes longer than 30 seconds, returning an H12 error, and its own documentation recommends keeping in-app timeouts to 10 to 15 seconds. That works for APIs but is painful for CMS exports, Magento report generation, and long Composer-driven admin tasks.
• An ephemeral filesystem. Any file written directly to a dyno, including WordPress media, Drupal files, and admin-installed plugins, is lost when the dyno restarts or scales. Production PHP teams work around this by adding S3 and a third-party plugin, which costs add-on dollars and developer time.
• An add-on bill for every service. Heroku charges Postgres, Redis, search, scheduling, and monitoring as separate add-ons, so a production-grade PHP setup means several contracts, several bills, and several vendor relationships to manage.

The platform still works. It just stopped being the lowest-friction PHP host years ago.

What to look for in a Heroku alternative for PHP

The criteria below structure the comparison and map directly to the columns of the comparison table.

• PHP runtime and version support. Whether the platform runs PHP natively or only through a Dockerfile, which PHP versions are supported, and whether PHP-FPM workers, Composer, and PHP extensions are configurable without custom container work.
• Persistent storage for CMS workloads. Whether the platform provides a persistent file mount that survives deploys and restarts. This is what allows WordPress media, Drupal files, and Magento product images to live on the application platform instead of being offloaded to S3 or Spaces.
• Managed databases and search. Whether PostgreSQL, MySQL, or MariaDB, Redis, and a search engine such as OpenSearch are offered as first-class managed services, rather than as separate vendor add-ons.
• Background workers and scheduled jobs. Whether Laravel Horizon, Symfony Messenger consumers, Drush cron, and other long-running PHP processes can run in dedicated worker containers that scale independently of the web tier.
• Preview environments and profiling. Whether the platform creates an isolated environment for every Git branch, whether that environment can include real production data, and whether PHP profiling tools such as Blackfire are available natively.
• Multi-cloud support and Heroku migration path. Whether the platform supports deployment across multiple clouds, and how compatible its build and runtime model is with an existing Heroku PHP application.

The best Heroku alternatives for PHP teams in 2026

1. Upsun

A multi-cloud application platform with native PHP, persistent storage, and an integrated managed services catalog built around production PHP workloads.

Upsun runs PHP as a first-class native runtime, supporting the latest PHP versions. Code and infrastructure are described in a single YAML configuration file: PHP-FPM workers, extensions, and Composer dependency management are configured in the same place. Every Git branch produces a preview environment that clones production code, configuration, and live data in under one minute.

Key capabilities:

• Native PHP runtime with configurable PHP-FPM workers and extensions via YAML.
• Persistent storage mounts for WordPress media, Drupal files, and Magento product images.
• Managed services catalog: PostgreSQL, MySQL, Redis, Elasticsearch, OpenSearch, RabbitMQ, and Kafka.
• Dedicated worker containers for Laravel Horizon, Symfony Messenger, and Drush cron.
• Multi-cloud deployment across AWS, GCP, Azure, OVHcloud, and IBM Cloud.
• Blackfire available as a PHP extension for application-level profiling.
• Compliance with ISO 27001, SOC 2 Type 2, PCI DSS Level 1, HIPAA, TX-RAMP, and GDPR.

Best for: Production PHP teams running CMSes, multi-framework portfolios, or compliance-sensitive workloads that need native PHP, persistent storage, and preview environments with real production data.

2. Laravel Cloud

Laravel Cloud is Laravel's own hosting product, built specifically for Laravel applications. It offers autoscaling queue workers that track CPU, memory, and job backlog, PR preview environments, and a control plane that understands Artisan commands and Horizon. Managed databases include MySQL and serverless Postgres, with the option to connect to external databases.

The trade-off is the obvious one: Laravel Cloud only runs Laravel applications. If your team also maintains a Drupal site, a Symfony API, or a Magento store, you need a second platform. Teams running other PHP frameworks or CMSes should not choose Laravel Cloud as their primary host.

Key capabilities:

• Laravel-specific autoscaling for queue workers and the web tier.
• PR preview environments aligned with Laravel conventions.
• Managed MySQL and serverless Postgres, plus external database support.
• Entry-level tier with spend caps and millisecond scale-to-zero.

Best for: Teams whose entire PHP portfolio is Laravel and who want a platform built around Laravel conventions.

3. DigitalOcean App Platform

A managed PaaS that uses the Heroku PHP buildpack directly, offering the lowest-friction Heroku migration path.

DigitalOcean App Platform supports Git-based deployment from GitHub, GitLab, and Bitbucket. Per DigitalOcean's documentation, it runs heroku-buildpack-php and supports PHP runtime versions 8.1 through 8.5, so existing composer.json and runtime configuration typically work without modification. Managed Postgres, MySQL, and Redis are available alongside.

Key capabilities:

• Git-based deployment using heroku-buildpack-php.
• PHP runtime versions 8.1 through 8.5.
• Managed Postgres, MySQL, and Redis.
• Integration with DigitalOcean Spaces for object storage.

Best for: Teams looking for the fastest, lowest-rewrite Heroku migration path on a single cloud.

4. Render

A plan-based PaaS for PHP teams already comfortable maintaining a Dockerfile.

Render does not provide a native PHP runtime. Its documentation lists Node.js, Bun, Python, Ruby, Go, Rust, and Elixir as natively supported languages and directs PHP users to Docker. For teams already standardized on containers, the rest of the developer experience is clean: managed Postgres, Key Value (Redis), background workers, cron jobs, persistent disks, and plan-based pricing.

Key capabilities:

• PHP deploys via Dockerfile, with an official Laravel Docker guide.
• Managed Postgres and Key Value (Redis).
• First-class background workers and cron jobs.
• Persistent disks for stateful workloads.

Best for: PHP teams that have already standardized on Docker and want a clean, plan-based PaaS for container-native deployment.

5. Fly.io

A container platform for global, edge-deployed PHP applications.

Fly.io runs Docker containers as lightweight VMs across 18 regions, according to Fly.io's regions documentation as of 2026. The platform supports FrankenPHP, the modern PHP application server, on its container model, and Laravel and PHP tooling have visible team support. Usage-based billing meters compute, bandwidth, volumes, dedicated IPv4 addresses, and inter-region networking separately.

Key capabilities:

• Multi-region container deployment across 18 Fly.io regions
• FrankenPHP runs cleanly on the container model
• Persistent volumes for stateful workloads
• Anycast networking with static IP support

Best for: PHP teams whose product depends on low-latency, edge-distributed delivery across geographies.

Quick look: how the five Heroku alternatives compare

 Choosing the right alternative

The core trade-off in moving off Heroku for PHP work is how much of Heroku's design you want to keep. The 30-second timeout, ephemeral filesystem, and add-on-style billing are not random choices: they are the cost of an abstraction that entirely hides the infrastructure. Alternatives that keep that abstraction, including DigitalOcean App Platform with the Heroku buildpack, deliver a fast migration but inherit a similar shape. Alternatives that loosen the abstraction, such as Upsun and Render, give you more control over runtime, storage, and services.

For Laravel-only portfolios, Laravel Cloud is the most opinionated and direct fit. For a fast, buildpack-compatible move, DigitalOcean App Platform is the closest match. For container-native PHP teams, Render is a clean choice. For edge-distributed workloads, Fly.io is the natural option. Upsun is the strongest fit for production PHP teams running CMSes or multi-framework portfolios that need native PHP without a Dockerfile, persistent storage for media, an integrated managed services catalog, and preview environments with real production data.

Frequently Asked Questions (FAQs)

Does Heroku still have first-class PHP support in 2026?

Heroku still maintains an official PHP buildpack supporting recent PHP versions, with Composer-based dependency management and a choice of Apache or Nginx. The PHP runtime itself is current. What has not changed is the platform model: the 30-second router timeout, ephemeral filesystem, and add-on-based services still shape how a PHP application has to be designed for Heroku, regardless of the PHP version on top.

Why do PHP teams move away from Heroku?

The three most cited reasons in 2026 are cost compounding across add-ons, the ephemeral filesystem breaking common CMS upload patterns, and the loss of the permanent free tier in 2022, which removed the cheap on-ramp many small PHP projects depended on. Teams looking for production-grade testing and multi-cloud flexibility also tend to outgrow Heroku's single-region, single-cloud model.

Does Upsun support PHP, and which versions?

Yes. Upsun runs PHP as a first-class native runtime and currently supports PHP 8.2, 8.3, 8.4, and 8.5. You select the version in a YAML configuration file stored with your code, configure PHP-FPM workers and extensions in the same place, and Upsun uses Composer 2.x by default for dependency management. No Dockerfile is required.

Which PHP frameworks and CMSes does Upsun support?

Upsun has documented guides for Laravel and Symfony, plus tutorials for the major PHP-based content management systems: WordPress, Drupal, Magento, Shopware, and Pimcore. Persistent storage mounts handle CMS media and user uploads without offloading to S3, and managed services include PostgreSQL, MariaDB, Redis, and OpenSearch for the typical PHP stack. Laravel Horizon, Symfony Messenger, and Drush cron all run in dedicated worker containers in the same project as the web app.

Which Heroku alternative supports WordPress, Drupal, or Magento natively?

Upsun supports WordPress, Drupal, Magento, Shopware, and Pimcore through documented templates and persistent storage mounts that survive deploys, which is the main blocker for CMS workloads on Heroku. Pantheon and Acquia are stronger specialist choices if you only run WordPress or Drupal and want a host built around that one CMS.

Can I migrate a Laravel app from Heroku without rewriting?

Yes, on most of the alternatives covered here. DigitalOcean App Platform reuses the Heroku PHP buildpack directly, so a Laravel app often migrates with no code changes. Upsun and Laravel Cloud both have first-class Laravel support and documented migration paths, though Upsun expects you to add a YAML configuration file describing your services. Render requires a Dockerfile.

Which Heroku alternative has native PHP support without Docker?Upsun, Laravel Cloud, and DigitalOcean App Platform all run PHP as a native, first-class runtime without requiring you to maintain a Dockerfile. Render and Fly.io expect Docker for PHP workloads. If avoiding container maintenance is a priority, the first three are the shorter list to evaluate.

Do any of these alternatives let me test against production data?Upsun is the only platform in this comparison that automatically clones production code, configuration, services, and production data into a preview environment on every Git branch. The others offer staging or PR preview environments, but they do not seed production data by default.