← Last checks before going live (Testing)
What should I check before I say yes to going live?
Short answer
Try it yourself, check the name, kind and sign-in time, clear test data and keep secrets out. The yes is yours.
Deeper
Also asked:
Who decides that it is good enough: me or my AI? You do. Agent.Coder asks you if you want it live when the last part runs and its checks pass; its rules say the person decides, not the AI, and it never publishes without your yes.
Going live means putting your app on the internet at https://<name>.pages.dev, a web address of its own, where <name> is the name given to your site. GilbPlatform and GilbApp have no checklist of their own for it, and GilbApp has no control that puts an app live. The checks below are what the other help answers and your AI's written rules point to; the list itself is advice.
Who decides. You do. Agent.Coder, the agent that writes your app's code, asks you if you want it live when the last part of what you asked for runs and its checks pass. An agent is your AI following one written procedure, its standing instructions, for one kind of work. Its rules say the person decides, not the AI, and it never publishes without your yes. When a change alters the data your app has stored, or how that data is laid out, Kai-Zen, the planning agent, first tells you what changes and asks you, a person, not an agent, for your go. The answer What happens when my AI asks if my app should go live? tells what it asks.
Is it ready? The signs are in the answer When is my app, website or program finished?: every step you wanted is built and tested, you have tried it yourself, and nothing you need is missing or broken.
Before you say yes, you could check these:
- You tried it yourself, the way a new person would. Your AI starts it on your computer and tells you what to try; see Where can I test what I've built, and try it myself before anyone else sees it? and How do I test my app the way a new user would, on other phones and browsers?
- Every link and button works. Agent.Tester, the agent that tests what others built, runs your app's tests and writes tests for what has none, but tests prove only what they test. Click every link and press every button on every screen yourself. You can also ask your AI in your own words to go through them; with a browser tool, a way for your AI to open and look at web pages itself, it opens the pages itself. Tell it what does not work, as How do I tell my AI about a fault so it can fix it? shows.
- No made-up records are left where others see them. Check every vault your app shows to others (a vault is the place where a person or a group keeps their records), and ask your AI which vaults those are; see How do I put test data into my app, and clear it out before going live?
- No passwords or keys are in your app's files. Everything in the folder that was put live can be opened by anyone. Publishing is refused when a file holds something shaped like a secret key, such as a Stripe secret key or a GitHub token, but the platform cannot know what else you want kept private.
- The name is the one you want. 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. A site cannot be renamed later, and a name you have published stays yours and counts as one of your 2 sites. A new name is a new site, and uses one of your 2. If you want a certain name, tell your AI before you say yes.
- The kind is right. 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.
- You know how long people should stay signed in. If your app signs people in, your AI asks you after your yes: from 5 minutes up to 14 days, and 14 days if you do not choose; each renewal starts the time again.
- You have room for it. Each person can have 2 sites. Publishing a site you already hold again works and does not use a new one. If you already hold 2 other sites, publishing is refused; see How many sites can I have, and how do I get more?
- It needs no outside service. A published app may fetch data only from its own address and from GilbPlatform's own addresses, such as id.gilb.com, and it has no server code, code that runs on a computer on the internet for your app. So payments taken inside your app, e-mails sent by your app and other outside services do not work in it today; see How do I test payments and e-mails before my app goes live?
- If your app collects anything about people, you have read Do I need a privacy page and a cookie banner? and Do I need terms of use for my app? This help gives no legal advice.
Know what going live means. It is public: anyone on the internet who has that address can open it, so search engines such as Google may find it; nothing here promises that they will. GilbPlatform has no option to keep it to invited people; see Can I let a few people try my app before everyone can see it? You cannot take a site off the internet yourself today: no button or command does it, and a site you have put live keeps counting as one of your 2. The answer How do I take my app off the internet? tells more. If you need this, write to [email protected].
If something is not right. Say no, or say what to fix first. Nothing goes live; your AI tells you that the app is not live, and where it runs instead. You can tell it later, in your own words, that you want it live. The answer I found a fault just before going live. Should I wait or publish anyway? helps you choose.
After your yes. GilbApp shows no list of your sites, so keep a note of each address when your AI gives it to you. Then Kai-Zen asks you to check it live; see How do I check my app once it is live?
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; never publish without the person's yes, the person decides; No: say it is not live, and where it runs; Browser: open pages with the runtime's browser tools; AfterIncrement), Kai-Zen.GoLive (Ask: if it changes stored data or its shape, tell the requester what changes and ask a person for go), Kai-Zen.HumanCheck (Ask), Proc_v_i_c_PublishPagesDev (steps 1-3: how long people stay signed in, 5 minutes to 14 days, 14 days by default; step 6: kind is app unless you say website), Standard Rule_Code_deployment (RuleDeployPagesDev: 2 sites; a Live, Offline or TakenDown site counts; Not live yet: takedown and abuse handling). GilbPlatform 0fc5a548 (https://id.gilb.com/version, read 13 November 2026): src/routes/publish.ts:278, :413, :442 (the only publish doors: no rename, list or take-down door); src/publish/records.ts:386-391 (a held name stays its owner's; a name cannot change kind), :410-416 (a new name at the limit is refused); src/publish/site-name.ts:12-13, :16, :29, :51, :68 (the name rules and the address); workers/publish-ingest/src/checks.ts:21, :30-40, :146, :165-172 (no server code; key-shaped strings refused; connect-src 'self' https://*.gilb.com). GilbApp 49b1ae53 (https://gilb.com/app/version.json, read 13 November 2026): no publishing control and no list of sites in src. Live help pages, sentences shared: When is my app, website or program finished?; What happens when my AI asks if my app should go live?; How do I put my app or website live on the internet?; Who can see and use my app once it is live?; How many sites can I have, and how do I get more?; How do I put test data into my app, and clear it out before going live?; Who tests my app, and why does my AI write tests?; Can I connect Stripe, PayPal or Vipps to my app?
Checked against GilbApp d529620.