Compare
dply vs Laravel Cloud
Laravel Cloud is a managed platform built for Laravel. dply runs Laravel the same way, as containers with managed databases, Valkey and queue workers, and it also runs Rails and Node apps and static or server-rendered frontends in the same project, on one bill.
How the pieces map
| Laravel Cloud | dply |
|---|---|
| App cluster | A container app, detected from the repo |
| Build and deploy commands | A generated image, or your own Dockerfile |
| Migrations in the deploy command | Migrations when a container starts, or on demand |
| Queue clusters | Queue workers that autoscale on queue depth |
| Scheduler toggle | The Laravel scheduler, every minute |
| Cloud databases | Managed Postgres, MySQL or MongoDB |
| Key-value store | dply Valkey |
| Reverb / WebSockets | Realtime |
| Compute size and hibernation | Instance size, sleep after idle, minimum instances |
What to plan for on dply
- No SSH
- Containers have no shell. Use the logs and the database tools (Migrate, Seed, Connect).
- No persistent disk
- Files written at runtime are lost on restart. Put uploads in object storage.
- Cold starts
- An idle app sleeps after 5 minutes by default. Set a minimum instance to keep one warm.
When Laravel Cloud is the better fit
- Every app you run is Laravel and you want the platform made by the framework’s own team.