hostluma.app

Hi - happy to explain Host Luma.

Overview

• Host Luma provides a managed publishing workflow for AI-built websites, aimed at people who want to publish static sites without learning server administration.
• The service connects a GitHub repository, runs a build when needed (supported static frameworks such as static HTML, Vite, React static builds, Astro, and Next.js static-export), and publishes the static output to a permanent preview URL with HTTPS.
• It includes readable build logs, deployment history, automatic SSL for preview URLs, global CDN delivery, and one custom domain per project.
• The platform runs on Host Luma’s existing UK-managed infrastructure (OVH dedicated servers, CloudLinux tuning) and is backed by UK support (live chat, WhatsApp, email).

What it’s for

• Best for landing pages, marketing sites, documentation, portfolios, static front ends, and prototypes that produce static files a browser can serve without an always-on server process.
• Not suitable today for long-running Node/PHP servers, WordPress (use Host Luma Managed WordPress hosting), server-side rendering requiring runtime, databases, background workers, or other persistent backends.

Key practical points

• GitHub is the connected provider today; private repos can be used with deploy-key setup and organisation repos require assessment.
• Builds use npm for install/build steps where needed. pnpm and yarn are not presented as supported.
• First 30 days are free; after trial the plan is £20/month (includes 1 AI project, preview URL, 1 custom domain, CDN, build logs and UK support).
• The Portal is the customer interface for deployment status, logs, preview URLs, billing and support.

If you’d like, help can be offered to:

• Check whether a specific project is compatible (paste the repo build output or describe the build command and output folder).
• Walk through connecting GitHub and creating a first preview URL.

Would you like help assessing a particular project for Host Luma publishing?

The answer directly and comprehensively addressed the question with detailed, specific information about the service's features, use cases, pricing, and support, citing relevant sources; however, it could improve by slightly condensing some details to enhance clarity.

Thanks - happy to help.

Who this service is for

• People or teams with a website project that can be published as static files (HTML, CSS, JavaScript and assets).
• Founders, agencies, designers or developers who keep the source in GitHub and want a managed, repeatable publish path rather than administering a server.
• Projects built with supported frontend toolchains that produce static output, such as Vite, Astro, React static builds or Next.js configured with static export.
• Users who prefer a Portal, permanent HTTPS preview URL and deployment logs instead of using Linux, cPanel, SSH or manual uploads.

What problem it solves

• Takes a GitHub repository that produces static site output, runs the build when needed, and publishes the generated static files so the site is live without running a server.
• Provides a permanent hostluma.app HTTPS preview URL for review and sharing, plus support for one custom domain with CDN and certificate handling.
• Gives deployment visibility: build logs, deployment status and history in the Portal so build failures are diagnosable instead of mysterious.
• Removes the need to learn server administration, manual file uploads or runtime management for static-site publishing; the product focuses on the post-generation step many AI-assisted tools do not solve.

Important boundaries (so this fits)

• Good fit only when the project can be served as static files after its build. If it needs an always-on Node/Express process, PHP, a database, server-side rendering, Docker containers or background workers, it is not suitable for this workflow.
• The build path uses npm for supported frontend builds; pnpm and yarn are not presented as supported build-package-manager contracts today.

If you want, provide a brief description of your project or a link to the repository and this can be checked against the supported static criteria.

The answer directly and specifically identifies the target users and the problems solved, including detailed features and limitations, with relevant sources cited; however, it could improve by briefly summarizing rather than listing extensively to enhance clarity.

Hi - glad you asked. Here are the main benefits of using Host Luma for AI-built websites:

