Test a containerized PHP web app on a free web service. Get a public URL, connect a custom domain, and use managed TLS without a workspace subscription.
Each instance has a fixed monthly price, prorated by the second.
Capability | Render | |||
|---|---|---|---|---|
How PHP runs | Docker web service | Long-running container | Web dyno | Fly Machine 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 |
Background workers | Workers and cron jobs | Workers and cron jobs | Worker dynos and Scheduler | Process groups. Cron via Supercronic |
Stack as code | One render.yaml, auto-synced on push | Project file, applied with CLI or CI | app.json per app, read only at creation | fly.toml per app. No database definitions |
Autoscaling | Scales on CPU or memory, Pro plan and up | Manual replicas. Vertical up to plan limits | Performance, Private and Shield dynos only | Proxy autostart, or a self-run autoscaler |
Competitor details as of November 2026. Instance prices are compute only. Fly.io prices are for US East.
Run PHP in Docker with the extensions and web server you choose. Define your services and databases in one render.yaml Blueprint.
Choose the PHP version and extensions in your Dockerfile. Your team maintains the image and dependencies while Render runs the service infrastructure.
Package the HTTP server your application needs alongside PHP. Keep local and hosted runtime configuration consistent.
Use managed Render Postgres when your app supports it. Connect to a self-hosted or external MySQL database when your application requires MySQL.
Run queue consumers as background workers and schedule tasks with cron jobs. Each service is configured and billed separately.
Put uploaded files in external object storage or under a paid disk mount. Disk-backed services have a few seconds of deploy downtime and cannot scale horizontally.
Configure an HTTP health check for your app. Stateless web services support zero-downtime deploys, with migrations and graceful shutdown handled by your application.
Pick a GitHub, GitLab, or Bitbucket repo and branch.


Select Docker, set the Dockerfile path, and add environment variables. Configure your HTTP server to listen on 0.0.0.0 and the service port.
Render builds your app and publishes its URL. Every later commit to your branch deploys automatically, or only after CI checks pass.

