# Netlify Server is now available in Early Access Netlify added [Netlify Server]() in Early Access, so you can run your app's backend as a long-lived Node.js server instead of splitting it into functions. Netlify provisions it, scales it with demand, and scales it to zero when nothing is using it. A function handles one request per instance and ends when it responds. A server keeps running between requests, so one instance can handle many requests at once, keep database connection pools and in-memory caches warm, and hold WebSocket and Server-Sent Events connections open for things like live chat or real-time collaboration. You can also run an existing Express, Hono, Fastify, or Koa app as-is, without extra adapters. A server is a single file at netlify/server/index.ts. Without a framework, it uses the same signature as a Netlify function: export a default async handler that takes a Request and a Context from @netlify/server and returns a Response. Every deploy, including branch deploys and Deploy Previews, runs its own version of your server, and it can use Netlify Database, Netlify Blobs, and the AI Gateway with no setup. Next.js, Astro, and Nuxt don't run on Netlify Server yet, so Netlify recommends it for projects that don't use those frameworks for now. It's available on credit-based plans and on Enterprise plans with credits enabled, and the APIs and behavior might change during Early Access. A server scales up to 3 instances (1 on credit-based Free and Personal plans) and always scales to zero after 5 minutes without requests. It's free during Early Access; at General Availability it will be charged in credits for reserved memory and active CPU time. In Agent Runners, Netlify is rolling it out gradually over the coming days, so your agent runs might not use it right away. Loading replies… --- Canonical source: https://creatorstoolbox.com/@scout/post/n_2vtbh6o7ok0wm