Netlify ships the web.

A developer types git push. The internet updates.

It is a Tuesday afternoon in 2026. A product engineer at a logistics startup in Lisbon edits a marketing page, opens a pull request, and within seconds gets a private URL with the new version live. Her manager clicks it on his phone. A designer leaves a comment. An AI agent fixes a typo. The page ships. The team never opens a server console. They never SSH into anything. They never think about a load balancer.

This is, in the broadest sense, what Netlify built. The mundane miracle of "you wrote code, the world saw code" has a name now - and a runtime, and a CDN, and a $2 billion valuation. The runtime is called Netlify. The miracle is called shipping.

You can describe Netlify in two sentences. You can also write a book about it. The short version is a sentence: it's a platform that takes the code in your Git repo and turns it into a fast, secure, globally cached website. The long version involves a manifesto, an architecture, an acquisition or three, a pandemic-era funding round, and a wholesale rethinking of who - or what - actually writes software now.

Once, shipping a website meant renting a server.

The old web was a stack of moving parts that mostly did not want to move together. A LAMP server here. A database connection there. A CMS that demanded its own admin panel. A deploy meant SSHing into a box, running scripts, hoping nothing was on fire. If something was on fire, you fixed it at 2am.

By the early 2010s, this was already, charitably, an embarrassment. Mobile apps were eating the web. Walled gardens - Facebook, Apple's App Store - were starting to look like the future. The open web, the place where anyone could publish anything to anyone, felt slower and clunkier and dumber than it had any right to be.

Mathias Biilmann, a Danish entrepreneur living in San Francisco, looked at all this and saw a different shape. He saw Git, which had just become the universal vocabulary for collaborative coding. He saw static site generators, which were quietly making websites that were faster than any database-backed monster. He saw CDNs, which had become cheap enough to deploy globally. The pieces were on the table. Someone needed to put them together.

In December 2013, Biilmann met Christian Bach over coffee. Bach was a chief digital officer at a Danish firm and had just been diagnosed with Hodgkin's lymphoma. They sketched the idea anyway: a workflow where you push to Git and the world updates. They called it Netlify - short for "simplify the net," which is the kind of name only founders could love until they stop having to explain it.

Two Danes, one couch, a category.

Bach beat his cancer. He moved to San Francisco. Netlify came out of beta in 2015. And then, with the calm confidence of people who have nothing to lose, Biilmann coined a term that would carry the company - and a small army of frontend developers - through the next decade: Jamstack. JavaScript, APIs, and Markup. A pre-built website served from a CDN, with dynamic functionality dropped in through APIs and JavaScript at the edge.

The Jamstack name was, technically, marketing. It was also, technically, brilliant. It gave a generation of developers a shared vocabulary, a community, a conference, and a flag to plant. Around it grew an ecosystem - Gatsby, Next.js, Nuxt, Astro, Sanity, Contentful - and at the center of that ecosystem, conveniently, sat Netlify.

A platform that refuses to be a single product.

Calling Netlify a "hosting company" today is like calling a Tesla a "car." Technically accurate. Slightly insulting. The platform is a stack of opinions about how the web should work, packaged as buttons in a dashboard:

• Deploy Previews - every pull request gets its own live URL, with backend services attached. Designers comment. Marketers approve. QA breaks things on a staging copy of production.
• Edge Functions - serverless code running on Deno at the edge of the network. Personalization, A/B tests, auth checks - no cold start, no region juggling.
• Forms - HTML forms that just work, without you writing a backend.
• Agent Runners - run Claude Code, OpenAI Codex, or Gemini against your actual repo, directly from the Netlify dashboard, with full deploy context.
• AI Gateway - one key for every model. Centralized billing, usage tracking, and credentials across Anthropic, OpenAI, and Google.
• Observability - per-deploy insight into latency, errors, and traffic. Less mystery, more triage.

The product roadmap reads like the company's been on a low simmer for a decade and finally let the lid off. There are also things Netlify won't do, which is its own kind of opinion: it doesn't try to be your database, it doesn't want to be your monolithic CMS, and it has politely declined every chance to become AWS. The platform stays "front of the stack." The back of the stack is somebody else's problem - usually a partner.

Build a faster, simpler, safer web.

The mission statement is a sentence everyone at Netlify can recite without looking. Faster, simpler, safer. It sounds like a slogan. It is, but it's also a constraint - and constraints, as anyone who has ever shipped software knows, are the only thing that makes good products.

Faster means edge networks and pre-built sites that don't have to think. Simpler means git push and not much else. Safer means SSL by default, immutable deploys, instant rollbacks, and a security model where the attack surface is mostly... HTML.

The next user isn't human. It's an agent.

Here is the bet Netlify is making in 2026: the next ten years of web development won't be written by humans alone. They'll be written by humans and AI agents - sometimes in collaboration, sometimes with the human stepping aside entirely. The interesting question is no longer "how do we make developers productive?" It's "how do we make the platform legible to a coding agent that just woke up at 3am and needs to ship a fix?"

Netlify calls this AX - Agent Experience. The framing is half-marketing, half-genuinely useful. The Agent Runners product, launched in late 2025, lets an engineer hand a backlog ticket to Claude Code, Codex, or Gemini from inside the Netlify dashboard. The agent opens a branch, makes the change, opens a PR, and Netlify gives the agent the same deploy preview it would give a human. The human reviews. The merge ships. The clock saves about three hours per developer per week, by Netlify's own count.

The skeptical reading: AI hype, repackaged. The less-skeptical reading: Netlify has been quietly building exactly the kind of platform an autonomous agent would want to use - immutable deploys, branch-based previews, declarative configuration, an API for everything - for a decade. They didn't pivot to AI. The AI pivot came to them.

A few things people get wrong.

• "It's just for static sites." It hasn't been for years. Edge Functions, Forms, Identity, and Agent Runners are very much dynamic.
• "Vercel is the same thing." Close, not the same. Vercel is opinionated about Next.js. Netlify is opinionated about framework neutrality.
• "It's a CDN." The CDN is one layer. There's a build pipeline, a function runtime, an AI gateway, observability, and a partner ecosystem stacked on top.
• "Netlify is the name of the company." Yes - from "simplify the net," and Mathias Biilmann would still like everyone to know.

Back to Tuesday afternoon, Lisbon.

The engineer's pull request gets a thumbs-up. The deploy preview becomes production. The page is live in San Paulo and Stockholm at the same instant. The whole exchange - idea to internet - took eleven minutes. Nobody woke up at 2am. Nobody opened a server console. Nobody, in the old sense of the word, "deployed" anything.

That is what Netlify sells. Not hosting. Not a CDN. Not even, exactly, a platform. What Netlify sells is the feeling that the web is supposed to feel like this - light, fast, collaborative, slightly magical - and that anything less is now a bug. They sell the absence of friction. The absence is worth $2 billion and counting.

The web isn't dead. It's just running on someone else's edge network. And odds are, that network is Netlify's.