From Git deployment to a website and application platform
Mathias Biilmann and Christian Bach founded Netlify in 2014, with the service launching publicly in 2015. It began with a workflow that connected Git repositories to automated builds and CDN deployment, then expanded into Deploy Previews, functions and edge capabilities, bringing website delivery and application development onto one platform.
The current enterprise subscription agreement names Netlify, Inc., a Delaware corporation with its principal place of business in San Francisco, as the service provider. Netlify is headquartered in San Francisco and operates with a globally distributed team. The venture-backed company announced a USD 105 million Series D led by Bessemer Venture Partners in November 2021.
Netlify acquired Gatsby Inc. in February 2023 and the visual-editing platform Stackbit in June that year, broadening its content-integration and website-editing capabilities. Its current platform supports building, deploying, running and managing websites and applications, with AI coding agents connected to the same projects and deployment workflows.
Connecting builds, previews and edge delivery
Netlify can build automatically from a Git repository, or accept deployments through the CLI, API and file uploads. Under self-serve terms, Image CDN, functions, Server and data services must be part of a website or application deployed on Netlify. Standalone CDN, compute or storage requirements need a separate agreement. A deployment prepares the complete version before switching it live, keeping HTML and its supporting assets in step. Deploy Previews and branch deployments let developers, editors and clients review changes before they reach the production domain, with previous versions available for rollback.
Static assets are cached across the global edge network and invalidated as deployments change. Functions, edge functions and proxy responses need explicit caching policies. Developers can set separate browser and CDN lifetimes, purge content by tag, and vary responses by cookies, language, country or query parameters. Authentication and personalized data need carefully defined cache boundaries.
The platform includes managed HTTPS, automatic DDoS detection and traffic rules. Rule allowances, team policies and advanced access controls depend on the plan. Enterprise customers can negotiate High-Performance Edge and a 99.99% availability SLA, subject to their contract. New teams on credit-based plans start projects as private and must adjust visibility before serving the public; defaults differ for older teams and other plans.
Image CDN creates image variants on demand
Image CDN resizes, crops and adjusts image quality on request, with formats such as WebP and AVIF for supported browsers. Developers can use project-relative images or allow specified remote sources. Framework integrations are available for Next.js, Astro, Angular and Nuxt. Generated images are delivered through the edge network alongside the site, without preparing every size in advance.
Remote originals must be accessible to Netlify and included in the project’s allowed sources. Image CDN does not forward the visitor’s Cookie or Authorization headers. Project-relative images follow the deployed version; remote images need a separate plan for source updates and caching. Image CDN cannot be used with Split Testing and is excluded from Netlify’s HIPAA-compliant hosting offering.
Choosing functions, edge execution or a persistent server
Netlify Functions handles APIs, server rendering, webhooks and background jobs, deploying with the project and using metered compute. Edge Functions runs Deno-based JavaScript or TypeScript at the edge for redirects, authentication and location- or language-aware responses. The runtimes, execution limits and caching behavior differ. Edge Functions has a 50-millisecond CPU execution limit per request; time spent waiting for resources or responses does not count toward this CPU limit.
Netlify Server is currently in Early Access. It offers persistent Node.js processes for Express, Fastify, Hono and Koa, supports WebSockets and SSE, and can scale to zero when idle. It follows a different deployment path from existing framework functions: full-stack frameworks such as Next.js, Astro and Nuxt cannot yet run directly as a Netlify Server. Each project supports one Server, with up to one instance on Free or Personal and three on other eligible plans. Netlify positions it for evaluation, experimentation and low-volume production at this stage.
Server compute is free during Early Access. General-availability rates for reserved memory and active CPU have not been announced; production deployments, bandwidth, requests and Functions elsewhere in the project remain billable. The platform also includes Blobs for unstructured data, managed Postgres with database branches for previews, and AI Gateway, which converts supported model usage into credits. Plan data storage and compute regions separately from CDN delivery locations when residency matters.
Plans, usage and purchasing terms
Netlify subscriptions allocate a shared credit balance to each team. Delivery, functions, databases, AI and production deploys can all draw from that balance. New accounts created from September 4, 2025 use credit-based plans. Earlier Legacy accounts can retain their plans, but switching to credits is irreversible. Current Pro pricing includes unlimited members rather than Legacy per-seat charges.
Netlify offers no time-limited free trial. The ongoing Free plan includes 300 credits per team each month. Free cannot buy extra credits, and exhausting the balance pauses all team projects until the next billing cycle or an upgrade. The free tier has no SLA.
Self-serve billing accepts Visa, Mastercard, American Express, Discover, JCB, Diners Club and UnionPay, with Apple Pay and Google Pay available on compatible devices, browsers and billing regions. Card acceptance also depends on the issuer and transaction conditions. PayPal and cryptocurrencies are not accepted.
Enterprise customers can arrange ACH or wire transfer under their contracts; these bank payment options do not apply to ordinary self-serve subscriptions. Standard self-serve plans are billed monthly in USD from the account’s billing anniversary. Annual prepayment requires Enterprise arrangements, and prices exclude applicable taxes. Users must be at least 13 and meet any higher local age requirement; some AI features can require age 18. US export restrictions apply to sanctioned locations and restricted parties.
Subscriptions renew automatically. Under the self-serve agreement, avoid renewal charges by terminating in the admin panel at least one day before the term ends, or by written notice at least ten days beforehand. Early cancellation generally does not refund the current term, apart from express contractual exceptions such as qualifying breach remedies. Upgrades normally take effect immediately, reset the billing cycle and prorate the unused previous term; downgrades take effect next cycle. Changing a Pro credit tier removes unused monthly and rollover credits but preserves purchased credit-pack and auto-recharge balances. Export content before termination because retention afterwards is not guaranteed.