Home / Companies / Netlify / Blog / Post Details
Content Deep Dive

Announcing Netlify Edge Handlers: Now in Early Access

Blog post from Netlify

Post Details
Company
Date Published
Author
David Calavera
Word Count
1,550
Company Posts That Month
19
Language
English
Hacker News Points
-
Post removed?
No
Summary

Netlify is announcing early access to its Edge Handlers, a solution that combines edge compute with a Git-based workflow, making it easy for frontend developers to customize the network edge for faster and more engaging web experiences. This allows teams to streamline Continuous Delivery between developers and SREs, bringing edge logic into the same Git repo as Netlify-powered sites and Netlify Functions. Edge Handlers start with traditional software development patterns, providing a developer experience that enables teams to personalize at the edge without sacrificing development velocity. They offer features such as authentication, personalization, internationalization, localization, site-wide changes, and more, all integrated into one workflow. With Edge Handlers, developers have full control over how their content is served to end-users, enabling fast personalized experiences while using tools and Netlify workflows already known. This marks the next evolution of Jamstack websites and web apps, with Edge Handlers allowing for the creation of unique content based on logic defined by the handler, respecting conditions such as user identity, cookie settings, and location. The announcement also includes the upcoming availability of Background Functions, enabling developers to run longer serverless functions for up to 15 minutes, further expanding the capabilities of Jamstack websites and web apps.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Serverless 10 676 96 39 +26%
Developer Experience 1 100 63 36 +75%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.