Skip to content
unnudged
brandRising

Vercel on X

Vercel is a default host people recommend: the largest group praises how fast a project goes live from a repo, plus its free tier. Cost is the counterweight — overage bills and usage limits push people toward Cloudflare — and newer agent tooling draws enthusiasm and security questions.

First written 27 Oct · what changed · from 199 posts by 189 people

Tracking posts that say “vercel”

Track this for your market
Posts, last 24h
100
+122%vs. previous 24h
Posts, last 7 days
529
285 in the last 72h
Velocity
76/day
7-day average
Momentum
+32%
Last 24h vs. a normal day this week

Posts per day, last 30 days

as of Nov 3, 12:00 UTC
2001000Oct 20: 0 postsOct 20Oct 21: 59 postsOct 22: 59 postsOct 23: 39 postsOct 24: 76 postsOct 25: 37 postsOct 26: 47 postsOct 26Oct 27: 109 postsOct 28: 63 postsOct 29: 0 postsOct 30: 72 postsOct 31: 99 postsNov 1: 73 postsNov 2: 13 postsNov 2

What changed

as of 27 Oct · checked once a month

First written 27 Oct. When what people say changes, it shows here.

Tone· 109 posts from 104 people· written 27 Oct

How do people feel about Vercel?

Most of the talk is positive: 63 people recommend Vercel as their default host, citing how fast a project goes from repo to live site and its generous free tier. The pull in the other direction is money — 16 people say they have left or are leaving over cost, and 9 more are weighing it.

Satisfied users describe Vercel as the place a project ends up by default: push to GitHub, get a URL. They point to weekend builds shipped with Claude Code or v0, prototypes that become "real next.js/typescript repos on vercel now. no way back", and the convenience of one dashboard for domains, deploys and experiments. Some defend it against the charge that it is not real hosting.

16 people are sold on the newer AI and agent tooling — durable-harness resuming a crashed run from the log, Sandbox and its egress controls, Connect handing agents restricted Stripe keys, AI Gateway, v0 — the same number as the people who are fed up, so the two are level.

The dissatisfied are nearly all cost-driven, and Cloudflare is where they say they go. Migration is described as doable in a day by some and as a headache by others; a few describe savings in euros per month.

In the undecided group, the questions are arithmetic: a project that cost "$15 for 9 days", Hobby limits approaching, whether to pay Vercel or rent a Hetzner box.

  • Satisfied, recommends it65
  • Sold on the AI and agent tools19
  • Fed up and moving off16
  • Undecided, weighing options9
See 5 of 109 posts

> a customer reports a bug > the agent opens a branch > writes the fix > spins up the preview > merges it under 30 minutes, per Vercel. it takes me longer to name the branch

RIP to the Mac mini under every engineer's desk durable-harness makes Pi, OpenCode, Codex and Claude Code durable on @vercel. Crash, timeout or redeploy, and the next function picks the turn back up from the log. You can close the lid now 🖤 h/t @pranaygp @fazxes link

triptojapan left @vercel - today - vinext on @CloudflareDev FTW ~$1,470/mo → ~$200-300/mo vercel was getting insane: build minutes ($1.3k since July), bandwidth ($1.1k), CDN requests ($0.9k) taking advantage of the new worker cache header feature for CDN hosting on static and semi-static pages

5 of the 109 posts behind this answer, one per person. The other 104, and every new one as it’s posted, come with tracking. Get early access

Pain points· 55 posts from 53 people· written 27 Oct

What do people complain about with Vercel?

Costs are the single biggest complaint: 22 people describe surprise bills, overage emails and free-tier limits that pause a site without warning. Security worries are the next most common at 8 people, then deploys that break (6) and outages (5).

The bill complaints are about the shape of the charge as much as its size: line items for build minutes, bandwidth and CDN requests, overage emails, an auto-pause warning that arrives at "100% of the free CPU", and card limits left open by mistake. One user says every email from Vercel is "either an overage or price increase"; another reports a $1,100 bill they did not see coming. Some say cancellation keeps billing.

Security is worried about more than it is described as attacked. People report a coding agent removing deployment protection because it misread a prompt, dangling CNAMEs pointing at Vercel being claimable by strangers, and a trust policy scoped only to the team letting preview deploys assume production. Vercel's push against static credentials is noted alongside the contradiction that deploying from GitHub Actions still needs a fixed token.

