# dply

> dply deploys Laravel, Symfony, Rails and Node apps, and static or server-rendered sites, from a Git push. Apps run as containers on a global edge network that scale out and sleep when idle. Managed Postgres, MySQL, MongoDB, Valkey, object storage, realtime and autoscaling queue workers run beside them, on one bill.

- Plans (monthly only): Starter $0/mo (1 seat); Pro $29/mo (3 seats); Team $49/mo (10 seats, +$5 per extra seat). Usage bills on top of the plan fee, and sites are unlimited.
- Usage bills by the second an app, worker or database is awake; requests and bandwidth by the unit.
- Starter is $0 a month plus usage, card required, with a spending cap you can raise; Pro and Team add limits and included build minutes.
- Pricing: https://edge.dply.io/pricing
- Features: https://edge.dply.io/features
- Compared with Laravel Forge: https://edge.dply.io/vs/forge, Laravel Cloud: https://edge.dply.io/vs/laravel-cloud, Heroku: https://edge.dply.io/vs/heroku
- Security and subprocessors: https://edge.dply.io/compliance
- Contact: hello@dply.io

Every documentation page below is also available as Markdown.

## Getting started

- [Introduction](https://edge.dply.io/docs/introduction.md): dply deploys websites and web apps from your Git repository to Cloudflare's edge network, with builds, domains, resources and observability managed for you.
- [Quickstart](https://edge.dply.io/docs/quickstart.md): Create an account, choose a plan, connect a repository and deploy your first app to the edge.
- [Frameworks & runtimes](https://edge.dply.io/docs/frameworks.md): The frameworks and language runtimes dply detects, the versions it builds with, and how to override what it detects.
- [How dply works](https://edge.dply.io/docs/how-dply-works.md): What happens between a Git push and a live URL, how requests reach your app, where your data lives, and how customers are kept apart.
- [Local development](https://edge.dply.io/docs/local-development.md): Run your app on your machine, keep its configuration in step with dply, and use the dply CLI to deploy, preview and inspect it from your terminal.
- [Private beta](https://edge.dply.io/docs/private-beta.md): What the dply private beta includes, what it costs, its current limits, and how to reach us.

## Apps & deployments

- [Apps](https://edge.dply.io/docs/apps.md): Create an app from a Git repository, understand what dply sets up for it, and delete it when you no longer need it.
- [Source control](https://edge.dply.io/docs/source-control.md): Connect GitHub, GitLab, or Bitbucket to dply, what each provider supports, and how dply uses your credentials.
- [Builds](https://edge.dply.io/docs/builds.md): How dply clones, installs, and builds your repository, and the settings, limits, and caches that apply to every build.
- [Configuration files](https://edge.dply.io/docs/configuration-files.md): The files dply reads from your repository on each build: dply.yaml, wrangler.toml, Procfile, dply-contract.yaml, and edge middleware.
- [Deployments](https://edge.dply.io/docs/deployments.md): How a deploy goes live, how to follow it, and how to redeploy, deploy a specific commit, roll back, and apply settings changes.
- [Deploy triggers & hooks](https://edge.dply.io/docs/deploy-triggers.md): Start deploys automatically on Git push, from a CMS or CI pipeline with a deploy hook URL, or from the CLI and HTTP API.
- [Preview deployments](https://edge.dply.io/docs/preview-deployments.md): Get a live URL for every pull request or any commit, review it with your team, and promote it to production.
- [Environment variables](https://edge.dply.io/docs/environment-variables.md): Set environment variables for your app, understand when they reach the build and the runtime, and see the variables dply adds for you.
- [Secrets](https://edge.dply.io/docs/secrets.md): Store a secret once in your organization's vault, link it onto apps, and rotate it in one place.
- [Monorepos](https://edge.dply.io/docs/monorepos.md): Deploy one package from a monorepo by setting a repository root, and control which pushes redeploy it.

## Runtime & compute

- [Static & hybrid sites](https://edge.dply.io/docs/static-and-hybrid.md): How dply serves prebuilt files from the edge, caches hashed assets, keeps old tabs working across deploys, and proxies dynamic routes to your own origin.
- [Server rendering (SSR)](https://edge.dply.io/docs/server-rendering.md): Render Next.js, Astro, SvelteKit and Remix pages per request on the edge network with Worker SSR.
- [Edge middleware](https://edge.dply.io/docs/edge-middleware.md): Run your own code on the edge before a static or hybrid app serves a request: rewrite, redirect, authenticate, or answer directly.
- [Container apps](https://edge.dply.io/docs/containers.md): Run Laravel, Symfony, Rails and Node servers as containers behind your app's hostname, billed per second while they run.
- [Scaling & sleep](https://edge.dply.io/docs/scaling-and-sleep.md): How container apps add instances under load, sleep when idle, stay warm on a schedule, and what keeps them awake.
- [Queue workers](https://edge.dply.io/docs/queue-workers.md): Run always-on or autoscaling php artisan queue:work processes next to a Laravel container app, with worker groups, failed jobs and logs.
- [Scheduled tasks](https://edge.dply.io/docs/scheduled-tasks.md): Run code on a cron schedule: a scheduled() handler for static, hybrid and Worker SSR apps, and the Laravel scheduler or a command (artisan, rake or your own Node route) for container apps.
- [Data regions](https://edge.dply.io/docs/data-regions.md): Where dply stores your files, databases and caches, where container apps run, and which settings pin them.

## Resources

- [Resources overview](https://edge.dply.io/docs/resources.md): Attach storage, databases, queues, and platform services to an app from the resource map on its Overview page.
- [Key-value (KV)](https://edge.dply.io/docs/resources/key-value.md): A globally replicated key-value store for caches, sessions, and settings, billed per read, write, and GB stored.
- [Object storage](https://edge.dply.io/docs/resources/object-storage.md): Private file buckets on Cloudflare R2 for uploads and generated files, reached through your app's private host or a Worker binding.
- [Edge SQL (D1)](https://edge.dply.io/docs/resources/sql.md): Serverless SQLite databases on Cloudflare D1, with a query console, table browser, and per-row billing.
- [Postgres, MySQL & MongoDB](https://edge.dply.io/docs/resources/databases.md): Run a managed Postgres, MySQL, or MongoDB database for your app that sleeps when idle, backs itself up continuously, and connects over TLS.
- [Valkey (Redis)](https://edge.dply.io/docs/resources/valkey.md): Add a private, Redis-compatible Valkey store to your app for cache, sessions, and queues, billed per second while it is awake.
- [External Redis](https://edge.dply.io/docs/resources/external-redis.md): Connect your app to a Redis you already run by pasting its address.
- [Queues](https://edge.dply.io/docs/resources/queues.md): Cloudflare Queues for background jobs: send from any app, run the jobs in one app, and pay per operation.
- [State (Durable Objects)](https://edge.dply.io/docs/resources/state.md): Small, strongly consistent values for counters, locks, and flags, stored in one Durable Object per app.
- [Realtime (WebSockets)](https://edge.dply.io/docs/resources/realtime.md): Add Reverb- and Pusher-compatible WebSockets to your app for broadcasting, private and presence channels, without running a socket server.
- [Messages](https://edge.dply.io/docs/resources/messages.md): Send HTTP requests later, with retries, callbacks and cron schedules: a message queue your app publishes to over HTTPS.
- [Database pools](https://edge.dply.io/docs/resources/database-pools.md): Keep warm connections to a Postgres or MySQL database close to your app so each request skips the connection setup.
- [Vector search](https://edge.dply.io/docs/resources/vector-search.md): Store embeddings in a vector index and find the closest matches: semantic search, recommendations and retrieval for AI answers. Billed by use, sleeps like any resource.
- [Workers AI](https://edge.dply.io/docs/resources/ai.md): Run text-generation and embedding models from your app without managing model servers or API keys.
- [Browser rendering](https://edge.dply.io/docs/resources/browser-rendering.md): Give your app a headless browser to fetch rendered pages, take screenshots, and make PDFs.
- [Images](https://edge.dply.io/docs/resources/images.md): Resize and convert images from your app's code with the Images resource, or serve resized images from signed URLs with Delivery image optimization.
- [Workflows](https://edge.dply.io/docs/resources/workflows.md): Workflows are not available on dply yet; this page explains why and how to remove an existing Workflow resource.

## Networking

- [Domains](https://edge.dply.io/docs/domains.md): Use your app's default dply hostname, attach your own custom domains, and get HTTPS certificates issued automatically.
- [Domain verification](https://edge.dply.io/docs/domain-verification.md): The DNS records dply asks for when you attach a custom domain, how verification works, and how to fix a domain that won't verify.
- [Routing, redirects & headers](https://edge.dply.io/docs/routing.md): Add redirects, rewrites and response headers to your app, from the dashboard or from dply.yaml, without rebuilding.
- [Caching](https://edge.dply.io/docs/caching.md): How dply caches static files and app responses at the edge, how to configure cache modes and TTLs, and how to purge.
- [Edge network](https://edge.dply.io/docs/edge-network.md): How requests reach your dply app through Cloudflare's global network, where content is stored and cached, and what HTTPS and DDoS protection you get.

## Security

- [Firewall](https://edge.dply.io/docs/firewall.md): Allow or block visitors by country at the edge, before they reach your pages, forms or app.
- [Rate limits](https://edge.dply.io/docs/rate-limits.md): Cap how many requests a single visitor IP can make to a path, and block or challenge anyone who goes over.
- [Bot protection](https://edge.dply.io/docs/bot-protection.md): Add a Cloudflare Turnstile challenge to your forms, verify tokens at the edge, and use it as the challenge for rate limits.
- [Access control](https://edge.dply.io/docs/access-control.md): Put your app and its previews behind a password or dply sign-in, and control who can see them.
- [Waiting room](https://edge.dply.io/docs/waiting-room.md): Queue visitors at the edge during launches and traffic spikes, so your app only admits as many people as it can handle.
- [Platform security & isolation](https://edge.dply.io/docs/platform-security.md): How dply keeps each organization's apps, builds, data and secrets separate, and how it protects outbound requests and credentials.

## Site features

- [Forms](https://edge.dply.io/docs/forms.md): Accept form POSTs on a path of your app at the edge, with honeypot and Turnstile spam checks, and no backend of your own.
- [Error pages](https://edge.dply.io/docs/error-pages.md): Brand your app's 404 and 500 pages and take it offline with maintenance mode, all served at the edge without a rebuild.
- [Snippets & tags](https://edge.dply.io/docs/snippets.md): Inject HTML snippets and third-party scripts such as analytics into your app's pages at the edge, with optional consent gating.
- [Status pages & uptime](https://edge.dply.io/docs/status-pages.md): Publish a public status page for your apps, post incidents and updates, and list components with their current state.

## Observability

- [Traffic & analytics](https://edge.dply.io/docs/traffic.md): See requests, bandwidth, cache performance, response times, Core Web Vitals, and live requests for an app.
- [Logs](https://edge.dply.io/docs/logs.md): Read build and deploy output, request logs, container logs, and queue worker logs for an app.
- [Alerts](https://edge.dply.io/docs/alerts.md): Send an app's deploy, domain, usage, and error events to your notification channels, and alert on slow pages and 5xx errors.
- [Notification channels](https://edge.dply.io/docs/notifications.md): Create the destinations dply sends alerts to, such as Slack, email, PagerDuty, or a webhook, and choose who owns them.
- [Deploy badge](https://edge.dply.io/docs/deploy-badge.md): Add a Deploy to dply button to a README so visitors can create an app from your repository with the form already filled in.

## Organizations & access

- [Organizations](https://edge.dply.io/docs/organizations.md): Create organizations, switch between them, and manage their settings, members, and deletion.
- [Teams](https://edge.dply.io/docs/teams.md): Group organization members into teams and give each team its own notification channels.
- [Roles & permissions](https://edge.dply.io/docs/roles-and-permissions.md): What owners, admins, members, deployers, and viewers can do in an organization, and how seats are counted.
- [App members](https://edge.dply.io/docs/app-members.md): Give an organization member a Viewer, Deployer, or Admin role on a single app.
- [Account security](https://edge.dply.io/docs/account-security.md): Protect your dply account with a password, passkeys, OAuth sign-in, and two-factor authentication.
- [Activity log](https://edge.dply.io/docs/activity-log.md): See who changed what in your organization and its apps, search the history, and export it for audits.

## Billing

- [Plans & pricing](https://edge.dply.io/docs/pricing.md): What each plan includes and the rate for every usage meter.
- [Starter and spending caps](https://edge.dply.io/docs/free-trial.md): dply has no trial: Starter is $0 a month plus usage, with a card on file and a monthly spending cap you can raise.
- [Usage & metering](https://edge.dply.io/docs/usage.md): How dply measures each usage meter, how often it is collected, where you can see it, and how it reaches your invoice.
- [Spending caps & alerts](https://edge.dply.io/docs/spending-alerts.md): Starter's spending cap, the optional spending cap on Pro and Team, usage alert emails, and what happens when you reach each kind of limit.
- [Invoices & taxes](https://edge.dply.io/docs/invoices.md): What each dply invoice contains, when usage is charged, how plan and seat changes are prorated, what cancelling bills, and how taxes are handled.
- [Paused accounts](https://edge.dply.io/docs/paused-accounts.md): Why an organization is paused, what stops while it is paused, how long its data is kept, and how to resume.

## Tools

- [CLI](https://edge.dply.io/docs/cli.md): Install the dply command-line tool, sign in from the browser, and deploy, roll back, and inspect your apps from a terminal or CI.
- [HTTP API](https://edge.dply.io/docs/api.md): Call dply from CI, scripts and integrations with organization-scoped API tokens.
- [API reference](https://edge.dply.io/docs/api/reference.md): Every dply HTTP API v1 endpoint, with the ability it needs, its parameters and an example response.
- [MCP server](https://edge.dply.io/docs/mcp.md): Connect Claude, Cursor, and other MCP clients to dply so an AI assistant can read, diagnose, deploy and roll back the apps in your organization.

## Guides

- [Deploy a Laravel app](https://edge.dply.io/docs/guides/laravel.md): Take a Laravel app from a Git repository to a running container on dply, with a database, cache, queues, scheduler and migrations.
- [Deploy a Next.js app](https://edge.dply.io/docs/guides/nextjs.md): Deploy a Next.js app to dply as a static export, a hybrid site in front of your own server, or Worker SSR through OpenNext.
- [Deploy an Astro site](https://edge.dply.io/docs/guides/astro.md): Deploy an Astro site to dply as a static build served from the edge, or with server rendering on Workers through the Cloudflare adapter.
- [Deploy a Rails app](https://edge.dply.io/docs/guides/rails.md): Take a Rails app from a Git repository to a running Puma container on dply, with a database, cache, jobs and migrations.
- [Laravel broadcasting with Realtime](https://edge.dply.io/docs/guides/laravel-broadcasting.md): Broadcast Laravel events to browsers with Echo and the stock Reverb driver, using dply's managed Realtime relay instead of running Reverb yourself.
- [Migrate from Vercel or Netlify](https://edge.dply.io/docs/guides/migrate-from-vercel-netlify.md): Move a site from Vercel, Netlify or Cloudflare Pages to dply with the import wizard, then move redirects, environment variables and custom domains without downtime.
- [Migrate from Forge or Laravel Cloud](https://edge.dply.io/docs/guides/migrate-from-forge-cloud.md): Move a Laravel app from a Forge server or Laravel Cloud to dply: map each piece, move the database, and switch the domain.
- [Migrate from Heroku](https://edge.dply.io/docs/guides/migrate-from-heroku.md): Move a Heroku app to dply: keep your Procfile, copy config vars, replace add-ons with dply resources, move the database, and switch the domain.
- [Migrate from Render](https://edge.dply.io/docs/guides/migrate-from-render.md): Move a Render service to dply: import render.yaml, copy environment variables, replace Render databases and Key Value with dply resources, and switch the domain.
- [Migrate from Railway](https://edge.dply.io/docs/guides/migrate-from-railway.md): Move a Railway service to dply: import railway.json or railway.toml, copy variables, replace Railway databases with dply resources, and switch the domain.
- [Migrate from Fly.io](https://edge.dply.io/docs/guides/migrate-from-fly.md): Move a Fly.io app to dply: build the same Dockerfile, set the port, copy secrets, replace Fly databases with dply resources, and switch the domain.
- [Troubleshooting builds](https://edge.dply.io/docs/guides/troubleshooting-builds.md): Find why a dply build or deploy failed, with the exact messages the build log shows and how to fix each one.
- [Troubleshooting errors & 5xx](https://edge.dply.io/docs/guides/troubleshooting-runtime.md): Diagnose 5xx responses, paused pages, slow first requests and broken assets on a deployed dply app, from what the visitor sees to the fix.

## Support

- [Support](https://edge.dply.io/docs/support.md): How to get help with dply, what to include in a request, and where to look first.
- [Compliance & security](https://edge.dply.io/docs/compliance.md): Where dply runs your apps and data, how it protects them, which subprocessors it uses, and what it doesn't offer yet.
- [Report abuse](https://edge.dply.io/docs/abuse.md): How to report a site hosted on dply for phishing, malware, spam, copyright infringement or other abuse, and what happens next.
- [Changelog](https://edge.dply.io/docs/changelog.md): Notable changes to dply, newest first.