Skip to content

Netlify

What it is

Netlify is a cloud platform for deploying websites and frontend applications, with a strong focus on JAMstack workflows, previews, and simple frontend operations.

What problem it solves

It makes it easy to publish and iterate on frontend sites without building a full deployment platform from scratch.

Where it fits in the stack

Development & Ops / Frontend Hosting Platform. It is a solid option for marketing sites, JAMstack projects, and frontend-first web experiences that do not require a heavy custom backend on day one.

Core concepts

Atomic Deploys

Netlify uses atomic deployments, meaning every deploy is a full snapshot of your site. This ensures that your site is never in an inconsistent state during a deployment and allows for instantaneous rollbacks to any previous version.

Deploy Previews

Every Pull Request or Branch can be automatically deployed to a unique URL. This allows teams to review and test changes in a live environment before merging to production.

Edge Functions

Netlify Edge Functions allow you to run JavaScript/TypeScript logic at the network edge, closer to your users. This is powered by Deno and is ideal for personalizing content, handling authentication, or modifying headers.

Typical use cases

  • Marketing websites
  • Small product sites and prototypes
  • Static or mostly static frontend projects
  • Form-driven lead capture pages
  • Sites where deploy previews matter to the workflow

Example website types

  • A service business site with a lead form
  • A lightweight content site with a few dynamic widgets
  • A small prototype app front-end paired with Supabase
  • A brand site where the team cares about previewing copy/design changes

Getting started

CLI Installation

Install the Netlify CLI globally via npm:

npm install netlify-cli -g

Authentication & Initialization

Authenticate your CLI session and initialize a new project:

# Login to your Netlify account
netlify login

# Initialize a project in the current directory
netlify init

Manual Deployment

To deploy a site manually from your terminal:

# Deploy to a draft URL for testing
netlify deploy

# Deploy to production
netlify deploy --prod

API examples

Netlify Functions (Serverless)

Netlify Functions (AWS Lambda under the hood) allow you to run serverless backend code. Create a file at netlify/functions/hello.ts:

import { Context } from "@netlify/functions"

export default async (req: Request, context: Context) => {
  return new Response("Hello from Netlify Functions!")
}

Edge Functions

Example of an Edge Function that modifies the response based on the user's country:

import { Context } from "@netlify/edge-functions";

export default async (request: Request, context: Context) => {
  const country = context.geo?.country?.name || "the world";
  return new Response(`Hello from ${country}!`, {
    headers: { "content-type": "text/html" },
  });
};

Strengths

  • Good developer experience for frontend teams
  • Strong fit for static and JAMstack-style deployment
  • Good preview workflow
  • Familiar option for teams that do not want to over-engineer website infrastructure

Limitations

  • Less of a default magnet than Vercel for AI app frontends
  • Not as minimal as GitHub Pages for docs-only sites
  • Backend usually still lives elsewhere

When to use it

  • When the site is mostly frontend and the team likes Netlify's workflow
  • When deploy previews and frontend iteration are central
  • When you want a credible free-tier launch option without treating hosting as a full project

When not to use it

  • When Vercel is the clearer default for a product or AI demo
  • When GitHub Pages is enough for repo-native static docs
  • When the main challenge is backend services rather than frontend deployment

Free-tier comments

  • Good free-tier fit for small websites, prototypes, and forms-oriented launches
  • Pair with Supabase for auth, database, and storage
  • Upgrade when build, bandwidth, team, or function needs become a business bottleneck

Common combinations

Sources / References

Contribution Metadata

  • Last reviewed: 2026-05-16
  • Confidence: high