Cloudways Velocity vs Vercel: Which Should Host Your Next.js App?

Should your Next.js app live on Vercel or on Cloudways Velocity? And does a flat $20 server really cost less than Vercel Pro once traffic is steady?

The 2 platforms run your code in different ways, and the bill follows from that. Vercel runs it as functions that start per request and charges by developer seat and usage. Velocity runs it as a Node.js process on a server that stays on, at a fixed monthly price.

For me, Cloudways Velocity vs Vercel comes down to how many apps you run and whether any of them must stay on. I’d keep 1 Next.js app with uneven traffic on Vercel. I’d move to Velocity for 3 or more Node apps, or for a backend with queues, long jobs or sockets that stay open.

I’ve hosted WordPress on Cloudways, and Velocity itself is a new product, so I’ve compared the 2 on their current plans and documentation. Here’s the whole difference in one table:

Factor	Cloudways Velocity	Vercel
How your code runs	An always-on Node.js process on a server	Functions that run per request
Pricing	Flat, $20 to $400 a month per server	Free Hobby plan, then Pro at $20 a seat plus usage
Apps	5 on the $20 plan, up to 150 on the largest	Each project is billed by its usage
Scaling	Manual resize, no autoscaling	Automatic
Preview deployments	No	For every push, on every plan
WebSockets	Stay open while the process runs	Close at the function time limit, 300 to 800 seconds
Cron jobs	Per app, as Node commands	Every minute on Pro, inside the function time limit
Database	PostgreSQL on the same server	Marketplace partners such as Neon and Supabase
CDN and firewall	Cloudflare Enterprise and a firewall included	Vercel’s own CDN, with a firewall on all plans
Rollback	Redeploy an older commit	Instant Rollback
Regions	1 DigitalOcean data center per server, including Bangalore	19 compute regions, including Mumbai
Shell access	None	None
Free option	3-day trial	Hobby plan, for non-commercial use

How Each One Runs Your App

This is the difference everything else follows from, so I want to ensure it is clear before the prices.

On Vercel, your app becomes functions. A function instance starts when requests arrive, can handle several at once and pauses when they finish. Vercel adds instances by itself as traffic grows, and you never see a server.

On Velocity, your app is a normal Node.js process. A process manager called PM2 keeps it running, NGINX passes requests to it and Cloudflare sits in front. The process uses the CPU and memory of the server you picked, and up to 5 apps share a Starter server.

3 practical consequences follow:

• Time limits. A Vercel function stops after 300 seconds on Hobby and 800 seconds on Pro. A Velocity process has no such limit.
• Request size. Vercel caps a request or response body at 4.5 MB. Velocity has no documented cap of that kind.
• Capacity. Vercel grows with traffic and bills you for it. Velocity stays the size you bought, and a spike slows the app until you resize.

Cloudways Velocity vs Vercel Pricing

Velocity’s price is easy to state, because each plan is one server at one price:

• Starter: $20 a month for 2 vCPU, 2 GB of RAM and up to 5 apps
• Professional: $30 a month for 4 GB of RAM and up to 8 apps
• Growth: $50 a month for 8 GB of RAM and up to 14 apps

On top of the plan, only extra CDN bandwidth, offsite backup storage and extra disk are metered. My Cloudways Velocity review has the full plan table.

Vercel’s price has more parts:

• Hobby: free, for personal and non-commercial projects, with 1 developer seat.
• Pro: a $20 monthly platform fee, which includes 1 developer seat and $20 of usage credit.
• Extra developers: $20 a month each. People who only view and comment are free.
• CDN: Pro includes 1 million CDN requests and 1 TB of data transfer a month. The next tier is $20 a month for 10 million requests.
• Functions: $0.60 per million invocations, $0.128 per CPU hour and about $0.011 per GB-hour of memory, charged against the credit first.
• Builds: from $0.0035 per CPU minute, with no build minutes included.

Here’s a worked example with made-up usage for 1 Next.js app in a month:

• 3 million CDN requests
• 2 million function invocations
• 40 CPU hours and 300 GB-hours of memory
• 300 CPU minutes of builds

Cost line	Vercel Pro	Velocity Starter
Base plan	$20, with 1 seat and $20 of credit	$20
CDN, 3 million requests	$20 for the 10 million tier	Included
Functions and builds	$10.55, covered by the credit	Included
Monthly total, 1 developer	$40	$20
Monthly total, 3 developers	$80	$20

So Velocity is cheaper in this example, and the gap grows with every developer and every extra app. A second and third app on the same Velocity server cost nothing more until the server runs out of memory.

Vercel wins in 2 cases. A personal project stays free on Hobby. And a small business site under 1 million requests a month costs the same $20 on Pro, with previews and automatic scaling included.

The risk on Vercel is a busy month. Usage above the credit is billed on demand, and a spend limit doesn’t pause your project unless you turn that option on. In 2024, the social app Cara faced a bill of about $96,000 for one week of function usage after a growth spike. On Velocity, the same spike would have slowed or stopped the app, and the bill would have stayed at the plan price.

Next.js Features

Next.js is built by Vercel, and it also runs in full on a plain Node.js server. The Next.js self-hosting docs say a Node.js deployment supports all Next.js features, and that image optimization and incremental static regeneration work with no extra setup on a single server.

