9 min read
Preview Deployments: Vercel, Cloudflare, Coolify, Dokploy
Key takeaways
- Vercel and Cloudflare create a preview URL automatically on every push to a non-production branch, with HTTPS and teardown handled for you.
- Self-hosted Coolify and Dokploy give you preview URLs on your own VPS but leave database wiring, env var duplication, and cleanup to you.
- No platform in this comparison provides a preview database that mirrors production out of the box; seed staging data yourself.
- Preview deployments consume build minutes and bandwidth on hosted platforms, so a burst of open pull requests can quietly raise your bill.
- Omeganodes offers git push to deploy with MTN and Airtel mobile money billing but does not yet offer automatic per-PR preview environments.
Preview deployments spin up a live copy of your app for every branch or pull request, so you test changes on a real URL before merging to production. This guide compares how Vercel, Cloudflare, Coolify, and Dokploy handle branch triggers, environment variables, databases, and teardown side by side, then runs Omeganodes through the same criteria, including where it falls short.
What is a preview deployment?
A preview deployment is a live copy of your app built from a branch or pull request, sitting at its own temporary URL. You push code, get a link, and share it with a teammate or a client before anything touches production.
The git-push-to-review workflow
Most platforms watch your GitHub repo and build a new preview on every PR. Vercel does this by default and documents the flow in its preview deployments guide, including how each PR gets a unique URL. The catch for solo developers is cost: preview builds count against your plan's limits, and a burst of activity can run up a bill.
The payoff is simple: you review real running code, not screenshots, without managing servers or YAML. Tools like Omeganodes (https://omeganodes.com) apply the same push-to-deploy idea, though preview-specific behaviour varies by platform.
How do preview deployments work on Vercel?
On Vercel, every push to any branch that is not your production branch gets its own preview deployment. Vercel builds the branch, assigns it a URL like my-app-git-feature-username.vercel.app, and issues automatic HTTPS for it. No YAML, no pipeline config: connect the GitHub repo and push-to-deploy starts working on every branch.
Branch triggers and automatic HTTPS
The trigger is the push itself. Open a pull request and Vercel comments on it with the preview link, then updates that same preview URL as you push more commits. Custom domains stay attached to production; previews run on the generated subdomains with certificates handled for you.
Environment variables per preview
You can scope variables to "Preview" separately from "Production" in the dashboard, so a preview can point at a staging database or test API keys. Sensitive values can be encrypted and hidden from the repo.
Where Vercel previews get expensive
Each preview is a full deployment that consumes build minutes and, once it receives traffic, bandwidth and function invocations on your account. A solo developer juggling several side projects can watch preview usage stack up quietly, and the surprise is the bill, not the limit. That is the pattern worth watching: previews are free until they are not, and there is no mobile money option to fall back on if you lack a USD-billing card. Omeganodes takes a different billing path entirely (https://omeganodes.com/it), though its preview story is covered later in this guide.
How do Cloudflare preview deployments work?
Cloudflare handles previews differently for Pages and Workers. On Pages, every push to a non-production branch gets its own preview URL in the form <hash>.<project>.pages.dev, so you can share a link to a branch before merging. Workers use preview URLs too, and you can control whether previews share your production routes or run on a separate workers.dev subdomain. Cloudflare documents these options in its Pages and Workers developer docs, including how to restrict preview access.
Preview URLs for Pages and Workers
Pages previews are automatic: open a pull request and the branch deploys without extra configuration. Workers previews depend on your wrangler setup, since the preview environment is defined in your config rather than triggered by a branch name alone. That means git push to deploy is fully automatic on Pages but more manual on Workers.
Database and binding handling in previews
Bindings (KV namespaces, D1 databases, R2 buckets) are shared with production by default unless you create separate preview bindings. There is no automatic per-branch database, so preview data can collide with production data if you are not careful. The same trade-off shows up on Omeganodes, where preview environments are not yet a built-in feature and staging typically means a second deployment with its own environment variables.
How do Coolify preview deployments work?
Coolify is self-hosted: you install it on your own VPS, connect it to your GitHub or GitLab repo, and it builds and runs your app there. The trade-off is real. You get push-to-deploy without Kubernetes or YAML, but you also inherit the operator's job that Heroku used to do for you.
Pull request previews on your VPS
When you open a pull request, Coolify can spin up a separate preview environment from that branch. It builds the branch on your server, exposes it on a subdomain or port, and injects environment variables you define per environment. Databases are the catch: Coolify does not give every pull request its own fresh database. You point previews at a shared dev database or wire up a separate one yourself, so test data can leak between branches if you are careless.
You own the teardown problem
Previews run on resources you pay for. If a pull request sits open for weeks, its container keeps eating RAM and disk on your VPS until you close the PR or clean it up manually. Coolify supports automatic cleanup on PR close, but the default is your responsibility to configure. That is the honest cost of the free, self-hosted route: the deploy is easy, the hygiene is yours. If you would rather not think about any of it, a managed PaaS like Omeganodes handles the pipeline for you, at the price of trusting someone else's servers.
How do Dokploy preview deployments work?
Dokploy generates a preview deployment for every pull request you open on a connected GitHub repository. It builds the branch in an isolated environment, gives it its own URL, and tears the environment down when you merge or close the PR, so each PR gets a live link your teammates and testers can click without touching staging.
Preview templates and compose-based apps
For compose-based projects, Dokploy uses preview templates: you define which services from your compose file should spin up per PR, and which environment variables get injected into the preview build. That keeps a database-heavy stack from launching a full copy of everything on every push. The mechanics are close to what Coolify documents for pull request builds, where each PR maps to its own domain and cleanup happens automatically (Coolify docs).
The honest gap: Dokploy is self-hosted, so you provision the server, watch disk usage during preview storms, and handle backups yourself. If that tradeoff doesn't suit you, a managed option like Omeganodes removes the server work, though it doesn't offer per-PR preview environments today.
Preview deployments compared: branch triggers, env vars, databases, teardown
The four platforms agree on the trigger: push a branch, get a URL. They diverge on everything a git push to deploy workflow depends on afterwards.
| Vercel | Cloudflare | Coolify | Dokploy | |
|---|---|---|---|---|
| Branch triggers | Every branch by default | Per-project settings | Manual or per-app config | Per-app config |
| Env vars | Inherited, overridable per preview | Per-branch bindings | You duplicate them yourself | You duplicate them yourself |
| Preview databases | Managed, tied to the platform | D1/Neon via bindings | Bring your own | Bring your own |
| Teardown | Automatic on merge/close | Automatic | Manual or scripted | Manual or scripted |
The pattern worth noticing: hosted platforms automate env var inheritance and teardown because they own the whole stack. Self-hosted Coolify and Dokploy give you preview URLs but leave database cleanup and variable plumbing to you, which is fine for a side project and a chore for a team.
None of the four gives you a preview database that mirrors production without extra setup. If your preview needs real data, plan to seed it yourself or point previews at a shared staging database and accept the risk.
What about preview deployments on Omeganodes?
What it does today
Omeganodes gives you push-to-deploy from GitHub to EU servers with automatic HTTPS, so every push to your main branch goes live without Kubernetes or YAML. Payment is the part built for you: MTN Mobile Money and Airtel Money work alongside cards, and pricing is regional rather than USD-only. That covers the deploy path, but not per-branch previews.
What it does not do yet
There is no automatic preview environment per pull request today. If you want branch-based previews right now, Dokploy's documentation covers preview deployments and application templates you can self-host, and Render offers preview environments on its own terms. The honest trade-off: Omeganodes keeps infrastructure out of your head and accepts the payment method you actually have, but you deploy branches manually or merge to test. Per-branch teardown and preview databases are on the roadmap, not in the product.
Which preview deployment setup should a solo developer choose?
Pick by payment first, maintenance second. If you can pay in USD by card and want zero config, Vercel or Cloudflare fit, but watch the bill: per-seat pricing and surprise overages are the common complaint. If you own a server and enjoy tinkering, Coolify or Dokploy give you preview deployments for the cost of the VPS, plus the freedom to run any database.
If you are in Kenya or Uganda without a card that bills in USD, the deciding factor is not features but checkout. Omeganodes takes MTN and Airtel mobile money, prices regionally, and keeps the Heroku-style flow: git push to deploy, automatic HTTPS, no Kubernetes, no YAML. The honest trade-off: preview deployments are simpler here than on Coolify, and you give up the deep per-branch env var tooling Vercel offers. Match the tool to your bill, not the feature list.
FAQ
Do preview deployments cost extra on Vercel or Cloudflare?
On Vercel, every preview is a full deployment that consumes build minutes, bandwidth, and function invocations against your plan, so a busy stretch of branches can quietly raise your bill. Cloudflare Pages previews are included, but traffic and resource usage still count toward plan limits. Previews are effectively free until usage pushes you into overage territory.
Can I pay for preview deployment hosting with MTN or Airtel mobile money?
Vercel, Cloudflare, Coolify, and Dokploy all bill in USD by card, with no mobile money option. Omeganodes is the exception: it accepts MTN Mobile Money and Airtel Money alongside cards, and prices regionally rather than in USD only. If checkout is your bottleneck, that difference matters more than the feature list.
How do I stop preview environments from piling up and eating my bill?
Close pull requests promptly, since merge or close triggers automatic teardown on Vercel, Cloudflare, and Dokploy. On Coolify, configure cleanup on PR close yourself, because the default leaves stale containers eating RAM and disk on your VPS. Also limit which services spin up per PR, as Dokploy's preview templates do for compose-based stacks.
Can a preview deployment connect to a real production database safely?
Not without risk. None of the four platforms gives you a preview database that mirrors production out of the box. Cloudflare shares bindings like D1 with production unless you create separate preview bindings, and Coolify or Dokploy expect you to wire up your own. Point previews at a shared staging database and seed test data yourself.
Do I need Kubernetes or YAML to get preview deployments on a self-hosted PaaS?
No. Coolify and Dokploy both run on a plain VPS, build branches on every pull request, and expose each preview on its own subdomain or domain without Kubernetes. You do inherit operator work: watching disk usage during preview storms, handling backups, and duplicating environment variables per environment. The deploy is easy, the hygiene is yours.
Deploy at the speed of Africa
World-class hosting, open to every developer, wherever you build and however you pay. Start free in a couple of minutes — no credit card, no lock-in.