Netlify

Netlify basically invented the modern JAMstack deployment workflow. If you’re a frontend developer who wants to push to Git and have a production site live in under two minutes, it’s still one of the best options out there. If you need a traditional server, long-running processes, or a database — skip it and look at Render or a VPS.

I’ve deployed well over 100 sites on Netlify since 2017, ranging from single-page marketing sites to documentation portals with 3,000+ pages. Here’s what I’ve actually experienced, not what their marketing page says.

What Netlify Does Well

The Git-to-deploy pipeline is the gold standard. Connect a GitHub repo, pick a branch, and Netlify auto-detects your framework. I’ve connected Next.js, Astro, Hugo, Gatsby, and plain HTML repos — the detection works correctly about 95% of the time. The remaining 5% just needs a one-line build command in netlify.toml. Every push triggers a build, and the new version goes live on their global CDN. No Docker, no YAML CI pipelines, no server config.

Deploy Previews changed how I work with clients. Every pull request gets a unique URL like deploy-preview-47--yoursite.netlify.app. I send that link to a client, they see the exact changes, and they approve or request edits — all before anything touches production. This feature alone has saved me hundreds of hours of screen-sharing and “can you refresh?” conversations. It works on every plan, including free.

The CDN performance is genuinely good. Netlify runs on a multi-cloud CDN (they use a combination of AWS and GCP edge nodes). For a typical static site, I see Time to First Byte (TTFB) of 30-80ms from North America and 80-150ms from Europe and Asia-Pacific. That’s not the absolute fastest (Cloudflare Pages edges them out by 10-20ms on average), but it’s fast enough that your Lighthouse scores won’t suffer.

Instant rollbacks are a safety net you’ll use more than you think. Every deploy is immutable. If you push a broken build at 2am, you click one button and the previous version is live in under 3 seconds. No Git revert, no rebuild, no downtime. I’ve used this in production emergencies at least a dozen times. It works exactly as advertised.

Where It Falls Short

Bandwidth pricing will bite you if you’re not careful. The free tier gives you 100GB/month. The Pro tier gives you 1TB/month. Go over, and you’re paying $55 per additional 100GB. I had a client’s marketing site go semi-viral — a single blog post with embedded video pulled 800GB in a week. On the free tier, that would’ve been a $385 overage bill. Netlify does alert you, but by the time you get the email, the damage is often done. If you serve any media heavier than compressed images, put your assets on a separate CDN like Cloudflare R2 or BunnyCDN.

Serverless Functions hit walls fast for anything beyond simple API routes. The default timeout is 10 seconds on Starter and Pro. Background Functions extend that to 15 minutes, but they’re async-only — you can’t return a response to the user. If you need to process a file upload, talk to a slow third-party API, or run any computation that takes more than 10 seconds synchronously, you’re stuck. I’ve had to move several projects’ backend logic to separate services because of this constraint. Vercel has the same 10-second limit on their hobby plan but offers 300 seconds on Pro, which is meaningfully better for real workloads.

Build minute consumption is hard to predict. A monorepo with multiple sites can burn through 25,000 Pro-tier build minutes in 2-3 weeks if your team commits frequently. I ran a project with 4 developers pushing 8-10 commits per day to a Next.js monorepo — builds averaged 3 minutes each, and we hit the limit by day 18 of the month. Netlify pauses builds when you run out, which means your deploys just stop until the billing cycle resets or you buy more. That’s a terrible developer experience when you’re trying to ship a fix on a Friday afternoon.

Pricing Breakdown

Starter (Free): You get 1 team member, 100GB bandwidth, and 300 build minutes per month. This is enough for a personal portfolio, a small blog, or a documentation site with moderate traffic. You get serverless functions (125K requests/month, 10-second timeout) and basic form submissions (100/month). Honestly, it’s one of the most generous free tiers in hosting.

Pro ($19/member/month): This is where teams live. You get shared team management, 1TB bandwidth, 25,000 build minutes, and some features that really matter: password-protected sites, background functions, and analytics. The per-member pricing adds up — a team of 5 is $95/month. That’s reasonable, but compare it to Cloudflare Pages which gives you unlimited bandwidth and build minutes on their free tier with team features.

Enterprise (Custom): I’ve seen quotes ranging from $1,500 to $10,000+/month depending on the org size and requirements. You get SSO/SAML, SLA guarantees (99.99% uptime), dedicated account management, priority builds, and advanced security features like audit logs. If you’re at this level, you should be comparing against AWS Amplify and Vercel Enterprise as well.

The hidden cost: overages. Bandwidth overages ($55/100GB) and build minute overages ($7/500 minutes) aren’t shown prominently during signup. Check your usage dashboard weekly if you’re anywhere near your limits. I set up Netlify’s usage notifications at 50%, 75%, and 90% thresholds on every project now.

Key Features Deep Dive

Serverless Functions

Under the hood, Netlify Functions are AWS Lambda functions. You write them in JavaScript/TypeScript (or Go), put them in a netlify/functions/ directory, and Netlify deploys them alongside your site. The DX is simple — you don’t touch AWS, no IAM roles, no API Gateway config.

