A reminder that Next JS is fully supported on Netlify, including advanced features like App Router, ISR, PPR, etc. Migrating should be as easy as linking your repository. If not, get in touch. docs.netlify.com/build/frame…

Netlify is the only place outside of Vercel where Next can be deployed on a serverless front-end cloud with support for all the advanced features. Today we're joining Open Next and starting to share our expertise with the broader community to help make Next run on more platforms.

Same conclusion, RSC is not working out. They add a lot of complexity and tie together front-end, bundling and server runtimes. And in return we get, what? The front-ends people are building with RSCs looks and feels no different to end users than the ones built without them.

Tanstack for apps. Astro for sites. Vite under the hood.

Jamstack has forever changed the direction of the web. Today @Netlify is doubling down on Jamstack in a big way. We’ve raised our Series D round. We acquired OneGraph. And we’re launching a Jamstack Innovation Fund. 🚀 netlify.com/press/netlify-ra…

There's a reason there's a cross industry open source protect called Open Next built just to make next work on other serverless platforms. Other frameworks built with modern frontend clouds as their ideal deployment target have clean adapter architectures and are trivia to port.

S3 was the beginning of the cloud, and simple blob storage turned out to be one of the most fundamentally useful abstractions for all types of cloud applications. Netlify just made it even simpler. netlify.com/blog/introducing…

When a spike in traffic can be automatically and absolutely classified as malicious, our platform is set up to block this. If it’s a new pattern we’ll add it to the automated rules and waive charges. It’s tricky when the traffic in question is not clearly malicious, but could be an indication of a customer being successful. In this case, any automatic block could mean ruining a launch, making a viral campaign go bad or disappointing fans of an emerging artist, etc. For free users, my philosophy has always been that we can never go back and fix it if we ruin your moment of glory, but we can always cancel an invoice or refund a charge. Our support team does their best to identify these situations in advance of a user ever being made aware. In the specific case of the user that posted about the large bill they received, we’ve been clear that while this was an incredibly rare situation, we should have done better. A bill this large should never have left our system automatically and our support teams should not have treated this as a business user. We also should not have speculated that this was a DDoS attack, since in this case the traffic does match organic traffic from a region with lots of old devices. While we do currently have notifications in place that make a user aware that extra bandwidth is being consumed, we do not currently have the ability for users to preset limits. We have assembled a team to immediately address this, and we will report back to the community ASAP when we have some more solid information to share around timing. When me and Chris started Netlify almost a decade ago, our primary goal was that any individual developer should be able to just build and use our platform for free. This is why our core monetization model is centered around helping large companies be successful, not billing individual developers. Since our inception, over millions of developers and thousands of open source projects have benefitted from our free offering; allowing anyone to build, deploy and launch their products to the world. We sincerely apologize that in the case of this user, we stumbled in the delivery of this promise.

Wow, 8 million developers on Netlify. If you're one of them, thank you. What’s something cool, fun, weird, creative or interesting you built recently?

AI will make the amount of software we build explode. At Netlify we just switched from Zoom to Google Meets. In general an improvement, except that in Meets you can't share audio from outside the tab you are screen sharing. This means no ability to play a Spotify song during the first few minutes of a townhall or large group meeting while showing the intro slides and messaging. Before AI, I would just have lived with it. Not now. I opened up Claude Code and gave it this prompt: "I want to create a chrome extension that lets me paste a spotify embed block (or similar embed block) and then injects an iframe into the current page with that embed positioned so it's always on top of any other elements and interactive. Make sure there's a little close icon to dismiss the iframe again (should remove the iframe from the DOM)" Now I have a Chrome Extension that lets me play Spotify from within any tab, and I've solved my problem. I've coded Chrome Extensions myself, but it's a long time ago, and I would not have had the time to read up on how they work, figuring out how to start one and do the setup, write UI code for drag'n drop stuff in JavaScript, etc, etc... This is software that would have never been made without AI, and we'll see so much more of this. What's also true is that had I not been an experienced developer, had I not known about the capabilities of Chrome Extensions to inject code into the current tab, or had I not known about iframe's and their ability to run external code safely within a tab, I would not have been able to write a prompt to solve this problem with or without AI. As @KentBeck said in a recent tweet: "The value of 90% of my skills just dropped to $0. The leverage for the remaining 10% went up 1000x."

Today it's exactly 10 years ago that we launched Netlify out of a private beta with a post on Hackernews. It's been an epic journey so far, with ups and downs and so many memories made along the way. Deep thanks to everyone that's been part of it. More in the thread below.