Deploy failures are specific: environment keys not working, an edge function timing out at 30 seconds while the dashboard shows 10, stale chunks, a missing font module.

Smaller groups call Vercel "rented land", hit runtime limits, or find resuming agents re-firing an email or payment.

  • Costs and surprise bills22
  • Security worries9
  • Deploys and builds that break6
  • Outages and sites going down5
  • Lock-in and rented land5
  • Slow Node patches and runtime limits3
See 5 of 55 posts

3 dias de orelha no ar kkkk Só no primeiro dia foram mais de 1 milhão de requisições e no pico foram mais de 13 mil acessos em uma hora, parece pouco, mas ainda assim é uma loucura! Agora um aprendizado, nunca deixar o cartão sem limite definido na Vercel 🤬

Congrats on the run. One shutdown step people skip: remove DNS records that point at hosts you're turning off, and keep the domain for a while. Dangling CNAMEs to Vercel or Heroku get claimed by strangers, and old users still trust that address.

5 of the 55 posts behind this answer, one per person. The other 50, and every new one as it’s posted, come with tracking. Get early access

Alternatives· 43 posts· written 27 Oct

What are the alternatives to Vercel?

Cloudflare is the alternative people name: 21 people weigh it against Vercel or say they moved there, almost always over price. Self-hosting on a VPS, with Coolify (5 people) or Hetzner (4) named, is the next most-raised route.

Cloudflare is the one comparison that cuts both ways. People leave for it citing bills — one describes consolidating off Vercel and Railway "in a day", another calls it "the cheapest", and someone else says a Cloudflare bill would come in "less then $70". A few frame it as the successor: "Cloudflare is the new Vercel". But people also name what Vercel does better: "you'll be deployed live on Vercel in the time it takes you to understand what you need for Cloudflare", a faster deploy on push, and one user switched to Vercel because Cloudflare could not be used where they were.

The self-hosting camp is about owning the stack: a cheap VPS configured and managed by an agent, two Hetzner boxes running everything for about €14 a month, Coolify as the open-source, self-hostable replacement. Some of it comes down to how technical someone is willing to become, and one person came back the other way, saying they cannot keep up with 0-days without a security team.

Railway, Render, GitHub Pages, Framer, Lovable and Infomaniak come up once or twice each.

  • Cloudflare21
  • Coolify5
  • Hetzner4
  • Own server or VPS4
  • Railway2
  • Render1
See 5 of 43 posts

Whichever you can afford at this point. The Cloudflare startup program and their recent acquisitions & releases make it hard to beat. But you’ll be deployed live on Vercel in the time it takes you to understand what you need for Cloudflare, and that’s with or without AI.

My hosting bill is €14 a month. Here's the whole setup. I moved all my side projects off Vercel and onto two @Hetzner_Online servers. The bill is about €14.38 a month. 1. A 4-core x86 box in Helsinki runs production: SaaS, its Postgres and the deploy control plane. 2. A 2-core arm64 box in Falkenstein runs the small sites @openshipio on the first box deploys to both. When I push to GitHub, a runner on the box builds and ships it. I don't touch a dashboard. Only ports 80 and 443 are public, and on the small box only @Cloudflare can reach them. SSH, dashboards and databases sit behind Tailscale. AI agents run most of it. One repo documents every server, port, cron job and change. The agent reads it, makes the change and writes down what it did. Hosting has been cheap for years. The real cost was always ops. Agents just made that cheap too.

So Vercel cost me $15 for 9 days. Time to switch? But where? 1) Cloudflare 2) Own VPS (Hetzner or netcup) 3) Anything else? It's nextjs project, database on neon.

Coolify: open-source, self-hostable alternative to Heroku, Netlify and Vercel. Needs only SSH access to a server; deploys from GitHub, GitLab, Bitbucket or Gitea. Apache-2.0. I read the docs, have not tested it. Worth a look if lock-in bothers you. link

5 of the 43 posts behind this answer, one per person. The other 38, and every new one as it’s posted, come with tracking. Get early access

Questions· 22 posts· written 27 Oct

What do people ask about Vercel?

The most common question is simply how it behaves — 8 people ask how Vercel routes and runs a site, how a feature or setup works, or why it was chosen. Stack fit and safety are next and level at 3 and 3 people each.

