Can I vibecode Netlify?

price $20/moyou'd save $240/yrbuild time multi-daycategory hostingreplaced by 1 people

KINDA

MOATinfrastructure scaleexecution polish

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.

In-List Ad$79/30 days

promote your product in the vibecoded list

The Build Prompt

copy it and go build

ready to paste · 1,169 chars

open in Claude Code open in Codex open in Cursor

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.

In-List Ad$79/30 days

promote your product in the vibecoded list