HostingCAN I VIBECODE
Netlify?
BUILD FIRST
- One specific customer type and one primary use case
- A vertical slice that completes the main job without manual workarounds
- Visible limits, review steps, and a fallback when an external dependency fails
LEAVE FOR LATER
- Broad third-party integrations
- High-scale collaboration, syncing, and permissions
- Automation that can cause harm without human review
RESEARCH NOTES
What this tool actually does.
Netlify is a web hosting and deployment platform pitched as a 'launch center' for modern web projects. It combines CI/CD from Git, CLI, or drag-and-drop uploads with a global CDN (100+ edge locations), automatic HTTPS, DDoS protection, and auto-scaling. Every push/PR/branch generates a unique Deploy Preview URL that can be promoted to production in one click; any deploy can be rolled back. Platform primitives include serverless/edge/background/scheduled Functions, Forms (submissions without backend code), Identity (auth/user management), Netlify Database and Netlify Blobs, and an AI Gateway for model access. Fine-grained caching, SWR, and image CDN are supported. Team/enterprise features include RBAC, SSO/SAML, audit logs, compliance, and a 99.99% uptime SLA. Docs describe use by solo builders, teams, and AI agents; deploys can be triggered by Git, CLI, drag-and-drop, or AI coding agents
RESEARCHED BUILD PROMPT
Give this to your coding agent.
Build a self-hosted web deployment platform inspired by Netlify's distinctive Git-connect workflow, under a new name and UI. The core loop: user connects a Git repository (GitHub), the service clones it, detects the build command (or uses a deploy config file like deploy.toml), runs the build, and publishes static output plus optionally bundled serverless functions. Every push to a branch or new PR triggers an isolated build that produces a unique preview URL (e.g., pr-123.<project>.example.com). The user can promote a preview to production with one click and roll back to any previous production deploy. Provide: a project dashboard with deploy history and logs; global HTTP serving over an edge cache (cache-control headers, cache-busting by deploy ID); HTTPS via Let's Encrypt; atomic deploys; per-project environment variables; a form-submission handler endpoint; and HTTP redirect/rewrite rules. Implement with Node.js/TypeScript, GitHub webhooks plus Git CLI for repo fetching, Docker for isolated build containers, an S3-compatible object store for immutable deploy artifacts, Postgres for project/deploy metadata, and Nginx for edge caching. Do NOT copy Netlify's brand, logo, colors, terminology, or UI layout; invent your own visual language and feature names. Out of scope (list as explicit limitations): auth/identity, AI gateway, SSO/RBAC, enterprise DDoS protection, compliance, split testing, background/scheduled functions, and multi-region edge execution. Provide a README covering setup (config, webhook, agent), local dev, deploy flow, and known limitations.