Netlify ships Server: a plain-language map of serverless functions vs long-lived servers vs VMs
thisiskp_ · x · 2026-11-12
Netlify launched Netlify Server this week—a long-lived Node.js server it provisions for you that stays up between requests—and this post pairs it with a beginner-friendly map of where it sits vs serverless functions and VMs.
- Serverless functions: wake for one request, then finish. Best for webhooks, form notifications, scheduled jobs; cheaper for occasional traffic.
- Netlify Server: stays warm, sleeps after 5 min idle, keeps memory/state across requests; fits WebSockets, warm DB pools, or Express/Hono/Fastify/Koa apps.
- VMs: most control, pay even when idle, for specific runtimes or multiple long-running processes.
- Rule of thumb: WebSockets need Netlify Server (a function can't hold one open); start with functions for standalone jobs, a VM when you need the box itself. Early Access.
More from coding & agent
- Emulating Humanlike Mouse Moves and Key Timing to Make Agents Undetectable — Darpinian · 2026-11-12
- Stanford NLP course's best homework: build your own agent harness — stanfordnlp · 2026-11-12
- Anthropic details agent memory: dreaming organizes Claude's memory, wiki+search hits 61% — RLanceMartin · 2026-11-12
- Talk preview: scaling 1,000 Fable 5.2 agents to formalize Fermat's Last Theorem — RLanceMartin · 2026-11-12
- Why Real Consumer PCs Are the Only Unblockable Way to Run Computer Use Agents — Darpinian · 2026-11-12
- Opinion: AI infra is becoming a coding runtime as intelligence units outgrow tokens — prateekj · 2026-11-12