Changelog

Google’s Gemini 4 Hydrogen model is now available through Netlify’s AI Gateway and Agent Runners with zero configuration required.

Use the Google GenAI SDK directly in your Netlify Functions without managing API keys or authentication. The AI Gateway handles everything automatically. Here’s an example using the Gemini 4 Hydrogen model:

import { GoogleGenAI } from '@google/genai';

export default async () => {
    const ai = new GoogleGenAI({});

    const response = await ai.models.generateContent({
        model: 'gemini-4-hydrogen',
        contents: 'How can AI improve my coding?'
    });

    return Response.json(response);
};

Gemini 4 Hydrogen is available for all Function types and Agent Runners. You get automatic access to Netlify’s caching, rate limiting, and authentication infrastructure.

Learn more in the AI Gateway documentation and Agent Runners documentation.

Netlify Server lets you run your application’s backend as a long-lived Node.js server. Netlify provisions it, scales it with demand and scales it down to zero when nothing is using it.

Whereas, functions handle one request per instance and finish when they respond, some backends need more. Netlify Server keeps running between requests so that it can:

• Handle many requests at once in a single instance.
• Keep warm database connection pools and in-memory caches.
• Hold WebSocket and Server-Sent Events connections open, for things like live chat and real-time collaboration.
• Run an existing Express, Hono, Fastify or Koa app as-is, without additional adapters.

A server is a single file at netlify/server/index.ts. Here’s a simple way to get started without any framework, with the same signature as a Netlify function:

import type { Context } from '@netlify/server';

export default async (req: Request, context: Context) => {
  return Response.json({ message: `Hello from ${context.geo.city}` });
};

Every deploy, including branch deploys and Deploy Previews, runs its own version of your server. The server can use other platform primitives, such as Netlify Database, Netlify Blobs and the AI Gateway, with no setup.

Full-stack frameworks such as Next.js, Astro and Nuxt don’t run on Netlify Server yet, so for now we recommend using a server in projects that don’t use one of these frameworks.

Early Access

Netlify Server is available on credit-based plans and on Enterprise plans with credits enabled. Its APIs and behavior might change during Early Access.

In Agent Runners, we’re releasing Netlify Server gradually over the coming days, so your agent runs might not use it right away.

Limits

These are the main limits during Early Access:

• A server scales up to 3 instances, or 1 instance on credit-based Free and Personal plans.
• An instance always scales to zero after 5 minutes without requests. After Early Access, you’ll be able to keep a minimum number of instances running, so infrequent requests won’t need to wait for your server to start.

The limits page has the full list.

Pricing

Netlify Server is free to use during Early Access. When it reaches General Availability, usage will be charged in credits based on two meters: reserved memory (in GB-hours) and active CPU time (in vCPU-hours). We’ll announce the cost in credits before then. If your usage during Early Access suggests you’ll need to upgrade your plan or buy more credits, we’ll let you know.

Other metered features in your project are billed as usual, and every request your server handles counts toward the web requests meter. Learn more about pricing.

To get started, read the Netlify Server docs and follow the guide to create your first server.

Netlify Visual Editor is deprecated as of November 10, 2026, and will reach end of life on February 8, 2027. After that date, Visual Editor will no longer be available or supported.

Your sites stay live and your content stays right where it is. The only thing that changes is how you make edits.

Timeline

If your team already has Visual Editor enabled, you can keep using it until February 8, 2027, and the Visual Editor docs still apply until then. No new teams or projects can enable Visual Editor.

How to keep editing

The Visual Editor, previously called “Netlify Create”, was designed before prompting updates was a common way people worked. Depending on how your team works, here’s how to keep editing:

• Using a CMS? Keep editing there. Nothing changes for you.
• Already using Claude or Codex? Point your agent to netlify.ai to get the skills and tools it needs to work with your project.
• Want to edit with a prompt in Netlify? Open your project and tell Agent Runners what to change. There’s nothing to install, configure, or connect first. You’ll see the result in a side-by-side preview, and nothing goes live until you publish.

Edit with Agent Runners

Agent Runners runs on credits, so you need a credit-based plan or an Enterprise plan that uses credits. If you’re on a legacy plan, compare plans or learn how to change your pricing plan.

A few things you can ask Agent Runners for:

• Edit content: “Update the homepage headline and swap the hero image.”
• Fix a layout: “The pricing cards stack badly on mobile. Fix the spacing.”
• Add a page: “Add an About page with our team and a contact form.”

Share feedback and get help

We’ll keep adding to what Agent Runners can do, and we want to hear what you’d like next. Tell us in the Netlify Discord, where the team and other builders are around to help and swap tips.

Learn more in the Agent Runners docs, or reach out to Netlify Support with any questions.

Google’s Gemini 4 Carbon model is now available through Netlify’s AI Gateway and Agent Runners with zero configuration required.

Use the Google GenAI SDK directly in your Netlify Functions without managing API keys or authentication. The AI Gateway handles everything automatically. Here’s an example using the Gemini 4 Carbon model:

import { GoogleGenAI } from '@google/genai';

export default async () => {
    const ai = new GoogleGenAI({});

    const response = await ai.models.generateContent({
        model: 'gemini-4-carbon',
        contents: 'How can AI improve my coding?'
    });

    return Response.json(response);
};

Gemini 4 Carbon is available for all Function types and Agent Runners. You get automatic access to Netlify’s caching, rate limiting, and authentication infrastructure.

Learn more in the AI Gateway documentation and Agent Runners documentation.

Following our recent change to form notification email requirements, you can now send notifications to email addresses outside your Netlify team no matter what pricing plan you are on.

You can now send form notifications to email addresses that don’t belong to a member of your Netlify team, such as a client or a shared inbox like orders@company.com, as long as the recipient confirms they want to receive them.

When you add an email address that isn’t connected to a member of your Netlify team, Netlify first sends that address a short email asking whether it wants to receive notifications for your form. No form notifications are delivered to the address until the recipient clicks Confirm. If they ignore the email, they never receive any notifications about your form submissions.

Notifications sent to team members work the same as before and don’t need confirmation.

If you switched a notification to a team member’s address after our recent change to form notification email requirements, you can now add the original address back. After confirming, you’ll start receiving notifications about form submissions to the confirmed email address.

Learn more about form notifications in our docs.

Anthropic’s Claude Fable 5.2 model is now available through Netlify’s AI Gateway with zero configuration required. Use claude-fable-5-2 alongside the other Claude models already available in AI Gateway.

Use the Anthropic SDK directly in your Netlify Functions without managing API keys or authentication. AI Gateway handles everything automatically. Here’s an example using Claude Fable 5.2 with the Messages API:

import Anthropic from '@anthropic-ai/sdk';

export default async () => {
    const anthropic = new Anthropic();

    const response = await anthropic.messages.create({
        model: 'claude-fable-5-2',
        max_tokens: 4096,
        messages: [
            { role: 'user', content: 'How can AI improve my coding?' }
        ]
    });

    return Response.json(response);
};

Claude Fable 5.2 also works in Scheduled Functions, Background Functions, and Edge Functions, with Netlify’s caching, rate limiting, and authentication infrastructure available automatically.

Learn more in the AI Gateway documentation.

Meta’s Muse Ember 1.0 model is now available through Netlify’s AI Gateway with zero configuration required. Use muse-ember-1.0 alongside the Muse Spark and Muse Wonder models already available in AI Gateway.

Use the OpenAI SDK directly in your Netlify Functions without managing API keys or authentication. AI Gateway takes care of the setup automatically. Here’s an example using Muse Ember with the Responses API:

import OpenAI from 'openai';

export default async () => {
    const meta = new OpenAI();

    const response = await meta.responses.create({
        model: 'muse-ember-1.0',
        input: 'How can AI improve my coding?'
    });

    return Response.json(response);
};

This Meta model also works in Scheduled Functions, Background Functions, and Edge Functions, with Netlify’s caching, rate limiting, and authentication infrastructure available automatically.

Learn more in the AI Gateway documentation and explore the models on Meta’s developer site.

Netlify now publishes a JSON schema for netlify.toml, so you can catch configuration errors in your editor instead of in a failed deploy. The schema describes the supported properties, the values they accept, and what they do, shortening the feedback loop for discovering and fixing mistakes.

To use it, add a $schema key at the top of your netlify.toml:

"$schema" = "https://open-api.netlify.com/netlify.schema.json"

[build]
  command = "npm run build"
  publish = "dist"

If you write code yourself, editors that support JSON schemas for TOML files can suggest properties as you type, show their descriptions inline, and flag invalid values as you work. In VS Code, install the Even Better TOML extension to turn on schema support for TOML files. You no longer need to keep the docs open in another tab or learn about a typo from your build log.

If an agent writes code for you, the same schema gives it a machine-readable contract for the file. Agents can check the configuration they generate against the schema and fix invalid properties or values before anything is deployed, instead of deploying, reading the failure, and trying again. That means fewer broken deploys for you to review and a faster path from a generated netlify.toml to one that works.

Netlify ignores the $schema key when it builds and deploys your project. Some checks, such as whether a configured directory exists, can only happen during the build, so a file that passes the schema can still fail to build.

Learn more about schema validation for netlify.toml.

OpenAI’s GPT Image 2.6 Sunburst (gpt-image-2.6-sunburst) and GPT Image 2.6 Flare (gpt-image-2.6-flare) models are now available through Netlify’s AI Gateway with zero configuration required.

Use the OpenAI SDK directly in your Netlify Functions without managing API keys or authentication. AI Gateway handles everything automatically.

GPT Image 2.6 Sunburst and GPT Image 2.6 Flare are also available across Scheduled Functions, Background Functions, and Edge Functions. You get automatic access to Netlify’s caching, rate limiting, and authentication infrastructure.

Learn more in the AI Gateway documentation.