SMF·NETLIFY
Can a prompt replace Netlify?
Hosting & deployment — web hosting + deploy pipeline
Exhibit tracking slip
Verdict
A git-push deploy pipeline to your own server with branch previews on subdomains is a real weekend build. What doesn't come with it is Netlify's actual product: a global CDN and edge functions, and a hosted platform whose reliability isn't your own server's uptime.
Exhibit A — The prompt
Received on30.07.2026Build a personal static-site deploy pipeline on your own server: a small service that receives a webhook on push, pulls the repository, runs the project's build command, and atomically swaps a live symlink to the new build — a failed build must leave the currently-live site untouched. Keep a handful of recent builds per site so rolling back is a one-line command. Support branch previews: a push to any branch other than the main one deploys to its own subdomain automatically, routed through a wildcard reverse-proxy rule. Log build output per deploy and expose a simple status command listing sites, last deploy time, and pass/fail.
Do not build a global CDN, edge functions, hosted forms, or a web dashboard — this is one server, not a global network, and a command-line status view is enough for a personal tool.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 a global CDN and edge functions
- B.2 hosted forms
- B.3 built-in redirect and header rules
- B.4 team workflows
- B.5 uptime that isn't tied to a single server
Prior art
Exhibit C — Why people still pay: hosting/infrastructure
Even a simple site still needs dependable CI/CD, routing, and previews — people pay so that infrastructure isn't something they run themselves.
Questions
Can I migrate my existing Netlify sites?
The build command and output directory, yes — those map directly onto this setup's per-site config. Netlify-specific features like hosted forms and edge functions need rewriting, since there's no drop-in equivalent here.
Will it work for a team?
For deploys, yes, if everyone has push access to the repository. What doesn't come with it is Netlify's own team-permission and review workflow around deploys.
What does it cost to run?
One small VPS and a domain, typically under ten dollars a month — often less than Netlify's paid tiers once a project needs more than the free allowance.
What's the one thing that doesn't survive the rebuild?
The global CDN. Netlify serves every site from locations near each visitor worldwide; a single VPS serves from one location, and matching that spread is a real infrastructure project on its own.
Related tools
Receipt