The builds that stick aren't one-shot generations.
They're the ones where you come back. Second run, third run, fourth. Same project, iterated in place.
Two weeks of netlify.new.
Read more: www.netlify.com/blog/start-a...
Genuine question: what's the thing that stalls your AI-assisted builds?
Not the generation. The part after. The "now what?" moment.
What's yours?
www.netlify.com/platform/sta...
What's next for Mattel? Leaning into AI to eliminate repetitive setup work, scaffolding, and common React patterns.
Already aligning with Netlify AI Gateway, Agent Runners, and Observability.
The infrastructure is stable. Now they build.
Read the full story: www.netlify.com/customers/ma...
74 Netlify sites supporting global presence. ~70 active projects across brands and internal services.
Zero emergency calls.
That last one is the one Mark actually cares about.
Serverless functions across 18 sites. Built-in build and edge capabilities.
Dynamic use cases handled without adding infrastructure overhead. Developers focused on React, not EC2.
Netlify wasn't a one-off adoption. It became the core digital platform.
Git + CI-driven deploys as the default. Teams moving faster without the multi-hurdle process of before.
The goal: consolidate into e-comm and non-e-comm stacks, and let full-stack developers actually own delivery.
Simple in theory. Hard when your infrastructure is fighting you.
Even basic fixes required sysadmin, cloud admin, network admin, AND DevOps.
Every. Single. Time.
That's not an ops problem. That's a platform problem.
Properties scattered across their own servers and multiple clouds.
Problems cropping up around the clock. No clean way to own any of it.
Barbie. Hot Wheels. Fisher-Price. American Girl.
That's just four. Mattel had 500+ digital properties to manage, and their stack wasn't built for that kind of scale.
500+ digital properties. Issues day and night. Every fix pulling in sysadmin, cloud admin, network admin, and DevOps.
Mattel called it "death by a thousand cuts."
Here's how they got out. 🧵
Most AI builders: incredible demo, inevitable migration.
The migration is the real product decision. It's just disguised as a starting experience.
Netlify skipped that part. Production infra from prompt one.
www.netlify.com/blog/start-a...
Two things slow AI building down: not knowing which primitives to use, and prompts that don't account for them.
Skills tell agents how to use Netlify correctly. Prompt Templates combine them into ready-to-use starting points.
Both available from your first prompt.
www.netlify.com/blog/better-...
The best product improvements aren't features. They're problems that just aren't there.
Netlify's AI Gateway: one endpoint, three providers, zero CORS fights. Already configured from your first prompt.
ntl.fyi/40XC1X0
Two weeks of building from a prompt on Netlify.
If you haven't tried it: type what you want, pick your agent, live URL in minutes.
Same infra from prompt one to production.
ntl.fyi/40XC1X0
One year of AX. And it's only gotten more real.
If agents can't use your product efficiently, you're invisible to a growing part of the ecosystem.
@biilmann.blog breaks down the four pillars: Access, Context, Tools, and Orchestration.
biilmann.blog/articles/one...
Built something with agent runners on Netlify?
We want to hear about it: what you started with, what changed on run two, what surprised you.
Our Creator Program is open: blog posts, videos, editorial support, author credit, swag, and 3 months of Pro.
www.netlify.com/creator-prog...
If you're building software, you have to be a constant learner.
Getting your peers and bosses excited about AI isn't about forcing it—it's about tapping into the innate curiosity we all share. Drop the old baggage. Take the spark and grow a fire.
How do you build a culture of true autonomy? Slow down and inform.
Your team should feel empowered enough to run on their own. Leadership should only need to step in as a tie-breaker for those 50/50 split decisions.
Build the culture, don't cut corners.
After years of working in silos, in 2024 @netlify.com, @cloudflare.social, OpenNext, Google @firebase.com, and the @nextjs.org team at @vercel.com built bridges.
We started discussing how to truly solve for full portability of Next.js. And we kept at it.
Today marks a culmination of this work.
The Next.js Adapter API is now stable.
That’s a big step toward running @nextjs.org across platforms. However, there's still work ahead and that's why we're forming the Ecosystem Working Group.
@philippeserhal.com shares what’s next:
www.netlify.com/blog/the-nex...
Most AI builders are great at the start.
Then the project gets real: users, APIs, access controls. And the platform runs out of runway.
Netlify enters the same starting moment without the ceiling. Same infra from prompt one to production scale.
www.netlify.com/blog/start-a...
CascadiaJS Web + AI Conference. Keynote speaker. Matt Biilmann. CEO - Netlify. June 1 - 2, 2026. Seattle, WA.
We couldn't be more excited to welcome @biilmann.blog, the founder and CEO of @netlify.com, to join us as a keynote speaker this year. Building for the web has never changed this fast and we're excited to hear his thoughts on how we can all keep up & thrive.
cascadiajs.com/2026
Who is adopting AI faster? Engineers or business teams?
We found that devs are naturally skeptical—when you've been taught to protect production at all costs, you don't let agents run wild.
Business users? They're bringing "YOLO" back and using AI for everything.
youtube.com/shorts/_MMeY...
In my past life where I developed e-commerce software from the ground up I would have *loved* to have Hydrogen. It has everything you need built in, with great DX without magic. It's really just React Router 7 framework mode with a bunch of utilities tailored to a Shopify storefront.
Give it a try.
Netlify now supports Shopify's Hydrogen on React Router 7.
Our Hydrogen template has been rebuilt with the Netlify Cache API for low-latency data fetching and the Netlify Vite Plugin for full Netlify power locally.
Read more in our changelog!
www.netlify.com/changelog/20...
You don't have to use Git to start a Netlify project.
No repo to initialize. No commit before you know if the idea is worth it.
Build first. Add Git when the project needs it, not before.
t.co/bILLory0sw
The gatekeeping of software development has lowered. What matters now? Taste and brains.
Shipping is important, but you can't build with blinders on. We have to share, iterate, and advance together.
That’s why community is everything. 👇
youtube.com/shorts/99bGS...
