Try a Laravel web app on free compute, with a public URL and managed TLS. Use the free tier to evaluate your app before choosing paid services for production.
Each instance has a fixed monthly price, prorated by the second.
Capability | Render | |||
|---|---|---|---|---|
How Laravel runs | Docker web services and queue workers | Long-running container services | PHP buildpack or containers on dynos | Fly Machines built from a Dockerfile |
Free tier | 750 free hours/month. Spins down after 15 min idle | $5 trial for 30 days, then $1/month credit | None. Eco: $5/month for 1,000 hours | No free tier. Personal bills under $5 waived |
Always-on, 2 GB | $25/month (1 CPU) | Up to $40/month at full use (1 vCPU) | $250/month (Performance-M, 2.5 GB dedicated) | $13.39/month shared CPU, $33 dedicated |
Managed Postgres and Redis | Postgres from $6 with PITR, plus Key Value | Maintained databases. HA and Postgres PITR opt-in | Postgres and Key-Value. No rollback on Essential | Managed Postgres from $38, HA included. Upstash Redis |
Queue workers and scheduler | Workers and cron jobs | Workers and cron jobs | Worker dynos and Scheduler | Process groups. Cron via Supercronic |
Migrations before deploy | Pre-deploy command on paid instances | Pre-deploy command | Release phase | release_command in fly.toml |
WebSockets | Yes, no maximum duration | Yes, no maximum duration | Yes, closes after 55s idle | Yes, through Fly Proxy |
Competitor details as of November 2026. Instance prices are compute only. Fly.io prices are for US East.
Run Laravel in Docker with workers, a scheduler, and Postgres. Define the stack in one render.yaml Blueprint.
Choose the PHP version and extensions in your Dockerfile. Render builds the image and runs your web service.
Connect to Render Postgres over the private network in the same workspace and region. Configure Laravel with the internal connection details.
Run queue consumers in background workers. Choose persistent queue storage and make jobs safe to retry.
Run Laravel scheduled tasks in a separately billed cron job. Use an appropriate schedule and command for your application.
Check application readiness before traffic moves to a new web instance. Plan compatible migrations and graceful worker restarts.
Use external object storage for uploads or attach a paid disk. Disk-backed services run one instance and have a few seconds of deploy downtime.
Create a Web Service from your repository and select Docker. Include the Dockerfile and server configuration your app needs.


Set APP_KEY and database credentials as environment variables. Configure HTTPS URLs and use a production web server.
Deploy the service, run the required migrations, and test a real request. Connect a queue worker only if your app needs one.