# Is my app's code public once it is live?

Checked 2026-11-15 against GilbApp d5296208bbffa2ab70076e6194f5537c4be1ddf7.

Yes: anyone with the address can open and read every file put live. Data your app saves for signed-in people stays in vaults.

## Deeper

What is put live. Publishing puts the files of one folder, your app as it was built, on the internet at https://&lt;name\>.pages.dev, where &lt;name\> is the name given to your site. It is public: anyone on the internet who has that address can open it, and no sign-in is needed to open it. Everything in the folder that was put live can be opened that way, so [keep passwords and keys out of your app's files](http://support.gilb.com/help/where-do-i-keep-the-passwords-and-keys-for-the-services-my-app-uses). The files of a web app are sent to every browser that opens it, so anyone can read them; that is true of every website. No code of yours runs on a server there, so nothing of your app is hidden on a server. GilbPlatform has no way to make a site private.

What is not put live. Only that one folder is sent. The rest of your project's folder, your plan and your code's copy on GitHub stay where they are. Data your app saves for people who sign in is kept in vaults, not in its files: a person who signs in to your app reaches only the data they themselves may reach. The answer [Who can see and use my app once it is live?](http://support.gilb.com/help/who-can-see-and-use-my-app-once-it-is-live) tells more.

Your GitHub copy. When building starts, Agent.Coder's rules [require your code on GitHub](http://support.gilb.com/help/do-i-need-a-github-account), a website where programmers keep and share code. A repository, one project's code there, can be private, seen only by you and those you invite, or public, seen by anyone. Tell your AI to [make the GitHub copy private](http://support.gilb.com/help/how-do-i-keep-a-private-copy-of-my-code-on-github), unless you want everyone to see your code. Publishing does not change it.

Keep secrets out. 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. So put nothing in your app's files that only some people may see; keep it in a vault, which is reached only by those you give access. Where keys belong is in Where do I keep the passwords and keys for the services my app uses? If a key may have been seen by others, make a new one at the service that gave it and end the old one; that service's own pages say how.

This answer is written for a computer screen.

Source: GilbPlatform 0fc5a548 \(https://id.gilb.com/version, read 13 November 2026\): src/publish/site-name.ts:67-70 \(the one address, https://&lt;name\>.pages.dev\); workers/publish-ingest/src/checks.ts:21, :146 \(no functions folder: no code on the server\), :30-40, :153-158 \(key-shaped strings refuse a publish\); src/routes/publish.ts:42-45 \(every admitted address serves code the builder controls\), :107-115 \(a ticket names only kind and name: no private option\). Connector 0.6.1, served at https://gilb.com/app/gilb-connector.mjs, read 13 November 2026: publish sends the files of the folder given with --dir. Standards read from GilbPlatform on 13 November 2026: Agent.Coder \(AskGoLive: it becomes public on the internet at that address; Contextual: Git workflow\), Standard Rule\_Code\_deployment \(RuleDeployPagesDev\). Live help pages, sentences shared: Who can see and use my app once it is live?; Do I need a GitHub account? \(private or public repository\); Where do I keep the passwords and keys for the services my app uses?; Where does all the code go, and can I get a copy of it?
