Use a static deployment when the project’s production build creates finished browser files and does not require your own HTTP process.
Codex guide
Host a Codex website without guessing the runtime.
Codex can generate a website or application; the checked-in production contract decides the Host Luma deployment path.
Know the boundary
Generated code is not automatically a static website.
A supported Node web application must deploy from GitHub, provide npm start, use the supplied PORT and expose GET /health.
Host Luma AI Hosting does not provide PHP, customer databases, Docker, queues or arbitrary background workers.
Codex is an authoring tool, not a Host Luma runtime integration. Read the generated project and test normal production behaviour before selecting static or Node deployment.
Before publishing
Turn the generated project into a reviewable release.
Confirm the correct package configuration, source and Git remote. Remove experiments and never commit secrets.
Build static output, or test the HTTP application with a supplied port and health route. A local development server is not enough evidence.
Commit the verified source that you want Host Luma to deploy.
Use deployment and runtime logs, then make one focused GitHub correction when a deployment needs attention.
Release controls
Preview, domains, logs and previous versions.
A successful deployment has an HTTPS preview URL. Attach and verify one custom domain per application in the Portal for CDN delivery. The preview URL is useful for testing but does not itself attach a domain.
For a previous successful Git commit, the Portal can queue a new deployment through the regular deployment flow. It is previous-version redeployment, not an instant rollback or restoration of a database, environment or snapshot.
Keep responsibility clear
Use a different platform where the project needs one.
If Codex generated server-side rendering, an API backed by a database, a Docker container or persistent worker, do not describe that architecture as supported simply because it uses JavaScript. The managed Node path is deliberately limited to the documented HTTP application contract.
For WordPress, use Host Luma Managed WordPress Hosting. For all other product fit questions, start with the framework compatibility reference.