Netlify

There's a difference between a live URL and a production app. Most AI builders give you the first. You get a working prototype with something to show. But when real requirements appear: auth, APIs, data, scale, you're looking at a migration before you can ship. On Netlify, the infrastructure isn't a later problem. Serverless functions, identity and auth, blob storage, AI Gateway. These are part of the project from the start. Not bolted on. Not a separate service tier. Just there, ready when the idea needs them. What starts as a prompt can become a real product without touching any of that. https://ntl.fyi/412VS7a 

Ten years ago, Ryan Neal joined Netlify as one of our earliest engineers. Today, we're celebrating a decade of his craft, dedication, and impact on everything we've built together. In an industry that moves fast and rarely looks back, Ryan is the kind of engineer who makes you believe in the long game. He's not just someone who's been here; he's someone who has shaped here. From the foundations up. To Ryan: thank you for a decade of showing up, digging in, and making Netlify better in ways that will outlast any sprint or launch cycle. We're lucky to have you. 🎉 10 years. Principal Software Engineer. OG. Here's to what's next.

Most AI rate limits are wrong from day one. Set them too tight and you block real users. Set them too loose and one bad traffic day becomes a surprise inference bill. Here is the signal to watch: Above 5% 429 error rate: your limits are too tight. Below 0.1%: they are too loose. 20 requests per 60 seconds per IP is a solid public chatbot baseline. Cap input at 2,000 characters to control token spend per request. Three lines of config in a Netlify function. Edge-enforced. No extra infrastructure to manage. Rate limiting is not a one-time setting. It's a dial you tune from real traffic data, and the sooner you start collecting that data, the more you'll have to work with. Full breakdown: https://lnkd.in/gu5jN_Vh   Most AI rate limits are wrong from day one. Set them too tight and you block real users. Set them too loose and one bad traffic day becomes a surprise inference bill. Here is the signal to watch: Above 5% 429 error rate: your limits are too tight. Below 0.1%: they are too loose. 20 requests per 60 seconds per IP is a solid public chatbot baseline. Cap input at 2,000 characters to control token spend per request. Three lines of config in a Netlify function. Edge-enforced. No extra infrastructure to manage. Rate limiting is not a one-time setting. It's a dial you tune from real traffic data, and the sooner you start collecting that data, the more you'll have to work with. Full breakdown: https://lnkd.in/gu5jN_Vh Turn on screen reader support To enable screen reader support, press ⌘+Option+Z To learn about keyboard shortcuts, press ⌘slash

Most AI builders give you a prototype. Netlify gives you something you can actually ship. Watch what happens when you go to netlify.new, describe what you want to build, and pick an agent: serverless functions, auth, AI Gateway, and blob storage are already there. Not a later step. Not a separate service. Just part of the project from prompt one. Nahrin Jalal walks through the whole thing in under two minutes. https://lnkd.in/eDW8YYB3 https://lnkd.in/eDW8YYB3

AI-assisted building follows a familiar arc. Progress is fast at first. You've got a working app, something you're excited to show. Then around the 70% mark, things slow down. Not because the idea is wrong, but because the platform underneath wasn't built for the rest of the journey. You need auth. Serverless functions. Somewhere to store files. Model access that doesn't require wiring together three services. And suddenly you're looking at a re-platforming project before you can ship the real one. The gap isn't in the generation. It's in what comes after. When you start on Netlify, those primitives are already there: functions, forms, identity, blob storage, AI Gateway. Available from the first prompt, not as a setup step you hit later. You keep building instead of stopping to catch up to your own idea. https://ntl.fyi/412VS7a

netlify.new is live on Product Hunt today. If you've been following the launch or you've already tried building with a prompt on Netlify, we'd love your support and your honest take. Drop an upvote, leave a review, or just check out what the community is saying. https://lnkd.in/etu3Sucy

Who doesn't love a good prototype - we know our customers, do! Thanks for the support Steve Jones, CFA and for building on Netlify.

Netlify co-founder and CEO Mathias Biilmann on what changed today: You can now start a project from inside Netlify. Type a prompt. Pick your agent: Claude Code, Codex, or Gemini CLI. Get a production-ready app without leaving the platform. You can still build anywhere and deploy to Netlify. That hasn't changed. But today, Netlify is also a starting point. Watch the entire message:

Welcome to Netlify, Jack Herrington! If you know Jack, you know he’s been deep in TanStack AI, MCP, and the tooling behind AI apps that actually ship. Here’s Jack's take on our Start with a Prompt news: https://lnkd.in/eZkq-Wma

Netlify is expanding from a deployment platform to the best place to start a new web project, build with an AI agent, and ship to production. In his latest blog post, Mathias Biilmann Christensen shares how every project you start on Netlify now comes with a production-ready foundation that works for both AI-native builders and deep technical developers. This approach also makes it easier for teams to collaborate. Product managers, designers, and other stakeholders can now participate directly in building new pages and features without waiting for developer capacity. The web is evolving and coding agents are becoming the natural starting point for new projects. Netlify is committed to giving every builder the fastest path from prompt to production. Read the full post: https://lnkd.in/eaM6dB_m