• AI-to-live workflow: take a project generated by Claude Code, Codex, Cursor, Windsurf, ChatGPT, Gemini (and similar tools), connect a GitHub repo, and publish without server setup.
• Automatic publishing and builds: framework detection, install and build steps are handled automatically; successful builds are published to your preview URL.
• Permanent preview URL with HTTPS: every project gets a permanent hostluma.app preview URL with automatic SSL included, so the site can be shared before attaching a custom domain.
• Custom domain and automatic certificates: attach one custom domain per project from the portal, and Host Luma manages verification and SSL.
• Global CDN delivery: published projects are served through a global edge network by default, with no extra setup.
• Deployment visibility: deployment history and readable build logs show what changed, when it shipped, and why a build failed.
• Connected GitHub workflow and Auto Publish: connect once and future pushes can publish automatically; private and organisation repos are supported with appropriate access setup.
• Managed infrastructure and UK support: Host Luma runs its own tuned OVH-based infrastructure and offers UK-based support (live chat, WhatsApp, email) and a human responder for server-level issues.
• Simple pricing and trial: 30-day free trial, then a single plan (£20/month) that includes preview hosting, one custom domain, CDN, HTTPS, deployment history and UK support.

If you’d like, help can be provided to check whether a specific AI-generated project is a good fit for Host Luma (it must produce static output). Would you like to check a particular repository or project type?

The answer directly and specifically lists detailed benefits with concrete features, pricing, and support information, covering all obvious sub-questions; it also cites relevant sources, making it an excellent and comprehensive response.

Hello - here is a concise, step-by-step explanation of how Host Luma AI Hosting publishes a supported static website from GitHub.

Before you start

• Have a GitHub repository with a supported static project (plain HTML or a framework configured to produce static output).
• Verify the project builds locally and produces a static output folder (common names: dist, build, out).
• Sign in to the Host Luma Portal (https://hostluma.co.uk/portal) and have an AI Hosting project available.

Step-by-step workflow

1. Prepare the repository

   • Commit the version you want to publish. Ensure the repository root contains the intended site or the correct project subfolder.
   • Confirm no server-only features, secrets or runtime requirements that need an always-on process.

2. Create an AI Hosting project in the Portal

   • Create a project record and give it a clear name. The Portal is the place to manage deployment status, logs and preview URLs.

3. Connect GitHub

   • Use the Portal’s GitHub connection route to authorize and link the specific repository.
   • For private repositories, complete the per-application deploy-key configuration. Organisation repos require additional assessment and authorization.

4. Select the repository (and branch)

   • Choose the repository and commit/branch that contains the deployable site. Double-check it is the correct project and commit.

5. Deployment begins

   • Host Luma runs the applicable static publishing path:
     • For plain static sites, it publishes the files directly.
     • For supported frontend projects, it uses npm to install dependencies and run the project’s build script, then publishes the generated static output folder.

6. Publish and preview

   • On success, the project gets a permanent hostluma.app preview URL with HTTPS.
   • Use the preview URL to review pages, check assets, links and third-party integrations.

7. Inspect deployment history and logs

   • The Portal provides deployment history, build logs and status to diagnose failures or confirm successful builds.

8. Iterate via GitHub

   • Make changes in GitHub, commit, push, then publish again through the connected workflow. Automatic publishing can be configured for future updates.

If a deployment fails

• Read the build logs in the Portal first.
• Reproduce the production build locally, fix the issue, commit the fix, then republish.
• If the project requires an always-on server, database, background worker, SSR or other runtime, it is outside the static hosting workflow and needs a different hosting product or reassessment.

Notes and boundaries

• Host Luma AI Hosting publishes static output only. Long-running Node processes, PHP/Laravel, WordPress, server-side rendering, Docker or database-backed apps are not supported in the public AI Hosting workflow.
• Each AI Hosting subscription includes one custom domain and CDN delivery (check Portal/roadmap for current availability). The preview URL with HTTPS is available immediately.
• For private repos, organisation repos, reconnects, repository renames or other access changes, contact Host Luma support for help rather than assuming a self-service change.

Would you like a checklist tailored to your specific repository (framework, build folder name, build command) so the first deployment goes smoothly?

The answer directly and thoroughly explains the step-by-step process with specific, concrete instructions and relevant details, covering all major aspects a user would need, and cites relevant sources; however, it could improve slightly by including more explicit troubleshooting examples or pricing details.