Choose Static site when the repository produces finished HTML, CSS, JavaScript, images and other browser assets. Typical projects include plain HTML and supported frontend builds.
Documentation · Getting started
Deploy your first GitHub project.
Host Luma deploys supported projects from GitHub. First establish whether yours is a static site or a supported managed Node 22 web application, then use the matching Portal workflow.
Choose the correct release
Start with the project’s production contract.
Choose Node.js application only for a supported HTTP app with a non-empty npm start, Host Luma’s supplied PORT and GET /health.
PHP, WordPress, customer databases, Docker, queues and arbitrary background workers are not supplied by AI Hosting.
The framework name is not the answer. A project can be static in one configuration and server-driven in another. Check the output or runtime behaviour that visitors will receive.
Before you begin
Prepare one reproducible source of truth.
Confirm the intended repository, branch and application folder. Do not deploy an untested parent directory or a local experiment.
Build and inspect static output, or run the Node HTTP app with a supplied port and test its health endpoint.
Keep credentials and private keys out of Git. Identify external forms, APIs and data services; AI Hosting does not provide them simply because a frontend uses them.
Push the tested source so GitHub, the Portal release and later investigation all refer to the same version.
Deploy
Create the project, connect GitHub and select the path.
In the Portal, create the AI Hosting project, connect the GitHub repository and select Static site or Node.js application to match the tested project. A static release runs the relevant build and publishes its finished output. A supported Node release uses its configured start command, supplied port and health check through the managed lifecycle.
Successful deployments receive an HTTPS hostluma.app preview URL. Open it, test primary pages and integrations, and read the release information in the Portal rather than changing server paths or uploading files manually.
Domains and delivery
Preview first; attach a domain deliberately.
Each application has a preview URL with HTTPS. One custom domain per application can be attached and verified in the Portal, with CDN delivery and certificate handling included. A working preview URL is not proof that a custom domain is already attached.
Use the provided domain state and instructions. Do not promise a customer launch until the selected domain is attached, verified and live.
Logs, restart and redeployment
Use the service record to make the next change.
Static deployments produce build and deployment information. Managed Node applications also expose runtime logs and restart controls through the Portal. Start with the first relevant failure or health message, reproduce it locally where sensible, make one focused GitHub correction and publish again.
For a recorded successful Git commit, the Portal can queue a previous-version redeployment through the normal deployment path. This is not an instant rollback or restoration of a snapshot, database or environment.