Netlify
Netlify, founded in 2014, is a platform for building, hosting and delivering web applications. Its scope includes deploy previews, form handling, redirect rules and Deno-based edge functions that can modify requests in transit.
Netlify is a web platform that builds, deploys and extends applications from Git with edge functions. It is framework-neutral and brings no database product of its own.
Explanation
Netlify helped establish the workflow that feels obvious today: push to a branch, automatic build, preview URL, approval, publish. For agentic projects the combination of redirect rules and edge functions is especially useful — requests can be adjusted, personalised or handed to an agent endpoint before delivery. Important in practice: Netlify provides frontend and functions, but no database. Knowledge base, state and logs therefore live in another service, and the connection details to it are part of the build. That is exactly where the typical surprises come from — for instance when an old build still points at a long-replaced backend.
Marketing Relevance
For teams running several frameworks, neutrality is the main advantage: the same workflow carries Astro, SvelteKit or a React application. What matters for accountable owners is the separation of layers — if you run forms and leads, you must know which backend the currently published build is actually wired to.
Example
A corporate site runs on Netlify, while the backend with database and mail delivery lives in a separate service. A redirect rule normalises old campaign URLs and an edge function adds language-dependent headers.
Common Pitfalls
Because connection details are baked into the build, a stale build can silently point at the wrong backend — requests then go nowhere even though the page shows a success message. Likewise, new routes in a single-page application need a matching fallback rule, otherwise the platform answers with a 404.
Origin & History
Netlify launched in 2014 and coined the term Jamstack: static delivery plus services over APIs. Serverless and edge functions were added later to enable dynamic logic. By 2026 the platform is positioned framework-neutrally and offers a current data processing agreement referencing EU law.
Marketing Use Cases
Delivery of multilingual marketing sites from Git.
Redirect rules for SEO restructures and legacy campaign links.
Edge functions for personalisation or pre-checks on requests.
Deploy previews as an acceptance step for content and legal review.
Frequently Asked Questions
Can I run forms and leads with Netlify?
Yes, either via built-in form handling or via a function that writes to your own backend. With personal data, document clearly which route is used and where the data ends up.
Why does Netlify suddenly return 404 for a new route?
Because it delivers statically and does not know the routes of a single-page application. You need a fallback rule to the entry file plus a fresh build for the route to become reachable.
Netlify or Vercel?
Both suit marketing sites. Netlify is more framework-neutral, Vercel more tightly integrated with Next.js and AI building blocks. The decision usually follows the ecosystem already in use rather than a feature comparison.
Related Services
Go deeper: Agentic AI Hub · Governance & compliance