Qanvas helps you build a Next.js marketing site by conversation, export plain App Router code.
I built Qanvas for freelancers and small agencies who ship Next.js marketing sites for clients. It's a local app: you describe the site, an AI with your project's context (routes, content, assets, design tokens) builds and refines it with you, and a visual inspector handles quick layout, spacing and token tweaks without spending AI calls.
After a final decision to step into software creation full time, I want to rebuild some of my old sites. I did not want to have mess of porting components, and later die trying to maintain them. Anyway, all my sites more or less have the same base. I don't want anything manual, I don't want to get stuck in a SaaS web builder. So I made my own. I am not a fan of AI taking over art, but as far as coding goes, I have no issue with that. So I want AI to do the heavy lifting in coding while I focus on designing the product the way I want. Yet again, I need AI to do my bidding, than I have to do its bidding.
So what's special about Qanvas:
Runs on your own localhost. The full repo of the websites you create is 100% yours to deploy wherever you want.
You use your choice of Bring-Your-Own-Key AI agent (Google, Anthropic or OpenAI). Create an API key and use it safely for Qanvas. You pay your AI provider, not Qanvas.
Qanvas is not a subscription. Non-throttled full features for one project for free. One time lifetime fee of $99 only if you want unlimited projects.
Get started now: `npx getqanvas --start` (Node 22+). No account needed.
[https://getqanvas.com](https://getqanvas.com) (I built my site with Qanvas)
I'd like to know, for those who've used AI coding agents for landing pages, where did it go wrong for you? Does it matter to you that you directly integrate your AI agent of choice (and not using mine)? Do you like the idea of a fully exported Next.js repo that you can then deploy where you see fit, and thus you are not locked in to a SaaS platform?