Netlify Server gives your app a backend that stays alive while people are using it. Build realtime experiences, multiplayer games, and AI agents that need time to finish. Describe what you want and an agent builds it, or bring your Express, Fastify, Hono, or Koa code. It holds WebSockets open, keeps state in memory, and deploys with the rest of your project, with its own server for every preview. Scales with demand and down to zero when idle. Free during early access.
Over the last couple of years, millions of new builders have shown up on Netlify, driven by AI. I know it sounds like a cliche! but honestly, we’ve had a front row seat to this renaissance. And we saw an ever growing number of those wanting to ship use-case like multiplayer apps or live chat, collaborative spaces,rich data dashboards, and AI agents - some of which need to run long agentic loops with tools for minutes to hours.
Those backends kept hitting the limits of functions, and our answer was usually "either adapt to our constraints, or - unfortunately - host that part of your app somewhere else." Of course, this never sat right with me (or any of us).
So we built Netlify Server: a long-running server for your backend, with everything a server can do and none of the work of running one.
To keep it concrete, here’s what having this server means in practice:
Hold WebSockets open for real-time collaboration, games, and chat
Keep connection pools, caches, and state in memory between requests
Run agent loops and long AI calls without racing to fit a timeout
Bring many existing backend apps & tools as they are, with no adapters (with frameworks like Express, Hono, Koa, etc.)
Servers have the same building lifecycle as other projects: you get deploy previews, you can roll back easily, and each branch gets its own Netlify Database branch. So you can safely test changes in isolation before you decide whether to publish any of them. Servers scale up with traffic, and scale to zero when nothing's using them.
The team “Early Access” is probably selling it short tbh, because multiple teams within Netlify have been building with servers for a while - apps that we now use in our daily work. The team was also great just building cool examples. I made one or two, or more, myself 🙂
Usage is free during Early Access. Start with the docs or just tell the agent in the Netlify UI what you want to create. We'd love to know what's the cool real-time / multiplayer / agent idea you've been holding off on!
The long-running server model addresses a real gap for AI agents that need to maintain state across multiple tool calls. Being able to bring Express/Hono directly instead of refactoring for functions is huge - removes a whole category of onboarding friction for teams already invested in those frameworks.
Netlify has been one of my most used platforms this year due to just how easy it is to go from idea to fully working app in literally minutes.
It's so good in fact that it stood up to my stress testing building and launching a new app, every day, for 30 days - TWICE! It's so easy to build and integrates seamlessly with the tools I already use.
Plus it has an amazing community team and Netlify Server is just one more thing that makes it my go-to platform for everything from developing, hosting, and scaling all my projects.
Congrats on the launch (and rebrand) team!
Congrats on shipping this. We run live game rooms where up to 300 phones answer the same question at once, so this is close to home. Two questions: when a server scales down to zero, what happens to a room that's mid-game and holding its state in memory? And is every phone in one room guaranteed to reach the same instance?
Hi, I’m Wade and I run product here at Netlify. Given the team has shared so many great details about Netlify Server, I thought I’d share three cool things at my pre-launch testing party for Netlify Server.
1/ Quiver Hollow, a multiplayer archery game, where the server keeps both human and AI archers in sync, with everyone dodging arrows.
2/ An OpenClaw agent I could chat with on Telegram where the server gives the agent time to work through a task before replying.
3/ A holiday wish wall where you write a wish on a gift tag and hang it up for all to see. It’s a regular Node.js application whose Express backend could run as-is alongside the front end.
We also used Netlify Server at our last board meeting.
Our founder, Matt, had already shown us at an all-hands how much you could do by building the presentation as an app. We did the same thing for our board meeting. Hours before the meeting, we realized how many times we were having to say “next slide, please,” and so Matt updated the board app to let any/all presenters advance the slides from their own laptop. Behind the scenes, server kept a WebSocket open so that when someone went to change the slide, it changed for everyone at the same time.
This is only scratching the surface and the potential. I’m so proud of how my team is shipping and I can’t wait to see what other people build with the Server. If you give it a try, drop me a link!
Excited to play around with Netlify Server. So much fun stuff to build with games and agents. I made a simple game a year ago, and just getting SSE or WebSockets set up was such a pain.
The long-running agent part is what caught me — I've had too many agent runs bump into function timeouts, so a server that just stays alive with state in memory is a big shift. How does the scale-to-zero side work with that — does active work keep a server alive, or can it spin down mid-task?
Love this. 💜 Built a quick real-time help board with Netlify Server earlier and it was surprisingly smooth. The fact that it scales to zero and deploys like the rest of the project makes it really practical. Nice work. And I love the new logo, new color and new website! Congratulations to team Netlify!
Heck yeah, Netlify team! This is awesome. What a week of announcements for ya'll!
I don’t think it can go undersold here but the ability to do whatever you need for as long as you need and not worrying about lambda timeouts and such silliness is amazing. Even more incredible is that it feels like the maintenance overhead (none) of lambda with the capabilities of an always on server. This is a legendary ship 👊👊
Giving each deploy preview its own backend is a useful detail. A reviewer can check the UI change alongside the server behavior it depends on, in the same preview.
Hi! I'm Eduardo, part of the engineering team behind Netlify Server.
I loved building on Netlify before I joined the company and started building Netlify itself. As someone who enjoys building all sorts of applications, there were always things I felt were missing from Netlify when it came to building truly full-stack applications. Real-time capabilities, request concurrency, and long-running executions are great examples.
With Server, Netlify is now a great home for the kinds of applications I previously had to deploy elsewhere. Being able to deploy them alongside my frontend and leverage deploy previews to test my backend, database, and UI in a completely isolated environment has been a game-changer for me.
I hope you enjoy it as much as I do. I can't wait to hear about your experience with the product and see what you build with it!
About Netlify Server on Product Hunt
“Run WebSockets, multiplayer apps, and long-running agents”
Netlify Server launched on Product Hunt on November 19th, 2026 and earned 290 upvotes and 20 comments, earning #3 Product of the Day. Netlify Server gives your app a backend that stays alive while people are using it. Build realtime experiences, multiplayer games, and AI agents that need time to finish. Describe what you want and an agent builds it, or bring your Express, Fastify, Hono, or Koa code. It holds WebSockets open, keeps state in memory, and deploys with the rest of your project, with its own server for every preview. Scales with demand and down to zero when idle. Free during early access.
Netlify Server was featured in SaaS (45.5k followers), Developer Tools (523.5k followers) and Artificial Intelligence (484.2k followers) on Product Hunt. Together, these topics include over 297.9k products, making this a competitive space to launch in.
Who hunted Netlify Server?
Netlify Server was hunted by KP. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Netlify Server stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Hey Product Hunt!
I'm Elad, Principal Product Manager at Netlify.
Over the last couple of years, millions of new builders have shown up on Netlify, driven by AI. I know it sounds like a cliche! but honestly, we’ve had a front row seat to this renaissance. And we saw an ever growing number of those wanting to ship use-case like multiplayer apps or live chat, collaborative spaces,rich data dashboards, and AI agents - some of which need to run long agentic loops with tools for minutes to hours.
Those backends kept hitting the limits of functions, and our answer was usually "either adapt to our constraints, or - unfortunately - host that part of your app somewhere else." Of course, this never sat right with me (or any of us).
So we built Netlify Server: a long-running server for your backend, with everything a server can do and none of the work of running one.
To keep it concrete, here’s what having this server means in practice:
Hold WebSockets open for real-time collaboration, games, and chat
Keep connection pools, caches, and state in memory between requests
Run agent loops and long AI calls without racing to fit a timeout
Bring many existing backend apps & tools as they are, with no adapters (with frameworks like Express, Hono, Koa, etc.)
Servers have the same building lifecycle as other projects: you get deploy previews, you can roll back easily, and each branch gets its own Netlify Database branch. So you can safely test changes in isolation before you decide whether to publish any of them. Servers scale up with traffic, and scale to zero when nothing's using them.
The team “Early Access” is probably selling it short tbh, because multiple teams within Netlify have been building with servers for a while - apps that we now use in our daily work. The team was also great just building cool examples. I made one or two, or more, myself 🙂
Usage is free during Early Access. Start with the docs or just tell the agent in the Netlify UI what you want to create. We'd love to know what's the cool real-time / multiplayer / agent idea you've been holding off on!