← What is the difference between …?
How do I put my app or website live on the internet?
Short answer
When your app is built and checked, your AI asks if it should go live; say yes, and it goes live at https://<name>.pages.dev.
Deeper
Also asked:
What does go live or publish mean? Putting your app or website live, or publishing it, means putting it on the internet, at a web address of its own, where other people can open it.
App or website: which am I making, and what is the difference? The difference between them when you publish: an app can sign people in and read and write vaults; a website cannot read or write vaults. Your AI publishes an app unless you say it is a website, and a name published as one kind cannot become the other.
Can I publish a website that only shows information, with no sign-in? Yes. Tell your AI it is a website, not an app. A website cannot read or write vaults, and it skips the sign-in question; it goes live at https://<name>.pages.dev, like an app.
What does pages.dev in my address mean? pages.dev is an address service run by Cloudflare, a web company. Every site goes live at https://<name>.pages.dev, where <name> is the name given to your site.
Can my website have its own name, such as example.com? Not today. Only pages.dev addresses are offered; an address of your own, such as example.com, is not. You can choose the <name> part: tell your AI before you say yes.
Does my app need a sign-out button? If your app signs people in, it gets one: after your yes to going live, Agent.Coder, the agent that builds apps, gives the app a button to sign out.
Which version of the connector do I need to publish? Publishing needs connector 0.5.13 or newer. The connector is the small GilbPlatform program on your computer; the answer How do I update Claude Code and the connector? shows how to get the newest.
Can I publish from GilbApp's chat, or only from Terminal? GilbApp has no control that puts an app live. With Grok alone, in GilbApp's chat, your app cannot be put live: you need an AI coder connected through the connector, and it puts your app live with one command in Terminal.
Putting your app or website live means putting it on the internet, at a web address of its own, where other people can open it. On GilbPlatform that address is https://<name>.pages.dev, where <name> is the name given to your site. pages.dev is an address service run by Cloudflare, a web company. Only pages.dev addresses are offered; an address of your own, such as example.com, is not.
Two kinds of site. An app can sign people in and read and write vaults. A website cannot read or write vaults. Your AI publishes an app unless you say it is a website, and a name that was published as one kind cannot become the other.
How it goes. You plan your app with Kai-Zen, the planning agent, and Agent.Coder, the agent that builds apps, builds it step by step. An agent is your AI following one written procedure, its standing instructions, for one kind of work. When the last part is built and its checks pass, Agent.Coder is told to ask if you want it live at https://<name>.pages.dev, a web address of its own. It becomes public on the internet at that address. Each person can have 2 sites; publishing a site you already hold again does not use a new one; for more, write to [email protected]. It is told never to put your app live without your yes. The answer What happens when my AI asks if my app should go live? tells what it asks and what you can answer.
After your yes. If your app signs people in, Agent.Coder first asks how long a person should stay signed in: from 5 minutes up to 14 days, and 14 days if you do not choose; each renewal starts the time again. It gives the app a button to sign out. Then it builds the app and puts it live with one command in Terminal, the window where you type commands (on a Mac, the Terminal app). It checks that the address opens and tells you the address. To tell that your site is live, open that address in your browser: if your site shows, it is live. A website that signs no one in skips the sign-in question.
The name. The name is part of the address. It may use only small letters a to z, digits and hyphens, 3 to 40 characters, and it must not already be in use on pages.dev. Some names are kept back, such as names of well-known brands. If you want a certain name, tell your AI before you say yes.
Which AI asks. Your AI asks only when it works under GilbPlatform's standards: an AI coder, such as Claude Code, Anthropic's AI, connected to GilbPlatform through the connector, the small GilbPlatform program on your computer. An AI used outside that setup does not know to ask. You can also tell your AI in your own words that you want the app live; it then follows the same publishing steps, and still needs your yes. Publishing needs connector 0.5.13 or newer; the answer How do I update Claude Code and the connector? shows how to get the newest.
GilbApp has no control that puts an app live. GilbApp's chat reaches a folder on your computer only when Claude Code, Anthropic's AI that you run in Terminal, is connected to it and a code folder is switched on (Choose a code folder, then Code in); otherwise code kept there needs Claude Code in Terminal.
The site belongs to you, also when your AI publishes it for you. Who can open it, and what they can reach, is in the answer Who can see and use my app once it is live? To change your app later, see How do I update my app after it is live? For more than 2 sites, see How many sites can I have, and how do I get more?
If publishing is refused, or your site does not open after it was published, write to [email protected] with the address and what your AI showed you.
This answer is written for a computer screen.
Source: Standards read from GilbPlatform on 13 November 2026: Agent.Coder (AskGoLive: ask when the last increment runs and its checks pass; public at that address; 2 sites per person; the same site again does not use a new one; more via [email protected]; never publish without the person's yes; Contextual: read Proc_v_i_c_PublishPagesDev when publishing), Proc_v_i_c_PublishPagesDev (steps 1-3: ask how long, 14 days longest and default, 5 minutes shortest, a Sign out button, a website without sign-in skips them; steps 4-8: build, one command, it prints the address, check that it loads; connector 0.5.13 or later), RuleDeployPagesDev (only pages.dev; the name free across Cloudflare). GilbPlatform 0fc5a548 (https://id.gilb.com/version, read 13 November 2026): src/publish/site-name.ts:12-13, :16, :29, :51, :68 (3 to 40 characters; a to z, digits, hyphens; reserved and brand names; the address); src/publish/records.ts:256, :259 (2 sites; [email protected]). GilbApp 49b1ae53 (https://gilb.com/app/version.json, read 13 November 2026): no publishing control in src. Connector served at https://gilb.com/app/gilb-connector.mjs, read 13 November 2026: version 0.6.1, publish command. Live help pages: What can I make, and is there something I can't make?; How does Kai-Zen put a change live? (GilbApp has no control that puts a change live); How do I make sure I end up with an actual app?; Can my app have its own users who sign in?; How do I update Claude Code and the connector?; What do I need before I can put my app live? (with Grok alone, in GilbApp's chat, an app cannot be put live)
Checked against GilbApp d529620.