Use this path when the project builds into finished HTML, CSS, JavaScript and assets. Check the production build and its generated output before publishing.
Claude Code guide
Host a Claude Code website with a clear runtime.
Claude Code can create the project; its production requirements decide whether Host Luma publishes it as a static site or runs it as a supported managed Node web application.
Choose the path
Static output and managed Node are different releases.
Use this path only when the project has a non-empty npm start, listens on Host Luma’s supplied PORT and answers GET /health.
PHP, WordPress, customer databases, Docker, queues and arbitrary background workers need a different hosting model.
Claude Code is not a special Host Luma integration and does not make a project compatible by itself. Inspect the checked-in project rather than trusting a development preview.
Pre-flight check
Verify the actual project before connecting GitHub.
Use the directory containing the intended source, package configuration and Git remote, not a parent folder of experiments.
For static work, create and inspect the published files. For a Node web app, run the start command with a supplied port and verify its health route.
Never commit passwords, tokens or private keys. A browser-visible static configuration value is not a server-side secret.
Push the version you checked to GitHub so source, deployment history and a later redeployment remain connected.
Deploy and operate
Use the Portal as the record of the release.
Create the AI Hosting project, connect the intended GitHub repository and choose the deployment type that matches the project. Successful releases have an HTTPS preview URL; you can attach one custom domain per application with CDN delivery.
Read build logs for static releases and deployment/runtime logs for managed Node applications. Correct the source in GitHub and publish again. For a recorded successful Git commit, the Portal can queue a previous-version redeployment through the normal deployment path; it is not a snapshot, database or environment restore.
Generated code needs review
Do not use a static fix for a runtime requirement.
Next.js, Nuxt, SvelteKit and similar projects can be static in one configuration and server-driven in another. A server-driven project is only a fit where it satisfies the managed Node contract. If it needs a database, Docker, a worker or a different server runtime, do not repeatedly retry a deployment that cannot provide it.
After a successful release, test the preview URL, primary pages and integrations before sharing it. A custom domain is separate from the preview address and must be attached and verified in the Portal.