dply
Your whole app, not just the frontend.
Connect a repository. dply detects Laravel, Rails, Django, Spring, .NET, Go, Rust, Phoenix, Deno, Bun or Node, builds it, runs it next to its database and queue workers, and gives every branch its own URL.
Apps & workers
Laravel, Symfony, Rails and Node run as they are, in containers.
Detected from the repo
dply reads the framework, runtime and build from your code and generates the image. Bring a Dockerfile when you want one.
Scales out, sleeps when idle
Instances follow traffic and sleep after a quiet spell. You pay for the seconds they run; keep one warm if you need to.
Queue workers & scheduler
queue:work processes that autoscale on queue depth, worker groups, failed jobs, and the Laravel scheduler every minute.
Migrations on deploy
Run migrations when a container starts, or on demand from the database sheet.
Databases & data
Attach what the app needs; the credentials arrive as environment variables.
Postgres, MySQL & MongoDB
Managed, in your app’s region, backed up continuously, and asleep when nothing is connected.
Valkey
A Redis-compatible store for cache, sessions and queues.
Object storage & realtime
Buckets for uploads, and WebSockets for Laravel broadcasting.
Bring your data
Upload a pg_dump or mysqldump and load it, or connect with the URL and restore it yourself.
Deploys & previews
Push a branch. Get a URL.
A preview per branch
Every branch and pull request builds to its own URL, posted back as a commit check and a PR comment.
Instant rollback
Releases are immutable and keep their own URL, so going back is a pointer change, not a rebuild.
Static, SSG & SSR too
Next.js, Nuxt, Astro, SvelteKit, Remix, Hugo and more, served from the edge under the same project.
Environment per app
Separate production and preview values, encrypted at rest, applied at build and runtime.
Domains & protection
What happens on the request path, before your app sees it.
Custom domains & TLS
Guided DNS, with certificates issued and renewed for you. Every app gets a permanent hostname on day one.
Redirects, rewrites & middleware
Declarative rules and your own code on the request path, evaluated at the edge.
Firewall & access rules
Block by country, IP or path, challenge bots, rate-limit, or put staging behind a login.
Traffic, logs & uptime
Requests, status codes and response times, a live tail of what the app prints, and URL checks with alerts.
Teams, API & security
- Orgs, invitations, roles, and an audit trail
- Metered usage visible before the invoice
- Spend guardrails that stop runaway builds
- GitHub, GitLab & Bitbucket over OAuth
- HTTP API behind every action, plus a CLI
- Org-scoped tokens with granular abilities
- Two-factor auth and passkeys
- Secrets encrypted at rest, never shown again
What it isn't
- A server to SSH into
- Containers start fresh and have no shell. Use the logs and the database tools instead.
- A persistent disk
- Files written at runtime are lost on restart. Put uploads in object storage.
- Zero cold starts by default
- An idle app sleeps and the next request waits for it to wake. Set a minimum instance to keep one warm.