In practice, they work well for simple use cases: form handlers, API proxies, webhook receivers, auth token exchange. The cold start time is typically 200-500ms for a Node.js function, which is noticeable on the first request but fine for subsequent ones. Where they break down is anything that needs persistent connections (WebSockets are a no-go), long processing times, or access to a filesystem. If your project needs more than thin API endpoints, you’re going to outgrow these fast.

Edge Functions

This is Netlify’s answer to Cloudflare Workers. Edge Functions run on Deno at the CDN edge, meaning they execute before your page is served. I’ve used them for geo-based redirects (show different pricing pages by country), A/B testing (serve different HTML to different user segments), and authentication checks.

Execution time is fast — typically under 50ms for simple logic. The Deno runtime means you write TypeScript but can’t use Node.js-specific packages (no fs, no native modules). The ecosystem is smaller than Node’s, which occasionally means rewriting utility functions you’d normally npm install. Still, for edge personalization without a full backend, they’re excellent.

Deploy Previews and Branch Deploys

This is Netlify’s killer feature and the thing I miss most when working on other platforms. Every PR gets a unique preview URL. But it goes deeper than that — you can configure branch deploys so that staging branch auto-deploys to staging--yoursite.netlify.app and production to the main domain.

I use this in every client project. The QA team tests on the preview URL. The client reviews on the staging branch deploy. Production merges are the final step. No separate staging servers, no manual deploys, no “works on my machine” arguments. This workflow alone justifies using Netlify for agency work.

Netlify Forms

Drop a netlify attribute on an HTML form, and Netlify handles submission processing server-side. No backend needed, no third-party form service. Submissions show up in the Netlify dashboard and can trigger email notifications or webhook calls.

The free tier gives you 100 submissions/month. Pro gives you 1,000. If you need more, it’s $19/month per additional 1,000. For a simple contact form on a marketing site, it’s perfect. For anything more complex — multi-step forms, file uploads over 8MB, conditional logic — you’ll want a dedicated form service like Formspree or just build your own endpoint with serverless functions.

Netlify Blobs

Added in late 2024, Blobs gives you key-value and binary storage directly on Netlify. Think of it as a simpler alternative to S3 for storing JSON config, user-generated content, or cached API responses.

I’ve used it to store CMS webhook payloads and serve them as cached JSON from the edge. It works, but the API is basic — no querying, no indexing, no TTL controls beyond what you manually implement. For persistent data storage, you still need an external database like Supabase, PlanetScale, or Turso.

Split Testing

Netlify lets you run A/B tests by splitting traffic between Git branches. Set 50% of traffic to main and 50% to experiment-new-hero — each branch is its own full deploy.

It’s elegant in theory. In practice, the lack of built-in analytics means you need to pipe data to Google Analytics, Amplitude, or another tool to actually measure results. And the split is done at the CDN level, so there’s no user-level persistence unless you add cookies via Edge Functions. It’s useful for quick landing page tests but not a replacement for a proper experimentation platform like LaunchDarkly or Optimizely.

Who Should Use Netlify

Solo developers and small teams building static-first sites. If your stack is Astro, Hugo, Eleventy, or static Next.js, Netlify is purpose-built for you. The free tier is generous enough for personal projects and small client sites.

Agencies managing multiple client sites. Deploy Previews, branch deploys, and instant rollbacks make client workflow dramatically easier. The ability to spin up a new site in 30 seconds from a template repo is huge for productivity.

Documentation teams. Docusaurus, VitePress, Starlight — all work flawlessly on Netlify. The build times are fast, the CDN delivery is reliable, and the free tier usually covers the bandwidth.

Teams who want CI/CD without infrastructure work. If you don’t want to maintain GitHub Actions workflows, Docker containers, or deployment scripts, Netlify’s Git-push-to-deploy model eliminates that entire category of work.

Who Should Look Elsewhere

If you need server-side rendering with long response times, Vercel gives you better serverless function timeouts on paid plans (300 seconds vs. 26 seconds) and has deeper Next.js integration since they literally build the framework.

If bandwidth costs worry you, Cloudflare Pages offers unlimited bandwidth on every plan, including free. For media-heavy sites, this alone can save you hundreds per month.

If you need a traditional backend — databases, cron jobs, persistent processes — Netlify isn’t the right tool. Look at Render for a modern PaaS that handles both frontend and backend, or AWS Amplify if you’re already in the AWS ecosystem.

If you’re running a large e-commerce site with dynamic inventory, real-time pricing, and complex checkout flows, Netlify’s static-first architecture will fight you at every step. You’ll end up building so many serverless workarounds that you’d have been better off on a traditional platform from the start.

See our Netlify vs Vercel comparison for a detailed head-to-head breakdown.

The Bottom Line

Netlify pioneered the JAMstack deployment model, and it’s still one of the best platforms for shipping static and hybrid sites with minimal DevOps overhead. The free tier is real, the DX is excellent, and Deploy Previews remain the feature I wish every platform would copy. Just watch your bandwidth usage, know the serverless function limits before you build around them, and don’t try to make it into something it’s not — it’s a frontend platform, and it’s great at that job.

---

Disclosure: Some links on this page are affiliate links. We may earn a commission if you make a purchase, at no extra cost to you. This helps us keep the site running and produce quality content.