Netlify

Dana and the team spent Wednesday night with Barcelona's AI builders at La Fabrica &Co. Thanks to HackBarna, Happy Operators and Matt Roberts for organizing, and to everyone who came out!

What can you build in an hour? Richard Terry-Lloyd showed Karthik Puvvada a sales dashboard he had built that morning to track bookings, pipeline, churn, hot leads, and forecasts. It's interactive, links directly into Salesforce reports and Notion docs, and lets him switch between monthly and quarterly views. The point wasn't just how quickly it came together. It was that the people closest to the work can now build the tools they need, tailor them to their own workflows, and keep improving them over time.

The build versus buy conversation isn't going away. The criteria are changing. In this conversation, Richard Terry-Lloyd explains how Netlify approaches that decision. Some tools are worth building. Others are worth buying because they help the team move faster and already fit the way people work. The goal isn't to build everything. It's to spend your time building the things that create the most value while letting great tools handle the rest.

Same prompt. Four models. No names until the reveal. A new frontier model drops almost every week, and everyone has a favorite. The question that matters is which one does the best work for the job you actually do. This Thursday, Karthik Puvvada and Tania Chakraborty are putting that to the test, live and blind. We'll run the newest models from Anthropic, OpenAI, and Mistral on real community and social tasks, from a nudge to a quiet superfan to a scroll-stopping launch hook. Every output shows up unlabeled, and the names only come out after the votes are in. Behind the scenes, every model runs through Netlify AI Gateway. That's one app and one setup, and swapping in a different model takes seconds, with no new keys and nothing to rewire. If you know your field cold and want to see which model actually earns its place in your work, come judge with us! Thursday, October 8, 12pm ET https://luma.com/0f036rrt

Gemini Nano Banana 2.1 is in AI Gateway, which means image generation now works from a Netlify Function with no API keys to configure. The example in the changelog is a complete Function. It reads a prompt from the query string, sets aspect ratio and image size in the config, pulls the inline image data out of the response, and returns the bytes with the correct content type. Calls work from Scheduled, Background, and Edge Functions too, and they pick up Netlify's caching, rate limiting, and authentication. https://lnkd.in/gEfGvn6T

Mathias is speaking at Claude Founder House in SF, which kicks off today. The registration link is in the comments on Veronica's post if you're in town. Say hi to him if you make it!

Great recap from KP. If you're on Svelte, look at SvelteKit 3. You get day-one support, and npx sv migrate sveltekit-3 moves the config for you. The rest is at netlify.com/changelog.

Netlify is returning to Barcelona tomorrow, Wednesday, October 7, in collaboration with HackBarna and Happy Operators. Here's the evening: a live Agent Runners demo from Netlify PM Vanessa Ramos, a fireside chat with CTO Dana Lawson and CPO Wade Wegner on where the web is heading, then an open mixer with drinks, snacks, and the Netlify crew. Every attendee will walk away with 3,000 Netlify credits and swag. Bring your hardest question for the panel! RSVP: https://luma.com/3xawjg1c

Netlify Edge Functions now run on compute inside our own network, which changes what we can build next. The documented limits of 50ms of CPU per request, 512MB of memory, and 20MB of compressed code came from the isolate execution model. Those are on the table now. npm packages already work in Edge Functions in beta, with caveats around native binaries and importing files at runtime. A real VM with a real filesystem removes most of the reasons those caveats exist. https://lnkd.in/gTpsxN7a

Mathias Biilmann Christensen's talk from WeAreDevelopers is up. It's the case for Agent Experience as its own discipline, and for why software engineering matters more rather than less as the tools change. Thanks to the WeAreDevelopers team for hosting it!