Guide
Static Site Hosting — Publish a Website Straight From Your AI Agent
OpenClaw Launch can serve a static website straight out of your instance's workspace. Tell your bot what to build, it writes the HTML, CSS, and JS into a site folder, you flip on hosting from the dashboard, and the page goes live on its own HTTPS subdomain — no Vercel account, no deploy config, no domain to buy.
What It Is
Static Site Hosting turns a folder inside your OpenClaw instance into a public website. Your AI agent (or you, directly) writes plain files — index.html, a stylesheet, a script, images — into a site folder in the instance's workspace. Once hosting is enabled for that folder, OpenClaw Launch serves those files over HTTPS on a subdomain of openclawlaunch.app. There is no build step and no server-side code — it is exactly the kind of hosting a landing page, a portfolio, or a docs site needs.
It is a feature of an existing OpenClaw instance, not a separate product. If you already have a bot running, you already have a place to host a site — you just need to point it at a folder and turn hosting on.
How It Works
Files Live in a Site Folder in the Workspace
Each site maps to its own folder under the instance workspace, for example workspace/sites/{name}/. Anything your agent (or you) writes there — HTML, CSS, client-side JS, images, a favicon — becomes part of the site. There is no separate upload step; the files your agent already wrote are the site.
You Enable Hosting From the Dashboard
From the Website page on your dashboard, you create a site by picking a name and choosing which instance it belongs to. That name becomes the subdomain. Creating the site is what turns hosting on for that folder — there is no separate publish button once it exists.
Served on HTTPS at Your Own Subdomain
Once enabled, the site is reachable at {name}.openclawlaunch.app over HTTPS, typically within moments of the files landing in the folder. You don't manage certificates, a CDN, or a web server config — that part is handled for you.
Let Your Bot Build and Publish the Site
The point of this feature is that you don't write the HTML yourself. Chat with your bot the same way you would about anything else — "build me a portfolio site with my resume and three projects, and deploy it to my-portfolio" — and it writes the files straight into the site folder. As soon as the files are there and the site is enabled, it's live. If your bot seems unsure what you mean, tell it directly to use the website skill — that nudges it toward the right folder and workflow.
Because your agent already has a real terminal and file access inside its own container, it can iterate on the site the same way a developer would: edit a file, you refresh the page, ask for another change. There's no separate deploy pipeline to wait on.
Custom Domain
The openclawlaunch.app subdomain works out of the box with no setup, but you can also point your own domain at a site once it exists. See the custom domain guide for how to attach one.
What It's Good For
- Landing pages — a product or project page you want live in minutes, not a deploy pipeline.
- Docs sites — plain HTML documentation your agent can keep updating as your project changes.
- Portfolios — a personal site with your resume and project links, built and maintained by your bot.
- Project sites — anything your AI agent builds for you and you want to hand someone a link to, without setting up hosting separately.
How to Enable It
- Open the Website page — From your OpenClaw Launch dashboard, go to the Website section.
- Create a site — Pick a name (this becomes your subdomain) and choose which running instance it belongs to.
- Tell your bot what to build — Ask it to build the page and write it into the site's folder in the workspace.
- Visit your site — Once the files are in place, the site is live at your subdomain over HTTPS. Use the dashboard to copy the link, visit it, or delete the site later.
A free trial is available if you want to try this before subscribing — see pricing for plan details.
Static Site Hosting vs Netlify, Vercel, and GitHub Pages
| OpenClaw Launch | Netlify / Vercel | GitHub Pages | |
|---|---|---|---|
| Who builds the site | Your AI agent writes the files for you | You write and push the code | You write and push the code |
| Setup | Create a site in the dashboard, no repo needed | Connect a git repo, configure a build | Push to a repo, configure Pages |
| Where content lives | Your instance's workspace folder | A git repository | A git repository |
| Account needed | Just your OpenClaw Launch account | Separate Netlify/Vercel account | GitHub account |
| HTTPS subdomain | Included automatically | Included automatically | Included automatically |
| Custom domain | Supported | Supported | Supported |
Netlify, Vercel, and GitHub Pages are great when you are already comfortable with git and want a dedicated hosting workflow. Static Site Hosting on OpenClaw Launch wins when you would rather describe the site to your AI agent and have it write and publish the files for you, without opening a separate hosting account.
Related Guides
- Custom Domain — point your own domain at a hosted site
- Coding Workspace Hosting — a hosted cloud dev box for AI coding CLIs
- What is OpenClaw? — the AI agent framework behind your instance
- OpenClaw Launch hosting plans — pricing and feature details
- Pricing — plans and free trial
Frequently Asked Questions
Do I need to know how to code to publish a site this way?
No. The point of Static Site Hosting is that your AI agent can write the HTML, CSS, and JS for you — you describe what you want in chat, and it writes the files into the site's folder. You can still edit files yourself if you want to, but it isn't required.
What kind of site can I host this way?
Static files only — HTML, CSS, client-side JavaScript, and assets like images. It's a great fit for landing pages, documentation, portfolios, and other project sites that don't need server-side code running behind them.
Where do the site files actually live?
Inside your OpenClaw instance's workspace, in a folder dedicated to that site. Your agent writes there directly, and enabling hosting for the site is what makes that folder's contents public.
Do I get an HTTPS URL automatically?
Yes. Once a site is created, it is served on its own subdomain of openclawlaunch.app over HTTPS — you don't configure certificates or a web server yourself. You can also attach your own custom domain to a site.
Can I try this before subscribing?
A free trial is available on OpenClaw Launch, so you can deploy an instance, ask your bot to build a site, and see it published before committing to a plan. See pricing for plan details.