Netlify Hosting Setup Guide: What It Costs and How to Deploy a Business Website This Week
By UVIDSTUDIO · July 28, 2026 · 8 min read · Development
Netlify's free tier covers most small business sites outright, and Pro starts around $19/member/month once you need more bandwidth or team seats. The real cost math, the deploy-from-git setup order, and where it stops being the right host.
Netlify solved a problem most small business owners never think about until it bites them: how a website actually gets from a developer's laptop onto the internet reliably. Instead of FTP-ing files to a server and hoping nothing breaks, you connect a GitHub repository and every push builds and deploys automatically, with a preview link for every change before it goes live. For a modern React or static site, that workflow is now the default rather than the exception — the question is what it actually costs once you're past the free tier, and how to set it up so it doesn't become one more account nobody remembers the login for.
The cost structure
Netlify's Starter plan is free and covers a real amount of usage: roughly 100GB of bandwidth and 300 build minutes a month, unlimited sites, and automatic HTTPS — genuinely enough to run a single marketing site or campaign landing page for a small business with normal traffic. The Pro tier runs around $19 per team member per month and lifts the ceiling to about 1TB of bandwidth and 1,000 build minutes, adds password-protected previews, and unlocks background functions and priority support — the tier most agencies land on once a client site is live and someone needs staging environments they can share with a client for sign-off. Business, at roughly $99/member/month, adds SSO, audit logs, and SLA-backed uptime, which is overkill until compliance or a large team makes it a requirement rather than a nice-to-have.
The line item that surprises people is overage, not the subscription. Exceed your bandwidth allotment and Netlify bills per additional gigabyte rather than cutting off the site — reasonable for an unexpected traffic spike, expensive if a site is chronically undersized for its tier and nobody notices for a few months. Serverless function invocations and build minutes both meter the same way. Budget a buffer above your average month, not your average day, and check usage quarterly rather than assuming the free tier is permanent.
Setup: the this-week version
A rushed Netlify setup usually means a site that deploys fine but nobody besides the original developer can touch. Do it in order instead.
1. Connect the git repository, not a manual upload. Link GitHub, GitLab, or Bitbucket so every merge to your main branch triggers an automatic build — this is the entire point of the platform, and skipping it for drag-and-drop file uploads throws away the deploy-preview workflow that makes Netlify worth using.
2. Set the build command and publish directory explicitly. Whether the site is built with Vite, Next.js, or a static generator, confirm the build settings match your framework's output folder before the first deploy — a wrong publish directory is the most common first-week failure.
3. Point your custom domain at Netlify and let it provision SSL. DNS propagation can take a few hours; do this early in the week, not the morning of launch, and verify the certificate is active before announcing anything.
4. Turn on deploy previews for pull requests. Every proposed change gets its own shareable URL before it touches production — the fastest way to get client sign-off on a homepage tweak without a second staging server to maintain.
5. Set environment variables in the dashboard, never in the repo. API keys and form endpoints belong in Netlify's environment settings, not committed to git where they're visible to anyone with repo access.
6. Wire form handling or a serverless function if the site needs one. Netlify Forms can capture a contact form without a backend at all; anything more complex — a booking flow, a donation webhook — is a function, not a reason to spin up a separate server.
Where it fits — and where it stops
Netlify fits static and JAMstack sites — marketing pages, campaign microsites, documentation, headless-CMS-driven builds — where content changes through a git-based workflow rather than a database an editor logs into daily. It's the natural home for a site built with the same modern tech-stack thinking this site itself uses, and its build-and-preview pipeline routinely improves Core Web Vitals simply by removing the server-response variability that plagues shared hosting.
It stops being the right tool the moment your site is fundamentally WordPress, Shopify, or another database-backed CMS a non-technical team edits directly — that's managed WordPress hosting territory, not a static build pipeline. And the moment your project is an actual application rather than a page — a persistent backend, background jobs, a database you manage yourself — DigitalOcean offers more granular infrastructure control than Netlify is built to expose, at a flatter, more predictable price than AWS. If your site is specifically Next.js, it is also worth weighing against Vercel, whose framework-native tooling is Netlify's closest direct competitor.
The honest summary: Netlify's free tier is a legitimate way to host a small business site with zero monthly cost, and the Pro jump is cheap insurance once a client or team needs shared previews and headroom. Connect git first, set your environment variables properly, and test the deploy pipeline with a throwaway change before launch day. If you'd like help deciding whether your next site belongs on Netlify, WordPress, or something else entirely — and getting it built and deployed right the first time — that's exactly what our web design team does for businesses across Jersey City, Hudson County, and the NYC metro.