React and Remix v3 remind me of Rust and Golang. And similarly, a lot of the loudest voices discussing the two frameworks seems to be looking for "truth" rather than "tradeoffs". Go is less elegant than Rust, error handling is verbose, type system is not as advanced and more limited in the abstractions it can express. In many ways Rust is obviously more advanced, but for many use cases Go's very explicit choice to keep the level of abstraction very low and the code more imperative than functional has proven extremely useful for making it simple for normal engineers to build really robust production software with an easy onboarding from other languages onto Go, while Rust presents a much deeper learning curve and culturally sometime attract developers who prefers clever abstractions over simple solutions. There's not a right answer to "is Rust better than Go" and I'm really grateful that we have both options to choose from and that the two communities are exploring really different paths. In the current world of JS frameworks I've often wished for someone to take the super-pragmatic, low abstraction Golang approach and really stick to it and Remix v3 for now really seems to be the strongest contender to a viable framework with this approach. This is not "better" than React. There's not one "truth" about front-end development. It's a really different set of tradeoffs that I'm really glad to see a team of the Remix caliber explore. Now a lot will come down to the discipline of @mjackson, @ryanflorence and the core Remix team in resisting the allure of layers of abstractions on top of their core paradigm that I can already see potentially emerge in the community - in the same way that Rob Pike, Ken Thompson et all had to resist the push for complex generics, more abstract error handling, and similar levels of abstraction that would have changed the nature of the language.

Our async workloads implementation take the specific await step approach for an example of doing this without string based directives. docs.netlify.com/build/async…

Wow, 9 million developers on Netlify. We onboarded a million new developers the last 3 months. If you're on of them, thank you! What do you want us to ship next?

Netlify's docs are built with Starlight

Genuinely excited to partner with Astro on building a better web! There's such a clear alignment between the two teams in valuing openness and simplicity. astro.build/blog/netlify-off…

I want TanStack to be a strong independent open source ecosystem with lots of strong industry sponsors. Our strategy in general is to sponsor and partner with independent open source ecosystems that we think are good for the web.

We just rolled out full support for Stale While Revalidate and Targeted HTTP Cache Control to all customers. All seamlessly integrated with our automatic, instant cache purges. netlify.com/blog/swr-and-fin…

Took us 5 years to land the first million developers. Now 4 years later we crossed 5 million developers on our platform. Come celebrate with us at Netlify Compose! netlify.com/blog/celebrating…

Big news! Netlify has acquired Gatsby Inc. This is another exciting step toward our mission to make it easier for developers and organizations to build for the web with composable architectures! netlify.com/press/netlify-ac…

Since I've gotten several requests for a migration check list, here you go:

Five years ago I introduced the term Jamstack at SmashingConf in San Francisco, to describe the decoupled architecture of the modern web. Today in @smashingmag I look at how this architecture has evolved since then and whats in store for the future. smashingmagazine.com/2021/05…

At Netlify we’ve taken on the “Preferred deployment partner” sponsorships for both @astrodotbuild and @tan_stack over the last years, but today we’re genuinely excited to have @Cloudflare join us and drop any notion of preferred labels. Open source thrive when we can all invest together across the industry and across competitive barriers, and these projects will lift the whole open web if well funded. Hope more partners will join in and help grow the open web ecosystem.

Been playing around with React server components and put together a demo on Netlify. It's much more barebones than @sugarpirate_'s full demo, and I hope that it'll be a good starting point for others. Demo: react-server-components.netl… Source code: github.com/netlify/react-ser…

We're now Official Deployment Partner for @vite_js @astrodotbuild for Sites, @tan_stack for Apps, and Vite as the underlying toolchain.

Welcome on board Gatsby team!

Very excited about this partnership. @tannerlinsley has been one of the most prolific builders in the whole funny end space the last decade, and TanStack Start is the framework I would pick if I were to rebuild our dashboard from scratch tomorrow.

Here's the full React Server Components demo with Postgress on the backend running on Netlify. Comes with a one-click Deploy button to get you started: github.com/netlify/full-reac…

API Endpoint to stream from OpenAI in 18 lines of code. Just add the file in the netlify/functions dir and deploy. Just Web API's, works with any front-end framework, or even without one.

Big moment for us, bringing FeaturePeek on board and launching collaborative Deploy Previews today. Proud of what we can share with the world. This marks the next era for Netlify, bringing the Jamstack benefits to life in a new way for teams. netlify.com/blog/2021/05/19/…

