How to Deploy a Claude Code Website on EZLaunch
Claude Code works in your terminal and writes files straight to your disk, which makes it the easiest AI tool to deploy from. Ask it for a plain HTML, CSS, and JavaScript site, run ezlaunch deploy in that folder, and you are live. No build step, no export, no ZIP unless you want one. This guide covers the prompt that keeps things static, the deploy command, and what to do if Claude built a framework project instead.
Start with the right prompt
Claude Code will build whatever you describe, including full React or Next.js apps. For a website that should be cheap, fast, and hosted anywhere, ask for static files explicitly. A prompt that works well:
Build a static website using only HTML, CSS, and vanilla JavaScript. Put index.html at the project root with css/ and js/ folders next to it. No frameworks, no build step, no server. Make it responsive and include a contact form with data-ezlaunch name="contact" on the form tag.Because Claude Code edits real files, when it finishes you already have the deployable folder on disk. Open index.html in a browser to check it.
Deploy with the EZLaunch CLI
Install the CLI once, log in once, then deploy from the project folder whenever you want the live site updated:
npm install -g ezlaunch
ezlaunch login
cd my-site
ezlaunch deployThe command uploads the current folder and prints the live URL on ezlaunch.app. Run it again after every change; each deploy replaces the previous one with no downtime. You can even ask Claude Code to run it for you at the end of a session.
Prefer the dashboard? Zip the contents of the folder (index.html at the top level of the ZIP) and drag it onto New site at app.ezlaunch.app.
Keep dev files out of the deploy
Deploy only what the browser needs. If your folder also contains node_modules, .git, .env, or a CLAUDE.md, either deploy from a clean output folder or ask Claude Code to "create a public folder containing only the files needed to serve the site" and deploy from there. Never upload a .env file; EZLaunch serves every file it receives.
If Claude built a Vite, Astro, or Next.js project
You will see a package.json and a src folder. Run npm install && npm run build, then deploy the output folder (dist for Vite and Astro, out for Next.js with output: 'export'). For React apps with client-side routing, use HashRouter or per-page HTML files, because EZLaunch returns 404 for paths that do not match a file. Or simply ask Claude Code to "convert this to a static HTML site with one HTML file per page" and skip the build for good.
Custom domain, forms, analytics
Domain: Settings → Custom Domain, add an A record to 87.99.143.176, click Check DNS; SSL is issued in about two minutes.
Forms: the data-ezlaunch name="contact" attribute from the prompt above is all it takes. Submissions appear in the dashboard on paid plans, with honeypot spam protection built in.
Analytics: on by default for every site, no script to add.
A workflow that scales
Keep the site in a Git repository, let Claude Code make changes on a branch, review the diff, merge, and run ezlaunch deploy. For client work, one EZLaunch account can hold many sites, each on its own domain, all deployed the same way. The prompt library has more prompts for landing pages, SEO passes, and forms that fit this workflow.
Common questions
Do I need a build step?
Not if you asked for plain HTML. That is the point of the prompt above.
Can Claude Code run the deploy itself?
Yes. Once the CLI is installed and logged in, tell it "run ezlaunch deploy" and approve the command.
What about environment variables or secrets?
A static site has none. Anything in the files is public. Put secrets behind a separate API, never in the deployed folder.
More deploy guides
Overview of every option: Deploying sites built by ChatGPT, Claude, Bolt, Lovable, and Replit.
EZLaunch is a product I build. Menu names and features in Claude Code change; check its documentation for current specifics.