01Artifact versus repository
In the conversation
Renders instantly for you. Lives as long as the conversation. Not reachable by visitors, not editable by other agents, not on your domain.
In your repository
Served from Australia on HTTPS. Reachable by anyone. Editable by any agent through git. Deployed on every push, with rollback.
02Artifacts versus a real site
03Artifacts versus a real site
New here? Start at the pillar page for the full picture.
An artifact renders inside the conversation, which is perfect for showing you the design and useless for showing the world. Hosting needs the files: the HTML, the CSS, the JavaScript, in a repository. Claude tends to produce clean, standards-shaped output, which is exactly what managed static hosting serves without any processing.
04The move, both ways of working
With Claude Code: sign up first, then ask it to create the repository with the site and push. That is the entire integration, because Claude Code already speaks git fluently. From the Claude web app: ask it to write out each file completely, upload them to a GitHub repository yourself, then connect it. The ChatGPT page describes the copy-out step by step; the steps are the same.
05Why Claude output and static hosting fit
Claude leans towards self-contained front-ends with client-side JavaScript, and static hosting serves that with no build step, no server, and no runtime to maintain. The division of labour stays clean: the agent builds, git hands over, the host serves. Neither side has to pretend to be the other.
06Frequently Asked Questions
My site has JavaScript interactivity. Does that still work?
Yes. Client-side JavaScript runs in the visitor browser and is served like any other file. What a static host does not run is server-side code, which Claude output rarely needs.
Does Claude need special deploy instructions?
No. A plain commit-and-push request is the deploy. The host watches the repository, so there is nothing agent-specific to configure.
Custom domain with a Claude-built site?
Yes, and the certificate is automatic. Custom domains covers the DNS steps for your registrar.
Who owns the finished code?
You do. The repository is in your GitHub account, private, and stays yours whether or not you keep hosting with us.
Build it with your AI. Host it here.
Deploys on every push, from Australia, with nothing to maintain.