brb, need to go confirm with the board that it's alright we keep shipping lots of stuff real fast!

Gatsby 1.0.0 is out - very exciting release! gatsbyjs.org/blog/gatsby-v1/

It’s been a long time since I’ve had an active personal blog. Given the way social networks seem to be breaking apart and the communities I typically interact with are scattering, it’s time to return to owning my own little corner of the web. biilmann.blog/articles/i-bui…

I just deployed a website from an airplane in flight. Cloud deploys for real!

Netlify.com is built with Astro. Seeing teams at Netlify choose Astro, being both happy and productive, made me very bullish on Astro. A strong reason to commit to this level of sponsorship. We're literally investing in one of the key tools we use to build Netlify.

I really like what I've seen of Remix 3 so far. In some ways less radical than what I had thought from the pre event signaling, but compared to all the complexity of useEffect, hooks, suspense, RSCs, etc, of modern React it was so refreshing to see something that felt very straight forward to understand end to end as @ryanflorence gradually built up the abstractions from pure DOM events and browser standards. Looking forward to play around with it.

Some dream of returning to PHP style full stack web development. Some of us have been there, done that and still have nightmares about it! SQL queries in my templates 😵‍💫

Over the last 3-4 years front-end architectures have gotten much more complex, without any real step change in what we're building. Let's make the web simpler again, so we can start spending our complexity budget on innovation again.

In the front-end community, there's a tendency to seek absolutes rather than balancing tradeoffs. Edge Rendering, for example, is powerful but not without its drawbacks. If you're building a full stack app on top of a database Edge Rendering is almost certainly an anti pattern for anything non-trivial. It's not cost efficient to replicate large databases across all edge regions. However, if you're building with a Jamstack approach on top of API's, then API caching + edge rendering can be a very powerful technique. Shopify's Hydrogen framework based on @remix_run is a great example of this. It's edge rendering on top of calls to Shopify's API which already have a good global edge caching layer, giving a good balance of very dynamic storefronts with low latency and a simple architecture to build with. Remix/Astro/Solid edge rendering on top of Netlify Connect is really exciting as well, since you'll get global edge caching for your GraphQL queries out of the box. One big tradeoff when running your app on the edge is more limited compute environments and more limited runtimes. We picked Deno as a runtime environment for Netlify Edge Functions for this reason. It strikes the best balance on the market right now between the security limits that makes it viable for edge environments, while providing a comprehensive JS runtime with good DX, standard libs and ecosystem.

Can't believe my baby's turning 10! If you're in SF in Monday, come celebrate with me in Netlify HQ: lu.ma/x1hgmp88?tk=E7p15g

Been excited about faster builds and installs with @bunjavascript? Now bun is available and supported for all Netlify Builds. netlify.com/blog/bun-support…

Want to play with the brand new React server components over the holidays? Here's a one click setup to get started: app.netlify.com/start/deploy… Demos mixing client and server side components, deployed to Netlify and runs locally with Netlify Dev. Enjoy!

Don't sleep on these types of posts from exceptional engineers like @zeeg or @schickling There's a big change happening in what it means to be a software developer. Writing code by hand it not going to be a big part of it. What follows is that reading code will also stop being a concern. There's no way the role for humans will be to sit and read through machine generated code all day. This change will have huge ripple effects across all of developer tooling, which is currently centered around code as our core IP and the core abstraction developers work at.

Big news: on-demand cache key variations with the new Netlify-Vary header. Want your cache key to understand a cookie value? Netlify-Vary: cookie=logged_in Want your cache key to respect pagination? Netlify-Vary: query=page|per_page netlify.com/blog/netlify-cac…

Sorry for all the tech trouble at @JamstackConf. We had an amazing setup for this, live studio at a house in SF with amazing peeps like @cassidoo and @jlengstorf ready to create a truly memorable experience. Then P&G lost power to the whole block. Now back streaming from London.

This particular case wasn't actually a DDoS issue, but a ~3.7mb mp3 file suddenly starting to get a lot of downloads over several days. Regardless of that, our systems should have handled this much better.

Gotta say @tannerlinsley's upcoming Tanstack Start is looking pretty incredible. Great presentation at Compose.

Found time for a weekend code project for once: Contributed a parallel runner to Gatsby which can heavily speed up some build steps. Currently seeing 4x+ performance increases for image processing. dev.to/biilmann/open-source-…

As CEO, do I tweet too little or code too much?! shiptalkers.dev/compare?name…

