dply
Ship a site, not a server.
Connect a repository. dply builds it, puts it on a global edge network, and gives every branch its own URL.
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.
Review on the real thing
Reviewers comment directly on a preview and mark it approved or changes-requested.
Instant rollback
Releases are immutable and keep their own URL, so going back is a pointer change, not a rebuild.
Private by default
Preview URLs need a signed link or an org login, so unreleased work is never indexable.
Builds & frameworks
Settings are inferred, and all of them are yours to override.
Framework detection
Next.js, Nuxt, Astro, SvelteKit, Remix, Gatsby, Vite, Hono, Eleventy, Hugo, Jekyll, and plain HTML.
Static, SSG & SSR
Static output is served from object storage; server-rendered routes run at the edge, under one hostname.
Cached builds
Dependencies are cached between deploys, so an unchanged lockfile skips the cold install.
Environment per site
Separate production and preview values, encrypted at rest, applied at build and runtime.
Domains & delivery
What happens on the request path, before your app sees it.
Custom domains & TLS
Guided DNS, with certificates issued and renewed for you. Every site gets a permanent hostname on day one.
Redirects, rewrites & headers
Declarative rules evaluated at the edge — no origin round trip to send a 301.
Edge middleware
Your own code on the request path for rewrites, geo routing, and A/B splits.
Cache & purge
Assets are cached at the edge, invalidated on deploy, and purgeable by path.
Protection & insight
Who reaches the site, and what happened when they did.
Access rules
Put a site or a path prefix behind a password or an org login — useful for staging and internal tools.
Firewall, bots & rate limits
Block by country, IP, ASN, or path; challenge automated traffic; cap requests per window.
Traffic & logs
Requests, bandwidth, status codes, cache ratio, and response times, plus a searchable live tail.
Uptime & alerts
Scheduled URL checks, with failed builds and error spikes routed to the channels you already watch.
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
- Managed databases
- Bring your own — reach it over HTTPS from a Worker or your build.
- Long-running services
- Edge runs your frontend and its request-path logic, not a persistent process.
- Form handling
- Submissions are captured per site; routing and spam filtering are still in progress.