01Done is not live
An agent will build you a complete website in an evening: pages written, styles sorted, the build passing, a local preview you can click around in. Then the session ends and the site exists in exactly one place, which is your machine. Publishing is the step between that folder and a stranger with a browser, and it is the step the agent was never assigned.
This guide is about closing that gap with machinery you already have. There is no new tool to learn and nothing to drag around in a page builder. The deploy is a git push, made by the same agent that wrote the code, watched by a host built for exactly that.
The whole thing in one line: your site lives in a GitHub repository in your account; your agent pushes to it the way it saves any other work; LoomWeb turns each push into a release on an HTTPS address and keeps every past release for rollback. How it works shows the pipeline as a diagram. The rest of this page is the detail around it.
02Why the repository sits in the middle
Every serious coding agent already speaks git. Claude Code, Codex CLI, Cursor, Copilot and a plain chat session where you paste the commands all end their work the same way: files changed, history recorded. Making that folder a GitHub repository gives every tool the same publishing interface, which is why this hosting has nothing builder-specific in it, and why swapping agents halfway through a project is a footnote rather than a migration.
Ownership follows from the same choice. The repository is created in your GitHub account, private, and stays yours whether you keep hosting with us or not. The connection is granted through GitHub OAuth with scoped access to that repository. Your GitHub password is never seen by anyone here, the access can be revoked from GitHub's own settings whenever you like, and the code stays in your account through all of it.
03The first deploy, start to finish
Sign up and connect GitHub
Signup provisions a private repository in your account and attaches hosting to it. You are never charged at signup; the first fourteen days are a trial.
Let the agent fill the repository
It plans and writes as usual, runs the build, and lands the site files on a branch you can see.
Push to main
The push triggers a deploy. The static build is validated, then the release serves on yourname.loomweb.co over HTTPS.
Click through everything
Every route in a normal browser, and the contact form once. The form endpoint is the one moving part a static site has.
Bring your domain when ready
Add it in the portal and point DNS across. Certificates are issued and renewed for the loomweb.co address and the domain alike.
04The loop, from a phone
05What a release is, and what rollback buys
Every push becomes an immutable release: numbered, dated, kept. Live traffic points at the newest healthy one. If a change turns out wrong, the portal restores the previous release in one click, with no reverting commits and no asking the agent to fix its own work under pressure. The realistic worst case of a bad push is a short window where the site shows something you did not intend, followed by a restore.
That property is what lets you move quickly with agents. Publishing is reversible, so speed is affordable. Teams who want more control keep the agent on a branch and merge to main only after a human has read the diff. Deployments follow main; review happens wherever you prefer, and for most people that is the pull request view in GitHub.
06The boundary: what this hosting cannot run
The limit of the product, in plain terms: LoomWeb serves static sites. Pages, styles, client-side JavaScript, images, and a contact-form endpoint. It does not run PHP, server-side applications, databases or email. A site that needs to compute on a server, a shop with a cart for instance, needs an application platform, and wanting it otherwise does not change the physics.
Most agent-built sites turn out to be pages. The practical test is to deploy and click through: if everything a visitor can reach works on the preview address, the site belongs here. If one part needs a server, that part needs a different home, and the remaining pages can still live with us. Static versus WordPress covers the boundary in both directions.
07Two ways to run the same site
Agent straight to main
The agent pushes and the site updates, with rollback as the safety net. Fits a solo owner moving fast on a site where a mistake costs minutes.
Branch, review, merge
The agent works on a branch; a human merges when satisfied. Fits client work, cautious owners, and anyone who wants the pull request to be the publish button.
08What running the site costs
Signup starts a fourteen-day trial and never charges you at signup. After the trial the plan is $39 a month, with billing handled by BSimple (MrSoftware Pty Ltd), and cancelling is self-serve from the portal at any time. Card capture happens on a hosted, tokenised payment page; card numbers never sit on our servers. Pricing carries the full list.
The serving side runs in Australia, so pages come back quickly for local visitors. Certificates renew without anyone writing a reminder. Deployment history accumulates without a quota to manage. The recurring maintenance a server-based site generates has no equivalent here, which is why the price stays the same in year two.
09Choosing your loop
The loop is identical for every agent; each tool just reaches it by its own road. Terminal agents push as part of their natural rhythm. Cursor keeps work local until someone pushes. Chat sessions hand you files that need placing in the repository. The ten guides below take the tools and questions one at a time, and the sibling pillar AI website hosting covers the same ground from the builder side, including export-based tools like Lovable, Bolt and v0.
If you read nothing else, read the five steps above and try them with the next thing your agent builds. The arrangement is easier to operate than to describe, and your agent will not need the tutorial: it already knows the verbs.
10The guides in this set
11Questions about agent publishing
Does my agent need a LoomWeb account or API key?
No. The agent pushes to GitHub with the access it already has. LoomWeb deploys from the repository and never touches the agent.
What if the agent pushes broken work?
It goes live, you notice, and you restore the previous release in one click. Or keep the agent on a branch and merge when the work is reviewed.
Can two different agents work on the same site?
Yes. They share the repository. Git does not care who made the commit and neither does the deploy.
Is there a CI config to write?
None. There is no YAML to write and nothing to wire up; keeping the pipeline working is our job, and a push to the tracked branch is the deploy.
What does hosting cost after the trial?
Fourteen days free, then $39 a month, cancelled from the portal whenever you like. The repository and code stay yours either way.
Do I need to know git to supervise all this?
Enough to read a diff, which is easier than it looks. The agent handles the rest of the syntax.
Build it with your AI. Host it here.
Deploys on every push, from Australia, with nothing to maintain.