Can I have a test version and a live version of my app at the same time?
Short answer
Yes: your AI builds and tests on your computer while the live version keeps running; nothing changes live without your yes.
Deeper
Your live app is at a web address of its own, https://<name>.pages.dev, where <name> is the name given to your site. While it runs there, your AI builds and tests the next version on your computer. By default only you see that version: its preview opens in a browser on your computer. When the change is built and checked, it goes live only with your yes, at the same address, and the live app stays as it was until then. The answer How do I update my app after it is live? shows how.
A second address for testing. The publishing steps give one address per site name and no separate test stage. You can put a second copy live under another name, but that is a new site that stays held under that name and keeps counting toward your 2: each person can have 2 sites, apps and websites together, and for more you write to [email protected]. A site is public on the internet at its address, so anyone who has the address can open the copy too. The answer How many sites can I have, and how do I get more? tells more.
The data is the same for both. Your app's users' data is not kept on the site; it is read and written in the vault of the person signed in to it. If your app signs people in, the copy on your computer may first need your approval to reach your vaults; ask your AI what it needs. So when you sign in to the version on your computer and to the live one, both save into the same vaults, and what you save while you test is saved for real. The answer Test data or real data: which does my AI use while it builds? tells more.
Trying a change before your users see it. Ask your AI to show you the change on your computer first, and try it there yourself before you say yes; until then your users keep the live version. Agent.Coder is told to prove a change to the screen in a real browser, at phone size, before it hands it back. Because both versions save into the same vaults, try a change that writes or deletes with made-up records, and clear them out before going live; the answer How do I put test data into my app, and clear it out before going live? shows how. When a change goes live, Kai-Zen, the planning agent, asks you to check it live, and fixes what you send back, puts it live again and asks again, until you approve. GilbPlatform has no way to show a new version to only some of your users: the address shows the same version to everyone who opens it. The answer Can I let a few people try my app before everyone can see it? tells more.
What counts. Kai-Zen, the planning agent, counts a step as delivered only when the people it is for can use it, and measures it there, not on a test copy. The version on your computer is for checking before your yes; the real measure comes once it is live.
This answer is written for a computer screen.
Source: Standards read from GilbPlatform on 13 November 2026: RuleDeployPagesDev ("An app or website built on GilbPlatform is published at https://<name>.pages.dev ... Do not publish to another host."; at most 2 sites; Publishing a site you already hold again always works; [email protected]), Proc_v_i_c_Deployment (ProcDplStPagesDev; the staging steps are Netlify only, Not the GilbPlatform path), Proc_v_i_c_PublishPagesDev, Proc_v_i_c_Handback (dev server on the builder's computer), Agent.Coder (AskGoLive), Kai-Zen.GoLive, Kai-Zen.ValueDeliveryStepRules.Delivered (Measure there, not on a test copy.). GilbPlatform 0fc5a548 (https://id.gilb.com/version, read 13 November 2026): src/publish/site-name.ts:68 (one name, one address); src/publish/records.ts:256 (2 sites). Live help pages, sentences shared: How do I update my app after it is live?; How many sites can I have, and how do I get more?; How do I put my app or website live on the internet?; Can my app have its own users who sign in? Agent.Coder (AfterIncrement: a UI change is proved in a real browser at phone size before hand-back); Kai-Zen.HumanCheck (check it live; fix, put it live again and ask again until they approve). GilbPlatform 0fc5a548: src/routes/publish.ts:107-115 (a publish names only kind and site name: no option to show a version to some people only). Live help pages, sentences shared: What should I do in the first week after my app is live?; How do I put test data into my app, and clear it out before going live?
Checked against GilbApp d529620.