Incredibly excited to add a whole new dimension too Netlify. Have known and followed the team at Stackbit since day one and seen how much they have helped our shared customers. Together we can do even more.

Boom 🔥🔥 Unstorage support for Netlify Blobs unstorage.unjs.io/drivers/ne…

Excited to announce this! Huge thanks to the amazing community around us, to the passionate and empathic team that's making all of this happen, and to both new and old investors taking a big bet on us. It's humbling to be working with you all. netlify.com/blog/2018/10/09/…

New article in thread: agent experience (AX). Agents now interact with our products autonomously, build with our platforms and consume our content and experiences on the web and beyond. We all need to consider how to craft our product experiences specifically for AI agents.

AX, agent experience, is now a key aspect of all tools we ship. Six months after I coined Agent Experience I mapped the real-world patterns and wrote up why they matter. Deploy first, claim later: @boltdotnew launches a live Netlify site before you even log in. @supabase auth and @prisma data and @clerk play the same tune; the agent handles set-up so you start with real output, not a blank prompt. Agents should meet humans where the work lives: Tag a code agent in a @linear issue and a branch pops into the repo, zero context switch. Docs for transformers are not docs for people: Skip the essay. Instead, feed the model a tight context file (llms.txt, .agent.md, recipe endpoints) that lists routes, auth, and edge cases with absolute precision. Context decides the winners: Give your agents real context and the line between tool and teammate disappears. I break down the why, the how, and what’s next in the full essay on AX in Practice: biilmann.blog/articles/ax-in…

Musk is really proving @jack's point that we need an open protocol for social media. I've always tooted the horn for the Web as the one platform without an owner. Importance of that is more obvious than ever. Hanging out more on that other site where tooting is more of a thing..

Remix 3 on Netlify: remix-3-on.netlify.app/

Built and hosted on Netlify. Huge fan of Evan's work and bullish on the future of Vite and @voidzerodev

We just shipped Netlify Image CDN as another core platform primitive. Simple to use with any framework (or without a framework). Composes well with our Netlify Blobs or with any image that's part of your digital experience, from builds, blobs or a CMS.

Learn vibe coding. Then get curious, and learn why it works.

Honestly JavaScript would probably be a slightly better language without both const and let, and if const hadn't been there in the first place I doubt anyone would have missed it. What I don't get is why everybody seems to wanna act like "class" is not part of the language.

Impressed by the quality of @AmpCode. Closest I've felt to having an experienced developer available straight in my terminal. Credit card starts bleeding fast as well though. It's a bold move to really just go for best quality vs cost as differentiator.

1/16 Today we released an important update to On-demand Builders, Netlify’s platform level feature for supporting DPR netlify.com/blog/2021/10/25/… Here are some thoughts on our approach and how these principles can extend to things like HTTP streaming.

From all of us to all of you: a whole new adapter for @astrodotbuild! Re-built on top of all of our recent improvements to our core platform primitives. If you're as excited about Astro as we are, go give it a whirl over the holidays. Can't wait to see what you all build!

Bolt users now have everything at their fingertips to publish and manage production ready apps, agents and sites. 🔥🔥🔥

You all deployed a million sites from Bolt to Netlify! 🚀

Looking for a dev rel engineer in SF. Required: Passion for the open web. Ownership, potential, hustle and drive. Builder at heart. Shares our vision of the open web as a platform. Great community & content skills. Not required: dev rel experience. boards.greenhouse.io/netlify…

Netlify Compose is coming up in a week, and it’s going to be an amazing event. So proud of the program the team has pulled together. More below! netlify.com/compose/agenda/

I got the chance to meet Jensen Huang at Cloud 100 with a group of CEOs. One asked him "who do you admire?" His answer really resonated: Never admire people for their success or intelligence. Admire people for their character. Great character is the real scarcity. Well put.

Big launch! Excited to work with the team at @deno_land to set the standard for how an open source, edge runtime should play into the modern web architecture. Streaming rendering, programmable routing, edge auth, etc... Can't wait to see what our community will build with this!

Local-First, similar to Jamstack back in the day, sits in the space between an architecture and a movement, and will play a large part in the future rich web experiences. We're brining some of the best minds in the space together at Compose. Come hear from @kylemathews, @pvh, @jchris and @expede at for our Local-First panel. Excited to bring people together from a broad swath of the composable web ecosystem across dev tools, AI, frameworks, API's and practitioners. netlify.com/compose/agenda/#…

