# Can I publish a website I made myself, or put my app live without my AI?

Checked 2026-11-15 against GilbApp d5296208bbffa2ab70076e6194f5537c4be1ddf7.

Yes, if it is a folder of plain files that keeps GilbPlatform's rules. You can run the publishing command in Terminal yourself.

## Deeper

Also asked:

Can I publish a website I made without Kai-Zen, or one I already have? Yes, if it is a folder of plain files that keeps the rules below; publishing does not need Kai-Zen. The folder gets a new pages.dev address and uses one of your 2 sites.

Publishing puts one folder of plain files on the internet at https://&lt;name\>.pages.dev, a web address of its own, where &lt;name\> is the name given to your site. GilbPlatform does not check who or what made the files: a website you made yourself, or with another tool, can be published if its folder keeps the same rules as one your AI built. It uses one of your 2 sites, and it gets a new address there: only pages.dev addresses are offered; an address of your own, such as example.com, is not.

The rules for the folder. One folder of plain files, with index.html, the start page, at its top. At most 2000 files and 5 MB in all. Only these kinds of file are taken: html, css, js, mjs, json, map, txt, xml, webmanifest, svg, png, jpg, jpeg, gif, webp, avif, ico, woff, woff2, ttf, otf, mp3, mp4, webm and pdf. A file or folder named \_headers, \_redirects, \_worker.js, \_routes.json or functions is refused: no code of yours runs on a server there. A server is a computer on the internet that runs a program's code for it. A file that looks like it holds a secret key is refused.

What a published site may do. GilbPlatform serves every site with fixed rules that you cannot change: its pages may fetch data only from their own address and from GilbPlatform's own addresses, https://\*.gilb.com; scripts come only from the site's own files, so a script written inside a page does not run; pictures come only from those places or from data: and blob: addresses; fonts come only from the site's own files or data: addresses. So a website made elsewhere may need changes: pictures, fonts, style sheets or scripts it loads from other websites, and other websites' pages shown inside it, do not work there, and a site that needs its own code on a server does not work there at all. The security rules for published sites do not block a plain link that opens another site.

App or website. A site you made that does not sign people in with GilbPlatform can be published as a website, by adding --kind website; without it the command publishes an app. Only an app's address may sign people in and read and write their vaults; a website's cannot. A name keeps its kind.

Without your AI. You can run the publishing command yourself in [Terminal](http://support.gilb.com/help/how-do-i-open-the-terminal-on-my-computer), the window where you type commands \(on a Mac, the Terminal app\). The answer [How do I publish my app from the terminal?](http://support.gilb.com/help/how-do-i-publish-my-app-from-the-terminal) shows each step: get the newest connector, build your folder, try the command with --dry-run, run it, and open the address it prints. For a website that signs no one in, add --kind website to the command. You still need [the connector](http://support.gilb.com/help/how-do-i-connect-my-computer-to-my-vault), the small GilbPlatform program on your computer, and [Node.js 18 or newer](http://support.gilb.com/help/how-do-i-install-nodejs-and-check-which-version-i-have). The command signs in by default with the connector's own sign-in: the AI you connected through "▸ CONNECT AI" in GilbApp, acting for you. So that connection must be set up, even when you type the command yourself, unless you add --as me, which signs in as this computer instead, if it was [added to your account](http://support.gilb.com/help/how-do-i-add-a-computer-to-my-account). GilbApp has no control that puts a site live.

Those steps are written for macOS and Linux and have not been checked on Windows. If you publish from Windows and it fails, write to support@gilb.com.

Without Kai-Zen. Publishing does not need Kai-Zen, the planning agent: without it, it writes no plan for you, and no AI asks you before the site goes live, so check it yourself first. Your old site, wherever it is now, is not changed or moved by publishing a copy here. The answer [I already have an app, a website or code. Can I bring it in?](http://support.gilb.com/help/i-already-have-an-app-a-website-or-code-can-i-bring-it-in) tells more.

This answer is written for a computer screen.

Source: GilbPlatform 0fc5a548 \(https://id.gilb.com/version, read 13 November 2026\): workers/publish-ingest/src/checks.ts:11-21 \(file kinds; \_headers, \_redirects, \_worker.js, \_routes.json, functions\), :30-40 and :155-158 \(secret-looking files refused\), :125-160 \(no check of who made the files\), :165-172 \(the rules every site is served with: default-src 'self'; script-src 'self'; img-src 'self' data: blob: https://\*.gilb.com; font-src 'self' data:; connect-src 'self' https://\*.gilb.com\); src/publish/ticket.ts:20, :31 \(2000 files, 5 MiB\); src/publish/records.ts:256 \(2 sites\), :390 \(a name keeps its kind\); src/routes/publish.ts:460-485 \(only an app's address is admitted\). Connector 0.6.1, served at https://gilb.com/app/gilb-connector.mjs, read 13 November 2026: publish --dir --name \[--kind app\|website\] \[--dry-run\] \[--as ai\|me\]; Node 18 or newer. Standards read from GilbPlatform on 13 November 2026: Proc\_v\_i\_c\_PublishPagesDev \(steps 4-8; the connector's own sign-in, a Connected AI acting for the person; --as me signs in as the computer\), Standard Rule\_Code\_deployment \(RuleDeployPagesDev: only pages.dev; the security rules\). GilbApp 49b1ae53 \(https://gilb.com/app/version.json, read 13 November 2026\): no publishing control in src. Live help pages, sentences shared: How do I publish my app from the terminal?; How do I put my app or website live on the internet?; I already have an app, a website or code. Can I bring it in?
