Netlify.new - Start a project with just a prompt on Netlify
by•
Start a project on Netlify with just a prompt—no repo or local setup needed! Describe your app, pick an AI agent (Claude, Gemini, or Codex), and get a working, live production URL immediately. Iterate in place on real Netlify infrastructure with built-in forms and serverless functions. Traditional methods still work, but now you can go from prompt to real product instantly, without migrating later. Git is there when you're ready.
Fastest way to try it: netlify.new
Replies
Hey Product Hunt! 👋
I'm KP from the team at Netlify.
We kept seeing the same gap: AI tools are incredible at generating code, but there's still a wall between "here's your code" and "here's your live product."
You generate something, then you're on your own to host it, wire up auth, configure builds, and figure out deployment. That's where momentum dies.
So we built netlify.new.
Go there, describe what you want, pick your AI agent (Claude, Gemini, or Codex), and you get a working app deployed to a live URL — not a preview, not a sandbox, a real production site on Netlify.
The part we're most excited about is what happens next.
You don't start over when you want to change something. You run the agent again and iterate on the same app.
Add a contact form, swap the layout, wire up authentication — it all happens in place. No regenerating, no migrating, no re-platforming.
We designed this for the prompt-first builders who want to ship real things fast — but also for the developers who want to invite their designer or PM to spin up an internal tool without handing them a CLI.
Try it at netlify.new and let us know what you build.
We're especially curious: what's the first thing you'd prompt?
@thisiskp_ Many congratulations on the launch, KP and team. :)
Is this suitable for complex applications too? Example, an app already has a database, authentication, or existing users, what happens when the agent modifies schemas, logic, or integrations? Is there versioning, migration handling or rollback built into the workflow?
@thisiskp_ @rohanrecommends Yes totally! this all sits on top of Netlify's platform which has atomic deploys, CI CD setups, etc.
@rohanrecommends oh yes! you can take it as far as you wish to. In fact a lot of our Netlify new projects are all built with this same infra.
@rohanrecommends It is built with full stack web apps in mind. You can work with your agent of choice (Claude Code, Codex, Gemini) through Agent Runners to get some of this set up with a couple of manual steps to set up environment variables, etc, but we are working on making parts of that set up easier. More coming soon here!
With what we've launched this week, it is more for new sites and apps, but you can still import existing projects with our git integrations or Netlify Drop. With using some of the Netlify platform features, you won't need to use external services for things like identity, Image CDN, forms, blob storage, and more since using the agent will set those up for you but you can still state your preferences.
And versioning and rollback is all built-in using the existing support for this that Netlify has had for years. https://docs.netlify.com/deploy/manage-deploys/manage-deploys-overview/#rollbacks
@thisiskp_ having been a Netlify customer who loves how simple and easy the hosting has been this is a huge unlock to now being able to start all my projects on Netlify - plus being able to choose from the most powerful AI models all in one place.
Going to be building on the Netlify platform even more now and it's for sure in my vibe coding stack.
Watched the Community Drop yesterday and it's so cool to see how it came together! Congrats to the entire team for all the efforts in building and launching this new feature! 🚀
@ashamplifies thanks a lot Ash - appreciate you joining the Community Drop too :)
@thisiskp_ Really like the framing here. The "wall between code and live product" is exactly where most AI coding tools drop the ball.
Curious how you'd position this vs Google AI Studio or v0 for someone evaluating all three. The way I see it: AI Studio is more of a model playground, v0 is great for component-level UI generation but you still need to wire everything up yourself. netlify.new seems to be going after the full deployment loop, which is a different bet entirely.
Is that the right read? And for teams already on Vercel or on a custom CI/CD setup, is there a migration path or is this more of a greenfield tool for now?
@thisiskp_ @federicobgt the only migration needed is deploying your project to Netlify. If you link your github repo and we can build it, you can also start using Agent Runners on it. That was actually the only path to using Agent Runners when they launched back in October.
Now you can also go the other way, start from Agent Runners and then push to a fresh git repo and tap into the traditional CI/CD workflow.
And yes, it's a full part of our workflow and deployment layer. In many way Agents start playing the role of the CI/CD loop.
@thejeremyredman howdy JRED! Thanks for the love
How many AI-generated apps have you had to rebuild once they needed real infrastructure? Netlify now lets you start from a prompt and deploy directly to production - so the thing you prototype is the thing you scale.
The curated prompt templates for common Netlify workflows - like accessibility audits and A/B testing with Edge Functions - are super useful. Pick a template, hand it to your agent in Netlify, and keep iterating. Couldn't be more excited about this launch! 🎉
@hughbeme getting to build from 0 on production-grade deployment environment is just epic.
Also, it would be impossible at the rate at which we build our internal apps without this feature. Thanks for all that you do in leading from the front in building :)
What I really liked is that you can run the agent again on the same app. Most tools make you start from scratch every time. You let people keep building. That feels real.
Anyway, just wanted to say this is cool. Hope it goes well, @thisiskp_!
@taimur_haider1 Well said, thanks man!
@thisiskp_ Appreciate man. Keep building cool products!
The prompt-to-deploy flow is something I keep wanting to work seamlessly. Been building a few small tools recently where the bottleneck is actually the setup - getting env vars, build config, and domain wired up correctly takes longer than writing the code. Does netlify.new handle that config layer from the prompt, or is the prompt mostly for the app code and you still do infra setup manually after?
@mykola_kondratiuk It's pretty compatible with being able to handle most config changes from prompts. We will be added a special flow for env vars to keep them isolated and there are things we are going to do to ensure the permissions work well. We also support things working as config in code in addition to in the UI, lots of options and lots of improvements coming!
Finally! Watching the team work on it and using the early versions I couldn't wait anymore for the final one. Such an awesome addition to the platform
@youvalv Thanks to you and the team for all the hard work on bringing this to life! We know it's only going to get better from here :)
Netlify has always been the place you bring your project after you've built it and you were ready to host it on the best infra with the best DX. Now you can also create new projects on Netlify and it's already set up on the best infra, ready for iteration. Prototypes, internal tools, and iterating on real world sites, this is amazing!!
Also don't forget you can have your full team on Netlify with roles that allow granular access to only the areas that your team agrees on. True full team empowerment and governance.
@developsean thanks Sean! all I want to say is I’m specifically grateful you led the team to bring this to life so thousands (millions?) of vibe coders and internal builders can go 0-1 on their ideas easily.
Can you bring your own context or instructions to the agent, or does it start fresh each time? For anything beyond a landing page the agent needs project context to make good decisions, and that's where most of these tools break down. Building Ritemark app - context and instructions are piling up as fast as code.
@jarmo_tuisk2 Right now we have per project context that you can save after the project is created, but it is an interesting idea to think about it for every new project the whole team. For now, you'll want to make sure to include it in the initial prompt.
This is awesome! Congratulation. Netlify rocks!
@zeng Thanks a lot Zeng. You rock!
We've hosted multiple projects on Netlify and it's consistently been one of the easiest parts of our stack. The ability to prototype with AI and immediately deploy on the same platform is a really interesting direction. Curious to see how much it speeds up early development. Congrats on the launch!
Is the goal to start with Netlify and then export to the IDE for further complex work or is the goal that I should be able to stay within Netlify throughout my whole development process?
@lienchueh we give you the full set of options.
Internally we've built complex projects entirely with Agent Runners, but our main app is a 10 year old React app linked to GitHub with an existing workflow around it. There we still use Agent Runners to build some features while other work is done outside of Netlify and pushed via GitHub.
When you've started a project from Agent Runners you can always push it to a new git repo and start using any other toolchain in addition to Agent Runners.