Jamstack won so much that it became less useful as a community term, since basically all modern web frameworks ended up being built around self standing front-ends talking to API's and services.

Interested in Partial Prerendering? I wrote a guide on how to do Partial Prerendering with plain HTML and no framework on Netlify. With the right platform primitives, it's simple to implement. developers.netlify.com/guide…

Back at @smashingconf SF at the Fort Mason 7 years later as the mystery speaker. Incredible to think through how far we've come since I first introduced the term Jamstack back then!

Lit is adopting @preactjs Signals: lit.dev/blog/2023-10-10-lit-… So much traction for Signal's as a primitive.

App deploys straight from Windsurf to Netlify with zero friction. This is why we're all in on AX. Agents will not just be writing the code, they'll be deploying, debugging and iterating as well. Excited to see what you all build!

🎉 Just wished @netlify a happy 10th birthday: "Happy birthday Netlify from your CEO and Co-founder :) Love this vibe coded site!" #NetlifyTurns10

So excited to have you onboard - surrounding ourself with people who're smarter than us keeps being one of the biggest joys for @Chr_Bach and me while building out @netlify!

So close to pushing the button!

My manifesto on the new generation of developers when code is no longer a gate letting function for feeling on the web. You are now a developer. netlify.com/blog/you-are-now…

People are consistently underestimating the actual benefits of a simple, static site when it comes to maintenance and security.

This is static HTML with Islands architecture for interactive components like search and shopping card. Not a template, real world, same core architecture since launch in 2017. The web platform is awesome.

I think it's actually much more the exception than the rule that the two patterns converge over time. For logged in dashboard style use cases (especially for professional tools), pure SPAs are very well suited and are simple to reason about.

Sorry to hear that. If it's been a while since you tried, a lot changed. We had a painful re-architecture of our approach to Next that landed last year and now have what's probably the largest test suite for Next JS functionality running nightly against our platform.

It's official: you can now Deploy via MCP! AX is the north star for our product at Netlify. Our new MCP server an important part of this strategy, making Netlify even better for agents to build and deploy on.

Congrats to Lovable! The worlds fastest growing business use Netlify.

1/2: Seeing major players like Cloudflare start down the Jamstack path is a testament to the movement. To truly disrupt the legacy web, the entire industry needs to be pointed in this direction.

Tools like Devin will make software development more affordable and accessible for small businesses and individuals. Just as site builders like Wix, Weebly, SquareSpace or Shopify did wonders to democratize custom websites or storefronts. In the 20 years since the first of these launched, the volume up web developers have grown by orders of magnitudes, far from being replaced by them! Ten years from now I believe there will be an order of magnitude more software developers than today. But just like a developer from 20 years ago would be a stranger to all of our modern front-end frameworks, SPA vs MPA discussions, hydration errors or tools like golang, wasm, rust or react, the toolset of a future developer will be radically different. This has been true for all the decades I've been developing software: the only constant is change. Be curious! Learn new tools, figure out how AI can help you do more or do things you could never do before, embrace the change and focus on how to be the best at building amazing things for other people - not at writing code in a specific language or framework.

Excited for @Netlify to partner with Wix on this. They have an extensive set of services used in production for millions of web sites, and are now making them available as headless APIs that developers can build great user experiences on top of.

Great to see more sponsors for Astro!

Huge congrats to @ThePracticalDev on their funding! They've built an awesome, welcoming and inclusive community. Excited for their next steps! dev.to/ben/announcement-from…

It's been amazing and we've built some awesome things together! Can't wait to see the next thing you build!

Tech check for @ViteConf See you all soon!

This is a really good article on evolving the SPA. I think will expect the experience of the web to feel more and more interactive and dynamic and starting with the client is a really powerful approachiof you're aiming to support that.

Excited to launch Netlify Connect! It enables companies to create web dev strategies, where they start their journey to web modernization, and unlock their ability to migrate from legacy to modern architectures in a modular and incremental approach. netlify.com/products/connect…

Asked Devin to do the job of every proper web developer and build me a Todo list app. Here's what Deving built and deployed to Netlify: snazzy-vacherin-45a697.netli… Love what @cognition_labs is building here, allowing AI models to participate in a modern development workflow.

Amazing launch. Congrats to the whole team!

I wrote a post on a simple approach to fast edge rendering with Netlify and @remix_run that works regardless of where your API servers live.

It's Friday and apparently Angular just got it's renaissance! Here's a brand new Angular runtime so you can go play with all the new ng17 goodness this weekend. Enjoy!