Laravel on Render
Render publishes its own guide for deploying Laravel.
PHP web framework with an ORM, queue workers and a scheduler that expects a persistent process.
What Laravel needs.
Every host claims to run Laravel, so the claim on its own decides nothing. These are the things Laravel actually requires from the platform underneath it, and what Render publishes about each. Render documents 4 of the 4.
Persistent processes
Supported
Queue workers and Horizon are long-running processes, not requests. They have to stay up between jobs.
Sources (1) →Sources ↓
- Background Workers – Render Docs ↗
“Background workers are services that run continuously (like a web service or a private service), but they don't receive any incoming network traffic.”
Read 2026-09-05 · official docs
Managed databases
Supported
Eloquent, migrations and the default session and cache drivers all expect a relational database.
Sources (1) →Sources ↓
- Render Postgres ↗
“Deploy fully managed, enterprise-grade databases that scale to any workload.”
Read 2026-09-05 · official docs
Scheduled jobs
Supported
Laravel's scheduler is one cron entry calling schedule:run every minute. Without cron, nothing scheduled ever fires.
Sources (1) →Sources ↓
- Cron Jobs – Render Docs ↗
“You can create cron jobs on Render that run periodically on a schedule you define.”
Read 2026-09-05 · official docs
Persistent storage
Supported
The default filesystem disk writes uploads under storage/app. On an ephemeral filesystem those files disappear at the next deploy.
Sources (1) →Sources ↓
- Persistent Disks – Render Docs ↗
“You can attach a persistent disk to a paid Render web service, private service, or background worker. This enables you to preserve local filesystem changes across deploys and restarts.”
Read 2026-09-05 · official docs
What Render documents.
Render publishes its own guide for deploying Laravel.
In this guide, we're going to deploy a simple Laravel 11 web app using Render's native PostgreSQL and Docker support.
Sources (1) →Sources ↓
- Deploy a PHP Web App with Laravel and Docker – Render Docs ↗
“In this guide, we're going to deploy a simple Laravel 11 web app using Render's native PostgreSQL and Docker support.”
Read 2026-09-05 · official docs
Laravel features on Render
Capabilities Render documents specifically for Laravel, with the constraint it documents alongside each.
laravel_scheduler
Supported
You can create cron jobs on Render that run periodically on a schedule you define. [...] The schedule to use for the cron job, defined as a cron expression.
storage_disk_mount
Supported
You can attach a persistent disk to a paid Render web service, private service, or background worker. This enables you to preserve local filesystem changes across deploys and restarts. [...] If your framework writes to a relative path (e.g., Rails Active Storage uses ./storage for file uploads), mount your disk at the absolute version of that path or an ancestor of it.
managed_mysql
Not supported
For storage of relational data, create a Render Postgres database. [...] You can also use a persistent disk to run a custom database instance instead of Render Postgres, such as MySQL.
native_php_runtime
Not supported
Render natively supports Node.js / Bun, Python, Ruby, Go, Rust, and Elixir. [...] To run virtually any language (PHP, .NET, Java/Kotlin/Scala, etc.), you can deploy a Docker image.
Sources (4) →Sources ↓
- Cron Jobs – Render Docs ↗
“You can create cron jobs on Render that run periodically on a schedule you define. [...] The schedule to use for the cron job, defined as a cron expression.”
Read 2026-09-13 · official docs
- Persistent Disks – Render Docs ↗
“You can attach a persistent disk to a paid Render web service, private service, or background worker. This enables you to preserve local filesystem changes across deploys and restarts. [...] If your framework writes to a relative path (e.g., Rails Active Storage uses ./storage for file uploads), mount your disk at the absolute version of that path or an ancestor of it.”
Read 2026-09-13 · official docs
- Render FAQ – Render Docs ↗
“For storage of relational data, create a Render Postgres database. [...] You can also use a persistent disk to run a custom database instance instead of Render Postgres, such as MySQL.”
Read 2026-09-13 · official docs
- Supported Languages – Render Docs ↗
“Render natively supports Node.js / Bun, Python, Ruby, Go, Rust, and Elixir. [...] To run virtually any language (PHP, .NET, Java/Kotlin/Scala, etc.), you can deploy a Docker image.”
Read 2026-09-13 · official docs
What it costs to run there.
- Pricing model
- The Hobby plan does not have a monthly fee, so you only pay for usage.
- When you exceed a cap
- Pipeline minutes: overage is auto-purchased, but with no payment method or once the monthly spend limit is reached Render stops running pipeline tasks, builds included.
- Regions
- Oregon, USA; Ohio, USA; Virginia, USA; Frankfurt, Germany; Singapore
Sources (3) →Sources ↓
- Platform Features by Plan – Render Docs ↗
“The Hobby plan does not have a monthly fee, so you only pay for usage.”
Read 2026-09-05 · official docs
- Build pipeline — Render Docs ↗
“Running out of minutes If you run out of pipeline minutes during a given month, you automatically purchase a supplementary amount of minutes for your current tier, unless: You've reached your monthly spend limit, or You haven't added a payment method.”
Read 2026-09-14 · official docs
- Regions — Render Docs ↗
“You can deploy Render services to any of the following regions to minimize latency for your users: Oregon, USA Ohio, USA Virginia, USA Frankfurt, Germany Singapore”
Read 2026-09-14 · official docs
Whether it suits you.
Workloads that need real background workers and persistent processes alongside web services, deployed from a repository or a Dockerfile. Managed Postgres and static sites run on the same platform.
Consider something else if…
Free web services spin down after 15 minutes without traffic, which makes the free tier unsuitable for anything that must answer immediately.
Visit Render documentation