FINDING 01·Backend and polyglot developers migrating from Heroku·3 sources
Poor support for non-JavaScript / non-Next.js runtimes
Developers using Python (Selenium/headless Chrome), Ruby on Rails, Django, and Flutter repeatedly hit walls deploying to Vercel — missing buildpack equivalents, broken runtimes, and 404 errors are common complaints.
Source
“My last project is python selenium bot… But the problem is I could not find anything like buildpack in vercel to add Chrome and Chromedriver.”
Source
“I'm trying to deploy my Rails application on Vercel directly from the respective GitHub repository but, as you can see from the picture, it throws a 404 error… this website was previously deployed on the free version of Heroku, so I just want to find another easy way to redeploy it.”
Source
“I'm trying to deploy my django app on Vercel but it isn't working… It's raising this error: Error: Function Runtimes must have a valid version.”
FINDING 02·Security-conscious teams and companies with compliance certifications·1 source
Security & compliance concerns after breach
As of early 2026, users with security compliance requirements (certs, audits) are actively reconsidering Vercel after a reported breach, making trust a live blocker for enterprise adoption.
Source
“Having read some of the comments about this company after the breach, I'm concerned about building anything else on this platform as my company needs to maintain several security compliance certs.”
FINDING 03·Full-stack and real-time application developers·1 source
Lack of WebSocket and persistent connection support
Vercel's serverless architecture does not natively support WebSockets, which is a meaningful gap for developers building real-time applications — explicitly cited as a motivation for building an alternative.
Source
“I made a Vercel alternative with WebSocket support… Tilda is my venture to build a Vercel alternative with a focus on open web standards.”
FINDING 04·Indie developers, startups, and cost-sensitive teams·1 source
Vercel's high cost drives users to seek alternatives
Pricing is a persistent, recurring pain point across multiple years (2025 discussions), with users explicitly framing alternatives in terms of cost savings — some citing 7–8x cost differences or self-hosting to cut bills significantly.
Source
“Own Vercel alternative in 8 less cost. Do self host in one command”
FINDING 05·Next.js developers considering self-hosting or migration·2 sources
Next.js features locked to Vercel platform
Developers worry that certain Next.js capabilities are exclusive to Vercel's infrastructure and cannot be replicated on self-hosted or alternative platforms, creating vendor lock-in concerns.
Source
“I would like to know, if all the functionality of nextjs is possible to replicate on private dockers servers or any type of jamstack itself or some functionality is limited only to the vercel platform.”
Source
“Tilda supports Next.js deployments with (almost) all features working exactly as they do on Vercel with zero code-changes to your project.”
FINDING 06·Production teams and developers dependent on CI/CD pipelines·1 source
Deployment reliability and platform incidents
Multiple HN threads from 2023–2026 flag Vercel deployment outages, blocked deployments, missing Middleware, and submission failures — suggesting recurring reliability issues that erode trust.
Source
“Cannot Submit Vercel Deployment?”