[verdict][generated prompt][source: vercel.com]
Can I vibecode Vercel?
// buildable in a weekend, but real gaps stay open
You can deploy to a VPS or self-host PaaS, but Vercel's edge network, preview deployments, CI/CD, observability, and Next.js integration are the paid value.
confidence: high
what it is: Frontend cloud for deploying Next.js and web apps from Git
Buildability index · an editorial game
- Price 20 $/month · per seat weight: plus 2
- Time multi-day weight: plus 1
- Category hosting no weight
- Moat infrastructure scale · execution quality weight: minus 3
- Confidence high weight: plus 1
- What you lose 7 items weight: minus 3
- Site vercel.com (si apre in una nuova scheda) no weight
The moat outweighs the price: rebuilding this is a project, not an evening.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
// free tier: The free Hobby plan covers non-commercial projects; 1M requests and 100 GB monthly.
What you build
Use a VPS/PaaS, connect git webhooks, build/deploy branches, provision HTTPS, and add preview URLs.
what you need
- VPS/cloud account
- domain/DNS
- CI/CD
- reverse proxy
- SSL
- monitoring
- backups
A core infra page: DIY is real, but not 'free' once maintenance is counted.
The prompt
A weekend with a coding agent. The gaps that stay are right below, under “what you lose”.
Build me a git-push deploy pipeline for my own VPS to replace Vercel. Requirements:
- Target: one VPS running Caddy. Each app lives in /srv/apps/<name>/ with a systemd
service and a Caddyfile entry.
- A bare git repo per app on the VPS with a post-receive hook: check out to
releases/<timestamp>, run npm ci && npm run build, health-check the new process,
flip a current symlink, restart the systemd unit. Keep the last 5 releases.
- Deploying is git push vps main; the hook streams build output back to my
terminal. A failed build or health check leaves the live release untouched.
- rollback <app>: re-point the symlink to the previous release and restart, under
10 seconds.
- newapp <name> <domain>: scaffolds the bare repo, systemd unit, and Caddy block,
then reloads Caddy. HTTPS is automatic via Caddy.
- Secrets: each app reads /srv/apps/<name>/shared/.env, symlinked into every
release, never committed.
- No accounts, no telemetry, no dashboard; logs via journalctl -u <app>.
- Out of scope: per-branch preview deployments, edge/CDN, autoscaling, and a web
UI. One VPS, main branch only.
- README: server prerequisites, DNS records, and an honest note that I am now the
platform team, budget time for the first 2am breakage. Prompt generated from the data on this page, not reviewed by hand yet. In English on purpose — it is the language coding agents work best in.
What you lose
- edge/CDN performance
- preview deployments
- scaling
- observability
- image functions
- team workflows
- Next.js integration
Why people still pay
They pay because deploys and previews are boring infrastructure that must not break.
moat: Infrastructure scale Execution quality what a moat is
hosting/infrastructure
Free alternatives
Not in the mood to build it? These already exist, they are free or open source, and we checked them one by one.
Rejected (1) — and why
- Vercel Hobby (si apre in una nuova scheda) — Free, but its terms restrict Hobby to personal or non-commercial use; your business frontend is not a hobby.
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- Coolify (opens in a new tab) — Open-source self-hosted Heroku/Vercel-like deployment platform. (alive)
What it costs in a year
20 $/mese 240 $/anno
Listino 20 $ al mese a persona su Vercel. L’anno è dodici mesi pieni, senza sconti annuali.
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.