Hosting · checked 2026-10-19

Can I vibecode Netlify?

KINDA· weekend project

Netlify's loop is: push to Git, build in a container, publish the output, give every branch its own preview address. On one VPS, a small webhook service that runs builds in Docker and lets Caddy serve a folder per deploy does that for your own sites in a weekend, and Coolify or Dokku already do it for free. What you can't copy is the edge: a CDN with copies of your files in many regions, functions and forms without a server to babysit, and a platform that stays up while you sleep. For a handful of personal sites it is a real option, but you take on TLS, DNS, patching and the server itself.

$9/moprice

$108you'd save a year

weekendbuild time

—people replaced it

Before you start

What you need on hand.

DifficultyAdvanced · Real infrastructure or OAuth work.

TimeA weekend; DNS and certificates are the slow part

Claude Code, Codex or CursorAny of them can run the prompt.
A small VPSLinux with Docker and Caddy installed and ports 80 and 443 open.
A domain you controlA wildcard DNS record is needed for per-branch preview addresses.
A GitHub webhook secretAdded to each repository's webhook settings by hand.

Before you buildNetlify Free is a hard cap of 300 credits a month. If your sites have little traffic and you deploy rarely, it may be enough; check your credit use before paying or self-hosting.

1. Install one agent: Claude Code, Codex, Cursor.
2. Make an empty folder and open it in the agent.
3. Paste the prompt below, press enter, and answer its questions as it builds.

The prompt

Build me a personal Git-push site host to replace Netlify for my own static sites. Requirements:

- Node.js 22 + TypeScript on one Linux VPS that has Docker and Caddy installed. A Fastify service
listens on 127.0.0.1:4800 (`npm start`); it writes Caddy config through Caddy's admin API on
localhost:2019 and Caddy serves the sites and handles HTTPS.
- Storage: better-sqlite3 in ./data/host.db for sites (name, repo URL, production branch, build
command, publish directory, env vars encrypted with a key from .env), builds (commit, status,
log, timestamps) and deploys. Build output lives in ./data/sites/<site>/<deploy-id>/ with a
`current` symlink per site; keep the last 10 deploys.
- Webhook: POST /hooks/github verifies X-Hub-Signature-256 against the secret in .env. A push to
the production branch builds production; a push to any other branch builds a preview; a closed
pull request deletes its preview.
- Build: `git clone --depth 1` into a temp folder, then run the build command in a `node:22`
Docker container with a 10-minute timeout and a 1 GB memory limit; copy the publish directory
into a new deploy folder. Stream the log to the UI.
- Serving: production at <site>.<BASE_DOMAIN>, previews at <branch>--<site>.<BASE_DOMAIN>, optional
custom domains per site. Use Caddy on-demand TLS with an `ask` endpoint that approves only
hostnames in the database. Switching `current` is the deploy; rollback points it at an older
deploy folder.
- Redirects and headers: read `_redirects` and `_headers` files in Netlify's format from the
publish directory and turn them into Caddy rules, so existing sites keep working.
- Admin: a server-rendered page on 127.0.0.1:4801 (one password in .env, signed cookie) to add a
site, see builds and logs, trigger a build, roll back and edit env vars. Reach it over an SSH tunnel.
- Check: after each deploy request the site's URL and mark the build failed unless it returns 200.
- Single user. No accounts, no telemetry. Outbound calls: git clone and your package registry.
- Out of scope: serverless functions, forms, a CDN, image optimization, team members.
- README: the DNS records, installing Docker and Caddy, opening only ports 80 and 443, and a warning
that running other people's builds on this machine is unsafe.

Opens your agent with the prompt filled in, you press enter. Or copy it and paste it into an empty folder.

Share on X

Max MiskowSponsoredAI agents, automations and MVPs, built for your company.Visit site ›

Then keep going

Next prompts, same folder.

The first prompt builds the core. Run these one at a time in the same folder to grow it into your own Netlify.

Extend the site host in this folder. Requirements:

- After a preview deploy succeeds, post or update one comment on the pull request with the
  preview URL and commit, through the GitHub REST API with a fine-grained token from .env.
- Edit the same comment on later pushes instead of adding new ones.
- Mark the commit with a status (pending, success, failure) that links to the build log.
- Update the README with the token's minimum permissions.

Add protection for preview sites to the site host in this folder. Requirements:

- A per-site setting for preview protection: off, basic auth with a password from the admin
  page, or a link containing a secret token that sets a cookie.
- Apply it through Caddy rules; production stays public.
- Add `X-Robots-Tag: noindex` to every preview response.
- Update the README.

Add a form endpoint to the site host in this folder. Requirements:

- POST /forms/<site> accepts url-encoded or JSON bodies, stores submissions in SQLite and sends
  them to FORM_TO_EMAIL through SMTP settings in .env.
- A honeypot field and a per-IP rate limit of 5 submissions per minute.
- An admin page listing submissions with a CSV download.
- Update the README with a sample HTML form.

What you lose

A global CDN: your sites are served from one machine
Serverless functions, edge functions and scheduled functions
Forms with spam filtering and CSV export of submissions
Netlify Database and blob storage next to the site
Someone else keeping the platform up and the certificates renewed

Why people still pay

