01The gap this fills
ChatGPT, Claude, Codex, Cursor, v0, Lovable, Bolt and Gemini will all write you a complete website and then stop, because hosting was never their job. Free hosts exist, but they hand you DNS settings, certificates and forms to figure out yourself. Traditional hosts hand you a cPanel built for PHP sites from a decade ago.
What was missing is a host that treats "an agent produced these files" as the normal starting point. Give it a repository, get a live site, and let every subsequent push redeploy. That is the entire product, and the rest of this page is the detail around it.
02The flow, once, for every builder
The AI writes files. The files go into a GitHub repository in your account. The repository connects to hosting. Every push deploys; every deploy is versioned; a bad deploy rolls back in one click. There is nothing builder-specific in that chain, which is why it works for every tool on the market and every tool that will appear next year.
Ownership is the part people miss: the repository is created in your GitHub account, private, and stays yours whether you keep hosting with us or not. We deploy from your code; we do not take it.
03Per-builder guides
Each tool has its own page with the specifics of getting its output into a repository and live. Pick yours: a ChatGPT site, a Claude site, a Codex project, a Cursor project, a v0 export, a Lovable site, a Bolt.new project, a Gemini build. Coming from Replit with a finished site: the migration comparison. Built something and unsure of the next step at all: the short version of everything.
04What deploys, and what does not
The honest boundary, stated once here and linked everywhere else: managed static hosting serves pages, styles, client-side JavaScript and forms. It does not run server-side applications. Sites that read deploy; sites that compute (shops, logins, databases behind the page) need an application platform, and no amount of liking our prices changes that.
Most AI-built sites turn out to be pages. The builders mostly generate front-ends, and the agents that trim a project to its static routes are doing five minutes of work. The full comparison covers the boundary in both directions.
05What comes with the hosting
HTTPS on your loomweb.co address and on any domain you connect, with certificates issued automatically. A contact form endpoint that works without a plugin. Deployment history with one-click rollback. Australian infrastructure, so the site answers fast for Australian visitors. And a flat monthly price that does not change when a page gets popular. Pricing has the numbers.
06After the first deploy
The site is live, and the roadmap is ordinary: connect your own domain, ask your agent for the changes you want, push, and watch the deployment history grow. Sites on LoomWeb do not need maintenance in the WordPress sense; there is nothing to patch and nothing to update. The work left is content, which is the work you wanted to be doing.
07Frequently Asked Questions
Do I need to know anything about deploying?
No. Signup provisions everything. Your agent pushing to the repository is the deploy, the same way it saves any other work.
My site is one HTML file. Too small?
The host cannot tell the difference between one file and fifty. Same push, same deploy, same price.
Is the trial actually free?
Fourteen days, card stored but never charged inside the trial, cancelling is self-serve and immediate. The terms are stated before you commit.
What if my agent goes rogue and breaks the site?
The bad version goes live, you notice, and one click restores the previous deployment. Or work on a branch and merge when reviewed.
Build it with your AI. Host it here.
Deploys on every push, from Australia, with nothing to maintain.