[verdict][generated prompt][source: netlify.com]
Can I vibecode Netlify?
// buildable in a weekend, but real gaps stay open
Static hosting and functions are easy to assemble, but Netlify's value is Git-based deploys, previews, forms, redirects, edge functions, and managed platform reliability.
confidence: high
what it is: Web hosting platform for static sites, functions, forms, and deploy previews
Buildability index · an editorial game
- Price 20 $/month 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 6 items weight: minus 3
- Site netlify.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.
What you build
Deploy static builds from git, serve via CDN/reverse proxy, add forms/functions, and create preview URLs.
what you need
- VPS or cloud static hosting
- CI/CD
- domain/DNS
- SSL
- serverless or container functions
- monitoring
Good to pair with Vercel; users can compare platform lock-in vs self-hosting.
The prompt
A weekend with a coding agent. The gaps that stay are right below, under “what you lose”.
Build me a personal static-site deploy pipeline to replace Netlify, running on my own
VPS. Requirements:
- A small deploy service: Node + Express receiving a GitHub webhook on localhost, with
Caddy in front serving the built sites over HTTPS.
- On push to main: pull the repo into /srv/sites/<repo>/, run the build command from a
per-site config (sites.json: repo, branch, buildCmd, outputDir), and atomically swap a
`current` symlink to the new build.
- Keep the last 5 builds per site on disk so rollback is `deployctl rollback <site>`, a
one-line CLI.
- Branch previews: pushes to other branches deploy to <branch>.<site>.mydomain.com via a
Caddy wildcard route.
- Build logs go to /srv/sites/<repo>/logs/<timestamp>.log; `deployctl status` lists
sites, last deploy time, and pass/fail.
- Webhook secret and tokens in .env. The service binds to localhost behind Caddy; no
accounts, no telemetry.
- Out of scope: CDN/edge functions, form handling, and team features. This is one VPS,
not a global network. Skip the dashboard UI, the CLI is enough.
- README: the Caddy config snippet, GitHub webhook setup, and the wildcard DNS record
previews need.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
- deploy previews
- CDN/edge functions
- forms
- rollbacks
- team workflows
- uptime/support
Why people still pay
They pay because simple sites still need dependable CI/CD, routing, and previews.
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 (2) — and why
- Cloudflare Pages Free (si apre in una nuova scheda) — Previews and functions are excellent; the missing built-in forms service means it does not replace the whole Netlify job.
- Coolify (si apre in una nuova scheda) — Great for hosting apps, but deploy previews, serverless functions, and a managed form inbox do not arrive as one finished product.
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 deployment platform for apps, databases, and static sites. (alive)
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.
