Vercel → Coolify
Self-hosted Vercel alternative: what if we switched to Coolify?
Short answer
Moving from Vercel to Coolify pays off in two cases. Either it bothers you that a US provider runs your application, or your monthly bill is above roughly $200. In both cases you need someone who can look after a Linux server.
It does not pay off if your bill is $20 to $60 and nobody on the team wants to own updates, backups and outages. Then Vercel sells you peace of mind, and that is a fair price.
Coolify is not a second Vercel. It is an open-source control panel that handles builds, deployments and certificates on your own server. The server, its security and its uptime are yours from then on.
We run mallorca-plus.de (Next.js 16) and this website on Coolify ourselves. The operating numbers below come from there. Prices and incidents come from the linked sources.
What changes
Next.js itself runs completely without Vercel. Image optimisation, Proxy (formerly Middleware), ISR and streaming also work on your own server, according to the official self-hosting guide. What you give up is the platform around the framework.
| On Vercel | On Coolify | What it means for you |
|---|---|---|
| Deployment on git push | Also on git push, by webhook or API | No difference day to day |
| Preview per pull request | Preview deployments through the GitHub App | Previews run on the same server as production |
| Automatic SSL | Automatic Let's Encrypt | No difference |
| Global CDN | One server in one location | Usually enough for visitors in Europe. Worldwide you need a CDN in front |
| Automatic scaling | Fixed server size | The server has to absorb traffic peaks |
| Edge Functions distributed worldwide | Run in the Node process on your server | The code works, the distribution is gone |
| Image optimisation on the edge network | Runs in the Node process on your server | Costs CPU and memory on your machine |
| ISR cache across all regions | Cache sits on the server's disk | Fine with one server. Several servers need a shared cache |
| Firewall and DDoS protection | Not included | Put your own in front or live without |
| Vercel Blob and Marketplace databases | PostgreSQL, Redis and S3-compatible storage as your own services | Move the data, adapt the client code |
| Web Analytics and Speed Insights | Not included | Run Plausible yourself, for example |
| Deployment without interruption | Rolling update if a health check is configured | No guarantee without a health check |
The middle column is based on the Coolify documentation on preview deployments and rolling updates and on our own setup.
What you need
You need a server, a person who knows Linux and Docker, and a plan for operations. The software is the smallest part.
| What | Minimum | What we recommend |
|---|---|---|
| Server | 2 CPU cores and 2 GB RAM according to the Coolify documentation | 4 cores and 8 GB as soon as a database joins, because the build runs on the same server |
| Location | Data centre in the EU | A provider headquartered in the EU, if data location is your motive |
| Skills | Linux, SSH, Docker basics | Someone who has restored a backup at least once |
| Time | Two to four hours a month, estimates a field report after eight months of running it | A fixed slot in the calendar for updates |
| Backups | Database dumps to storage outside the server | Daily, plus a test restore once a quarter |
| Monitoring | Uptime check from outside with an alert | Alerts for disk, memory and certificates as well |
| Firewall | Only the ports you need | A firewall at the provider, because Docker can bypass local rules |
Your application has to run as a container. Coolify detects Next.js through Nixpacks or Railpack, and a Dockerfile of your own works too. This website builds exactly that way: with its own Dockerfile and output: 'standalone'.
If you do not want to maintain the control panel yourself, Coolify Cloud starts at $5 a month. The Coolify team then runs the dashboard. The server stays your job.
What it costs
In money terms the move only pays off from about $200 of Vercel spend a month. Below that, the time you spend on operations eats the saving.
Running costs per month
| Item | Vercel Pro | Coolify on your own server |
|---|---|---|
| Base price | $20, including one developer seat and $20 of credit | €0, Coolify is open source |
| More developers | $20 per seat, viewers are free | No price per seat |
| Compute | Usage based, first from the credit, then on top | Fixed server price, for example €8.49 net for 4 vCPU and 8 GB at Hetzner |
| Traffic | 1 million requests and 1 TB included, next tier $20 for 10 million requests | 20 TB included in the Hetzner plan |
| Password protection | $20 per protected project | Basic auth through the proxy, no extra charge |
| Static IP address | $100 per project | Every server has one, €0.50 for IPv4 at Hetzner |
| Visitor statistics | Web Analytics included, Plus tier $10 | Run Plausible yourself, which uses server capacity |
| Operations | Included in the price | Two to four hours of your time |
The Vercel prices come from the documentation on the Pro plan and on Flat Rate CDN, as of September 2026. The Hetzner prices apply since the price adjustment of 15 June 2026.
Beyond the credit, Vercel bills by usage, with prices that differ by region. One CPU hour costs $0.128 to $0.221, and 1,000 image transformations cost $0.05 to $0.0812. By default Vercel only notifies new customers at $200 of spend per billing cycle. It pauses projects only if you configure that in Spend Management.
Three worked examples
| Situation | Vercel per month | Server per month | Difference before your time |
|---|---|---|---|
| One person, one project, little traffic | $20 | About $10 | About $10 |
| Three developers, two projects with password protection | $100 | $10 to $19 | $81 to $90 |
| As above, plus a static IP and the CDN tier for 10 million requests | $220 | $10 to $19 | $201 to $210 |
The figures use list prices without tax and a rate of 1 euro = 1.1253 dollars (16 October 2026). The server is a Hetzner CX33 or CX43 with IPv4. Usage beyond the credit is not part of the calculation.
Your operating time comes off that difference. Use your own hourly rate: at $90, two to four hours cost $180 to $360 a month.
In the second example you lose money. In the third, something is only left if two hours are enough.
Two things tilt the maths in your favour. Operating time is spent once per server, and at our end twelve applications share one server. And if you look after Linux servers anyway, part of the work is already in your calendar.
One-off costs
The move costs working time, not licences. How much depends on three questions:
- Do you use Vercel's own services such as Blob, Cron Jobs or Edge Config?
- Does a database move too?
- Do you need preview deployments?
How it runs at our end
We run twelve applications on a single server with Coolify, and the server is bored. The numbers are a snapshot from 14 November 2026.
| Figure | Value |
|---|---|
| Coolify version | 4.7.5, self-hosted |
| Server | One VPS at IONOS with 16 GB RAM and about 500 GB of storage |
| What runs on it | 12 applications, 3 services (Plausible and Metabase among them), 1 database |
| CPU | About 5 percent used on average |
| Memory | About 6 of 16 GB in use |
| Storage | About 17 percent in use |
| mallorca-plus.de | 274 deployments since 26 March 2026, mostly 2.5 to 3.5 minutes |
| wolf-tech.io | 137 deployments since 6 March 2026, mostly 2 to 3.5 minutes |
mallorca-plus.de runs Next.js 16 from its own Dockerfile. CI triggers every deployment through the Coolify API, and the database migrations then run as a post-deployment command. wolf-tech.io is a Docker Compose application and deploys by webhook.
One stumbling block from operations: during next build our application has no access to the database. Prerendered pages therefore showed old data after every deployment. Since the application revalidates when the server starts, the content is right again.
Two things we have not solved cleanly ourselves yet. Neither application has a health check configured in Coolify, and wolf-tech.io gets no rolling update because it is a Docker Compose application. A deployment can therefore cost us requests for a moment.
Risks
With the move you take on jobs that Vercel has quietly done for you. Know these ten points before you decide.
| Risk | What can happen | What helps |
|---|---|---|
| Security holes in Next.js | With React2Shell (CVE-2025-55182, December 2025, CVSS 10.0), Vercel, Netlify and Cloudflare protected their customers at platform level. Self-hosted instances stayed exposed until someone installed the update, according to Bitdefender. | Subscribe to security advisories, install updates the same day, rotate all credentials after an incident |
| Security holes in Coolify | Several critical vulnerabilities were published in 2026. With CVE-2026-34038 (July 2026, CVSS 9.9), a logged-in user with write access could run commands on the server. | Keep Coolify current, create few accounts, restrict access to the dashboard |
| One server, one point of failure | If the server goes down, every application on it is offline. | Backups outside the server, a rehearsed restore, a second server for critical applications |
| Builds on the production server | A Next.js build briefly needs a lot of memory and CPU. On a tight server that slows the running application. | Choose a server with headroom or connect a separate build server in Coolify |
| Deployments with an interruption | By its own documentation, Coolify does not guarantee uninterrupted deployments. Docker Compose applications get no rolling update at all. | Set up a health check, avoid fixed host ports and container names, test under load |
| Previews run other people's code | The code of a pull request runs on your deployment server, warns the Coolify documentation. | Previews only for repository members, separate credentials for previews, no production secrets |
| A rollback is not a backup | A rollback starts an older image. Data and database changes do not come back with it. | Back up the database separately, keep migrations backwards compatible |
| What is gone | Global CDN, automatic scaling, firewall and DDoS protection belong to Vercel and do not move with you. | Put a CDN or WAF in front, plan for traffic peaks, run statistics yourself |
| Being on call | If something fails at night, the alert lands with you. | Alerts to your phone, a named stand-in, or hand operations to a service provider |
| Server prices rise too | Hetzner raised its low-cost cloud plans by 31 to 38 percent on 15 June 2026. In autumn 2026 they were temporarily unavailable to order. | Budget with headroom, keep a second provider in view |
React2Shell showed how fast it gets serious. In April 2026 Cisco Talos found an automated campaign that used this hole. Within 24 hours it took over at least 766 Next.js hosts and stole credentials, reports SecurityWeek. If you host yourself, you have hours for such updates, not weeks.
None of these points alone argues against the move. But write a name next to each one: who takes care of it?
GDPR
The move solves exactly one data protection problem: your hosting no longer sits with a US company. It does not make your application GDPR compliant by itself.
Using Vercel is permissible as things stand, provided contract and privacy notice are in order. By its own account the company is certified under the EU-US Data Privacy Framework, and the European Commission's adequacy decision is in force. The EU General Court dismissed an action against it on 3 September 2025.
That does not have to last. An appeal, case C-703/25 P, has been pending before the Court of Justice since 31 October 2025. In October 2026 it was still undecided. The court struck down both predecessors of the framework, Safe Harbor and Privacy Shield.
On top of that, Vercel remains a US company. It is subject to US law such as the CLOUD Act, even if your functions run in Frankfurt.
| Question | Vercel | Coolify on an EU server |
|---|---|---|
| Who runs the infrastructure? | Vercel Inc. from the US | You, on hardware of an EU provider |
| Data transfer to a third country | Yes, based on the Data Privacy Framework | Not for hosting, if provider and location are in the EU |
| Data processing agreement | With Vercel | With the server provider |
| Open legal question | Appeal against the judgment on the Data Privacy Framework | None comparable |
| Technical safeguards | Largely handled by the platform | Yours: access, updates, backups, deletion |
The last row is easy to forget. Article 32 GDPR requires appropriate technical safeguards, and on your own server you put them in place yourself. Our view: a neglected server of your own is the bigger data protection risk than a well-kept US service.
The typical trap is US services that stay elsewhere in the project. Think of a US CDN in front of the server, fonts loaded from Google's servers, Google Analytics or a US email provider. Each of them brings the topic back, so check the whole chain before you advertise EU hosting.
This is not legal advice. Have your data protection officer or a law firm review the assessment for your company.
The steps
The move takes ten steps, and until the DNS switch in step 9 no visitor notices anything. The order follows the Coolify guide on coming from managed platforms.
- Take stock: which Vercel features do you really use? The prompt further down does that for you.
- Order the server and secure it: SSH with keys only, a firewall at the provider, automatic security updates.
- Install Coolify and restrict access to the dashboard.
- Prepare the application:
output: 'standalone', a Dockerfile and an endpoint for the health check. Replace system variables such asVERCEL_URL. - Replace Vercel's own services: Blob with S3-compatible storage, Cron Jobs with scheduled tasks in Coolify. Redirects from
vercel.jsonmove tonext.config. - Copy database and files, set up the backup and test a restore.
- Deploy in Coolify, transfer the environment variables and test on a temporary domain. DNS stays untouched.
- Set up monitoring and alerts before real visitors arrive.
- Transfer the latest data and switch DNS. Lower the record's TTL a day before.
- Keep the Vercel project running for at least two weeks. Cancel only after that.
The way back is short as long as the Vercel project runs: point DNS back. Mind the data when you do. From the switch on, the application writes to the new database, and whoever goes back has to take that state along.
The technical details are in two guides of ours: Deploying Next.js to Coolify and Coolify v4 self-hosted on Hetzner.
Switch or stay
Whether the move pays off comes down to one question: who looks after the server? Without an answer, staying is the right result.
Switch if
- a customer, a contract or your data protection officer demands an EU provider
- your Vercel bill is above roughly $200, or add-ons such as static IP and password protection drive it
- someone on the team looks after Linux servers, or a service provider takes over operations
- you have several projects that can share one server
- most of your visitors are in Europe
Stay if
- your bill is $20 to $60
- nobody wants to own updates, backups and alerts
- your visitors are spread across the world, or traffic peaks arrive unpredictably
- you need previews for pull requests from outsiders
- you promise an availability that a single server cannot deliver
The middle way
You do not have to move everything at once. Leave the public application on Vercel and move internal tools, staging or side projects to your own server first. That way you learn operations without your revenue depending on it.
Prompt to copy
With this prompt you check for yourself whether the move pays off for your project. It works in two phases: first the inventory, then the target picture. Paste it into the AI assistant of your choice and replace the placeholders in square brackets.
You are an experienced cloud architect with a focus on Next.js hosting. I am considering moving an application from Vercel to my own server in the EU with Coolify. Help me assess this soberly. "Stay on Vercel" is an allowed result.
Rules
- Ask if information is missing. Do not guess numbers.
- Mark every assumption as an assumption.
- I will not give you passwords, API keys, tokens or customer data. If I do so by mistake, point it out and do not use them.
- Prices change. For every price, say how recent your knowledge is and what I have to verify myself.
My information
1. Vercel invoices or usage overview of the last three months: [insert]
2. Plan, number of paid team seats, booked add-ons: [insert]
3. package.json (dependencies), next.config and vercel.json: [insert]
4. Results of the code search for runtime = 'edge', revalidate, next/image, @vercel/ and VERCEL_: [insert]
5. Names of the environment variables, without values: [insert]
6. Databases and storage the application uses and where they are hosted: [insert]
7. Visitors per month, typical traffic peaks, where visitors come from: [insert]
8. Who on the team knows Linux and Docker and how many hours a month are realistic: [insert]
9. How long the application may be down in the worst case: [insert]
10. Requirements on data protection and contracts, for example a customer who demands an EU provider: [insert]
Phase 1: current state
Create a table of all Vercel features I use. Columns: feature, what I use it for, equivalent with Coolify, effort for the move (low, medium, high), risk. Then name the three biggest cost drivers on my bill and the three biggest risks of the move. List all open questions. Stop here and wait for my answers.
Phase 2: target concept
Only after my answers:
1. Target architecture with Coolify: server size, services, backups, monitoring, a CDN if needed.
2. Running costs per month compared with today and one-off costs for the move, each with assumptions. Include my working time for operations.
3. What I lose and whether that matters for my project.
4. Migration plan in steps with a test on a temporary domain, the DNS switch and the way back.
5. Verdict: switch, switch partly or stay. Justify it in no more than five sentences.
Wrap-up
Summarise everything on one page so that I can send it to a service provider for a fixed-price quote.
How to collect the data
| Information | Where to find it |
|---|---|
| Invoices and usage | In the Vercel dashboard under Usage and with the invoices in the team settings |
| Configuration | package.json, next.config and vercel.json from the repository |
| Code search | The command below this table, run in the project folder |
| Environment variables | Names only, from .env.example or from the project settings on Vercel |
| Visitors and traffic peaks | From your web analytics or the usage overview |
grep -rnE "runtime = .edge.|revalidate|next/image|@vercel/|VERCEL_" \
--include="*.ts" --include="*.tsx" --include="*.js" --include="*.jsx" --include="*.mjs" \
--exclude-dir=node_modules --exclude-dir=.next .
Two notes before you paste anything. Do not paste values of environment variables, tokens or customer data, and black out address and payment details on invoices. Also check every price in the result against the pricing pages, because an AI assistant does not know current prices reliably.
Second opinion
If you want the result cross-checked: send the summary from the last step to hello@wolf-tech.io. We read it and tell you whether we reach the same verdict.
Frequently asked questions
Is Vercel GDPR compliant?
As things stand, Vercel can be used in a compliant way. By its own account Vercel is certified under the EU-US Data Privacy Framework, and the European Commission's adequacy decision is in force. The appeal in case C-703/25 P before the Court of Justice is still open.
What does Coolify cost?
The self-hosted version is free and open source. You only pay for the server, for example €8.49 net a month for 4 vCPU and 8 GB at Hetzner. Coolify Cloud starts at $5 a month, and you bring your own server there as well.
Does Next.js run completely without Vercel?
Yes. According to the Next.js documentation, image optimisation, Proxy, ISR and streaming work with next start on your own server. Only with several instances do you need a shared cache, for example Redis.
Can Coolify do preview deployments?
Yes, through the GitHub App or a webhook, with a separate domain per pull request. The code from the pull request runs on your deployment server. So allow previews only for members of the repository.
Who installs security updates?
You do. Vercel protects its customers at platform level against holes like React2Shell, and on your own server that protection does not exist. Plan a fixed slot for updates and an alert path for urgent advisories.
How long does the move take?
That depends on how much Vercel is in your project. An application without Vercel Blob, Cron Jobs and Edge Config mainly needs a Dockerfile and a test run. Every Vercel service you have to replace comes on top.
Is there a European alternative to Vercel?
There are two routes. You run Coolify yourself on a server from a European provider such as Hetzner or IONOS, which is cheap and means work. Or you take a managed platform from a European provider, which costs more and takes operations off your hands.
This page covers the first route.
Sources and date
All figures were checked on 14 November 2026. Vercel prices are list prices in dollars without tax, server prices are net prices in euros. Conversions use 1 euro = 1.1253 dollars, the rate of 16 October 2026.
| Topic | Source | As of |
|---|---|---|
| Vercel Pro: base price, seats, add-ons | Vercel documentation on the Pro plan | Updated 15 September 2026 |
| Vercel: Flat Rate CDN tiers | Vercel documentation on Flat Rate CDN | Updated 14 September 2026 |
| Vercel: usage prices | Regional pricing | Retrieved 14 November 2026 |
| Vercel: Data Privacy Framework | Vercel changelog | Vercel's own statement |
| Next.js on your own server | Self-hosting guide | Retrieved 14 November 2026 |
| Coolify: requirements, prices, deployments | Installation, Usage, Rolling updates, Preview deployments, Rollbacks, Coming from managed platforms | Retrieved 14 November 2026 |
| React2Shell | Bitdefender | December 2025 |
| Campaign against Next.js hosts | SecurityWeek | April 2026 |
| Coolify vulnerability CVE-2026-34038 | NVD | Published 6 July 2026 |
| Hetzner: prices | Price adjustment | In effect since 15 June 2026 |
| Hetzner: availability | Bitdoze | Checked 20 October 2026 |
| Appeal on the Data Privacy Framework | EUR-Lex, case C-703/25 P | Lodged 31 October 2025 |
| Operating effort | Field report at nextgrowth.ai | Retrieved 14 November 2026 |
| Our own operating numbers | Wolf-Tech's Coolify instance | Read on 14 November 2026 |
Prices and the legal situation change. Verify any figure your decision depends on before you move.