The free plan's 300 credits are a hard cap that pauses every site, so anything with real traffic needs Personal or Pro just to stay online. Past that, people pay for previews on every pull request, build capacity and not having to operate hosting at all.

Moatinfrastructure scale execution polish integrations

Do the math

Netlify or your own copy?

Over

Your usage

Count my time12h ×$/h

Netlify, 1 yr$108

Your own copy, 1 yr$110running + build session

Paying is cheaper by$2pays for itself in 15 months

Estimate · A small VPS is the whole running cost, and DNS can stay on a free provider. The build is token usage on your agent plan. You also take on updates and security for the server.

Leaving Netlify

Take your data, then cancel.

1 · Take your data out of Netlify

1Your site's source is in Git, so the deployable part is already yours. Settings that live in a netlify.toml file move with the repo; anything set only in the dashboard (build command, publish directory, redirects) has to be copied out by hand.
2Environment variables: find them under Project configuration > Environment variables, or run `netlify env:list --plain --context production > .env` with the Netlify CLI. Variables marked secret are not shown by the list command, so keep your own copy of those.
3Form submissions: in the Forms tab open a form and choose Download as CSV near the top, or fetch them from the API's listFormSubmissions endpoint. Deleting a form deletes its submissions, so export first.
4Anything you stored in Netlify Blobs or Netlify Database lives only there: copy it out before you leave.

2 · Cancel Netlify

1A Team Owner opens Usage & billing > Plan details and selects Change team plan.
2Choose Free and confirm. A downgrade takes effect at the end of the current billing cycle, and you keep your features until then.
3Unused monthly plan credits are removed when it takes effect; credits from packs or auto recharge stay.
4To remove a saved payment method you must add another one or be on the Free plan.

Free is a hard cap of 300 credits, so a site that moves back to Free can be paused for the rest of the month; move DNS before you downgrade if the site has traffic.
The plan-change page doesn't describe what happens to sites over the Free limits. Ask Netlify support first if that matters.
Moving a team from the credit-based plans back to Legacy plans isn't possible.
Keep the old site running until the new host serves your domain correctly, then switch DNS and check certificates.

Checked 2026-10-19 against Netlify's docs: 1, 2, 3, 4, 5, 6, 7

The escape hatch

Don't feel like building it? These are already free.

CoolifyOpen sourceApache-2.0 self-hostable PaaS with a web UI for static sites, apps, databases and one-click services on your own servers.★ 63k · active Oct 2026 · docker to self-host
serverVisit ↗DokkuOpen sourceMIT Docker-based PaaS that deploys on git push to a single host; command-line only.★ 32k · active Oct 2026 · docker to self-host
serverVisit ↗PikuOpen sourceMIT git-push deployments to your own server, driven from the command line with no web UI.★ 6.6k · active Sep 2026 · self-host, real ops
serverVisit ↗

All 5 free alternatives to Netlify ›

The numbers

Netlify pricing

Plan	Monthly	Annual, per month	What you get
Free	$0	—	300 credits a month (hard limit, no auto recharge), functions, AI models, Netlify Database, blob storage, firewall rules and the global CDN. One team owner.
Personal	$9	—	1,000 credits a month, smart secret detection, 1-day observability, priority email support, optional auto recharge. One team owner.
Pro	$20	—	Starts at 3,000 credits a month with unlimited members; adds private organization repos, shared environment variables, 3 concurrent builds and 30-day analytics.
Enterprise	custom	—	99.99% SLA, enterprise network tier, high-performance builds, SSO and SCIM, log drains, dedicated 24/7 support.

Free tier: 300 credits a month with a hard stop: at the limit every project on the team shows a Site not available page, and the Free plan can't buy more credits.
Billing: Billed per team, monthly; neither the pricing page nor the billing docs mention annual billing. Credits reset at the start of each cycle and unused plan credits don't roll over except on Pro tiers of 5,000 credits and up. Upgrades take effect at once and reset the cycle; downgrades take effect at the end of the current cycle.
Hidden costs: Everything is metered in credits: 15 per production deploy, 20 per GB of bandwidth, 10 per GB-hour of compute and 2 per 10,000 web requests. At the $10-for-1,500-credits pack price a deploy costs about $0.10 and a GB of traffic about $0.13. Auto recharge is off by default, so a traffic spike pauses your sites rather than billing you; turning it on removes that ceiling. Extra concurrent builds are $40 a month each.
Source: www.netlify.com

Also on the list

Vercel$20/mo · HostingKINDA

Webflow$25/mo · Website buildersKINDA

Heroku$7/mo · HostingKINDA

Questions

Netlify, briefly

Not answered here? Tell us and we'll add it.

Ask a question ›

Free gives 300 credits a month as a hard limit; when they run out, every project on the team is paused.

Kinda. The core is a weekend build with the prompt on this page, but real gaps remain: A global CDN: your sites are served from one machine, Serverless functions, edge functions and scheduled functions.

About $9 a month on the Personal plan, $108 a year (checked 2026-10-19).

A global CDN: your sites are served from one machine; Serverless functions, edge functions and scheduled functions; Forms with spam filtering and CSV export of submissions; Netlify Database and blob storage next to the site; Someone else keeping the platform up and the certificates renewed. If any of those matter to you, keep paying.