To host a website made with Grok means putting the HTML Grok wrote on a server so anyone can open it at a normal HTTPS address. On deed.page that is one curl request with no account, and the Free plan holds 25 sites of up to 25 MB each (pricing).
Grok can already publish some of what it builds. xAI's announcement says every app published from Grok Build "gets its own address on grok.me", with access set to just you, anyone with the link, or the whole internet, plus optional custom domains, and that Build is on every plan (Grok Build on web and mobile, August 19, 2026, checked November 16, 2026). If you made the page in Build mode and are happy on grok.me, use that. The steps below are for everything else: HTML from a plain Grok chat, a page your Grok Bot made on its computer, or a project in the Grok Build terminal agent. Every command was run against production on November 16, 2026 with a 15-minute expiry, and the test sites were then deleted.
How do I host a website made with Grok?
Ask Grok for the page as one complete index.html with the CSS and JavaScript inline, copy it from the code block, and save it as index.html. Then publish it from any terminal:
curl -T index.html "https://deed.page/v1/sites?slug=pet-sitter-grok-v5h9&ref=blog"
The reply had "url": "https://pet-sitter-grok-v5h9.deed.page/", "version": "v1", and a deed_tok_… owner token shown once. Keep that token; it is the only credential. Pick your own suffix, since that slug is only an example. When we sent the same request again without the token, it returned 409 slug_taken with the suggestion pet-sitter-grok-v5h9-2 (choosing a slug). There is no sign-up, no claim link, and no default expiry.
If your Grok Bot made the page
Grok Bot works on its own computer (Grok Bot), so it can run that curl line itself and hand you the link. Tell it once to save the token to ~/.config/deed-page/token with chmod 600 and to reuse it, so later pages stay under one owner. The Grok Bot guide has a prompt you can paste.
A built folder from the Grok Build terminal agent
Grok Build also runs in a terminal and, per xAI, picks up your AGENTS.md, skills, and MCP servers (Introducing Grok Build). For a framework project, build first and pack the output so index.html sits at the root, then send it with the token from the first publish:
tar -C dist -czf site.tar.gz .
curl -T site.tar.gz -H "Authorization: Bearer $DEEDPAGE_TOKEN" \
"https://deed.page/v1/sites?slug=pet-sitter-grok-v5h9&ref=blog"
That returned "version": "v2" at the same URL, and /assets/style.css served as text/css. Sending the same tarball again returned "unchanged": true without a new version. deed.page serves static files only, so a Build app that calls Grok's APIs from its own code, or anything with a server or database, should stay on grok.me or another host that runs code. Bigger builds go up in parts (large sites).
Let Grok Build publish it with MCP
If you would rather Grok call a tool than a shell command, add deed.page as an MCP server:
grok mcp add --scope project deed-page https://deed.page/mcp
We ran this with Grok Build 1.0.77 in a scratch folder. It wrote [mcp_servers.deed-page] with url = "https://deed.page/mcp" to ./.grok/config.toml, and grok mcp list showed it. One thing tripped us up: grok mcp doctor refused to start a project-scoped server in an untrusted folder. Once the folder was trusted, it reported handshake OK and 30 tools, with no sign-in step. Use --scope user to put it in ~/.grok/config.toml for every project instead. The publish call Grok makes looks like this:
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"publish_site","arguments":{"slug":"pet-sitter-grok-mcp-v5h9","files":{"index.html":"<!doctype html><title>Pet sitting</title><h1>Pet sitting, published by Grok Build</h1>"}}}}
It returned ok: true, version: "v1", the subdomain URL, and a token. Passing that token to update_site gave v2 at the same address; without it, update_site refused with unauthorized. The MCP walkthrough covers the rest.
Make it the project's way to deploy
Keep the token in a file with chmod 600 and out of git, then put one line in the project's AGENTS.md so each Grok Build session knows where to publish:
Deploy: tar -C dist -czf site.tar.gz . then curl -T site.tar.gz with
Authorization: Bearer $(cat ~/.config/deed-page/token) to
https://deed.page/v1/sites?slug=<our-slug>. Tell me the url from the reply.
deed.page stores only the token's SHA-256 (trust, token hygiene).
FAQ
Can Grok host a website by itself?
Yes, if you build it in Grok Build: published apps get a grok.me address, and you choose who can open it (xAI). HTML from a regular chat or from a Grok Bot's computer needs a host, which is what the steps above cover.
Do I need an account?
Not on deed.page; the first publish mints the owner token. Sites stay under that token, and you can roll back to any of the last 10 versions on Free.
Will the site disappear if nobody visits it?
No. Sites do not expire unless you send X-Ttl for a throwaway page (TTLs). Free sites show a small "Published with deed.page" link; Hobby at $3 a month removes it.