Velocity detects a Next.js project and sets the build and start commands for you. This is what you keep and what you give up when the app leaves Vercel:

Feature	On Velocity	On Vercel
Server rendering and API routes	Run inside your Node process	Run as functions
Incremental static regeneration	Cached on the server’s local disk	Stored by Vercel and billed per read and write
Image optimization	Runs on your server’s CPU	Runs on Vercel and is billed per transformation
Preview URL for each pull request	Not available	Included, with comments
Rollback	Rebuilds an older commit	Switches back instantly
Version skew between old and new deploys	Not handled for you	Skew Protection on Pro

Cloudways doesn’t document whether the regeneration cache survives a redeploy, so I’d plan for it to be rebuilt after each deploy. Image optimization also uses the same CPU as your app, which matters on the 2 vCPU plan.

Backends, WebSockets and Long Jobs

This is where Velocity is the better fit. Vercel can run an Express app, but it runs it as a single function, with the function limits attached.

• Express on Vercel: the app pauses between requests, serves static files from a public folder and follows the 800-second and 4.5 MB limits.
• WebSockets on Vercel: they are generally available on all plans. A connection closes when the function reaches its time limit, and a reconnect can land on a different instance, so state has to live in an external store.
• Cron on Vercel: once a day on Hobby and every minute on Pro, and each run is a function with the same time limit.
• On Velocity: the process stays up, so a socket stays open, a queue worker keeps polling and a scheduled job runs as a normal Node command.

For a chat server, a job queue, a bot or an n8n instance, I’d pick Velocity without much thought. For request-and-response APIs with short handlers, both work.

Scaling and Reliability

Vercel is the stronger platform when traffic is unpredictable. It scales by itself, can run functions in up to 3 regions on Pro and puts its CDN in front of everything. Its 99.99% uptime SLA is for Enterprise customers, and Pro comes with email support.

Velocity doesn’t autoscale. You resize the plan by hand, each server lives in 1 region and there is a weekly maintenance window when a short interruption is possible. Support is available 24/7 for the server and the platform.

This is the tradeoff. On Velocity, you choose a fixed bill and accept a fixed capacity. If a launch or a viral post can multiply your traffic in an hour, Vercel is the safer home.

Deploys and Team Workflow

Vercel’s workflow is the reason many teams pay for it. Every push gets a preview URL, teammates and clients can comment on it for free, and a bad release goes back with Instant Rollback.

Velocity’s workflow is simpler. It can auto-deploy every push to one branch, it keeps a deployment history with build logs and it redeploys an older commit when you need to go back. It has no preview deployments, builds run on the same server as your live apps and Cloudways’ docs warn that a deploy can affect availability.

If your team reviews work on preview links every day, I’d count that as a real cost of leaving Vercel.

Moving a Next.js App From Vercel to Velocity

The move is short for an app that already runs with a standard build and start command. This is the order Cloudways’ own guide follows:

1. You push the code to a GitHub repository you own.
2. You create a Velocity app on the Starter plan and connect that repository. Velocity detects Next.js and sets the build and start commands.
3. You add PostgreSQL from the dashboard if the app needs a database. It runs on the same server, so the host in the connection string is 127.0.0.1.
4. You copy your environment variables across and redeploy.
5. You point your domain at the app, and it gets an SSL certificate.

The guide stops there, so this is the list of Vercel-specific pieces I’d check before switching DNS:

• Cron jobs defined in the Vercel config, which become cron jobs in the Velocity dashboard
• Files in Vercel Blob, which need another object store
• A database from the Vercel Marketplace, which can stay where it is or move to the local PostgreSQL
• Vercel Web Analytics and Speed Insights, which need a replacement

Which One Should You Pick?

I’d choose Vercel if you:

• run 1 or 2 Next.js projects with traffic that rises and falls
• review every change on a preview URL
• want scaling handled for you and can live with a bill that moves
• have a personal project that fits the free Hobby plan

I’d choose Cloudways Velocity if you:

• run 3 or more Node apps and want them on one fixed bill
• need a process that stays on for sockets, queues, bots or long jobs
• have several developers and don’t want to pay per seat
• already host WordPress on Cloudways and want the front-end in the same account

You can also use both. A Next.js front-end on Vercel with its API and workers on Velocity gives you previews on one side and always-on processes on the other. For more options, my list of the best Node.js hosting platforms covers Render, Railway, Fly.io and others.

FAQs on Cloudways Velocity vs Vercel

Final Remarks

If you’re still unsure, I’d look at last month’s Vercel invoice first. If it is the base $20 and your team uses previews, I’d stay. If seats, the CDN tier and usage have pushed it past $60 and the traffic is steady, a Velocity server will cost less.

Before moving, I’d run the app on Velocity’s 3-day trial with a copy of the production environment and watch memory during a build. That shows whether the $20 plan is enough or whether you need the next one.

Disclaimer: This site is reader-supported. If you buy through some links, I may earn a small commission at no extra cost to you. I only recommend tools I trust and would use myself. Your support helps keep gauravtiwari.org free and focused on real-world advice. Thanks. - Gaurav Tiwari