The mechanics questions are practical rather than skeptical: whether a domain has to be bought through Vercel, whether a Next.js backend can run an agent framework "without hosting a separate application", whether a Gateway login is required, and how the host actually serves a page — "what do you think vercel does when you hit a website that they host?" One asks how an issue got caught, whether Vercel recommends it or something else did.

Stack-fit questions list real combinations: Nx monorepos in TypeScript, Python, Electron and Next.js, and whether Turborepo is the only option; Resend, Stripe and GitHub wired in together.

Safety questions want a specific answer, not reassurance: whether revoking OIDC token issuance stops an old deployment from fetching new API keys, and whether a dedicated user gets read-only repo access and no production secrets.

Smaller pairs ask how to keep the bill down, what people are actually building, which host to pick among Vercel, Netlify, Cloudflare and AWS, and how the Sandbox separates traffic and cores.

  • How does it work?8
  • Will it work with my stack?3
  • Is it still safe?3
  • How do I avoid a big bill?2
  • What do people use it for?2
  • Which host should I pick?2
See 5 of 22 posts

why would I be saying that? you’re imagining that a platform can’t: give you a VM instantly + provide your data on it? that’s a failure of the current state of affairs sure, some folks might want to pay more to have stuff stick around in RAM longer, but I do not (by any means) think that’s the norm what do you think vercel does when you hit a website that they host? route you to a box that’s always running the website?

@NxDevTools @vercel_dev Can I expect first-class support for my NX monorepos if I choose Vercel as my deployment platform? Primarily developing in TypeScript, Python with Node, Electron and Nextjs targets. Or must I use @turborepo only?

Let me ask another way: if I patch the RCE and rotate my API keys the old deployment could not be used anymore to get the new API keys. Does this work for OIDC, too? Like revoke that vercel issues an OIDC token for deployments before date yyyy-mm-dd.

5 of the 22 posts behind this answer, one per person. The other 17, and every new one as it’s posted, come with tracking. Get early access

Wishes· 9 posts from 8 people· written 27 Oct

What do people want from Vercel?

The asks are about credentials and patches: 3 people want short-lived OIDC tokens to be the norm so agents stop pasting long-lived API keys into .env files, and 2 want the patched Node runtime rolled out sooner.

The token request is framed around agents: "Every agent setup I see starts with pasting a long-lived API key into a .env file, and those files get copied everywhere." People say static keys with full access and no expiry are what they worry about when wiring a new vendor in, and that short-lived OIDC tokens should be "table stakes".

The runtime request accepts the WAF rule as partial: "it only covers inbound traffic. It's not a replacement for the patched runtime." People are watching for the patched Node version to land and say there has been no update yet.

Single asks sit behind those: a Pro+ plan that gives "more bang for buck", a dashboard or email warning when a project uses OIDC but deployment protection is off, and a wish for a free, open-source Vercel to exist.

  • Short-lived tokens should be standard3
  • Ship patched Node sooner3
  • A cheaper tier with more included1
  • Warn when deployment protection is off1
  • A free, open-source version1
See 5 of 9 posts

Coding agents make this more urgent. Every agent setup I see starts with pasting a long-lived API key into a .env file, and those files get copied everywhere. Short-lived OIDC tokens are the only version of this that scales when agents are the ones logging in.

Static API keys are what I worry about most when we wire a new vendor into our stack. Too many still hand you one key with full access and no expiry, and you only learn what breaks when you rotate it. Short-lived OIDC tokens should be table stakes.

5 of the 9 posts behind this answer, one per person. The other 4, and every new one as it’s posted, come with tracking. Get early access

In their words

How do people talk about Vercel?

The phrases people use most, counted once per person.

  1. 1“api keys”3
  2. 2“cheaper than vercel”2
  3. 3“pay vercel”2
  4. 4“vercel bill”2
  5. 5“cheap vps”2
  6. 6“short-lived oidc tokens”2
  7. 7“tool call”2
  8. 8“close the lid”2

Posts are shown the way X shows them. One of them yours? Here’s why it’s shown, and how to take it off.

Also in App hosting and deploy

See all 6 in App hosting and deploy →

Get every post about Vercel, filtered and labelled

This page is the summary. Tracking gives you the stream behind it for any brand, keyword or @mention: each new pain point, request and question as it’s posted, with the spam and promotions already taken out.