# Can I hand my app over to someone else, or sell it?

Checked 2026-11-15 against GilbApp d5296208bbffa2ab70076e6194f5537c4be1ddf7.

The address stays with your account. You can give them a copy of the code, and "Control" on the vaults they should look after.

## Deeper

Your app has three parts: its address, its code and its data. Each moves in its own way, and the address does not move at all.

The address. Your app is live at https://&lt;name\>.pages.dev, where &lt;name\> is the name given to your site. The site belongs to you, also when your AI publishes it for you. GilbPlatform keeps one owner for each site, the account that first claimed its name, and nothing in GilbPlatform or GilbApp moves a site to another account. Only that account can publish under that name; another account is told "This site name is not held by this account." So the other person cannot update your app at your address. If you need a site moved to someone else, write to support@gilb.com; nothing here promises what support can do.

The code. Code is the text your app is made of. It is kept in the folder on your computer where your AI builds it, with a copy on GitHub, a website where programmers keep and share code, once building has started. You can give the other person a copy of that folder. A repository is one project's code on GitHub. GitHub says: "You can transfer repositories to other users or organization accounts." You need administrator access to the repository. When you transfer it to another person's account, that person gets an e-mail with instructions to accept, and the invitation ends if they do not accept within one day \(https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository, read 13 November 2026\). The answer [Where does all the code go, and can I get a copy of it?](http://support.gilb.com/help/where-does-all-the-code-go-and-can-i-get-a-copy-of-it) tells more.

Putting it live from their account. With the code, the other person can put the app live from their own GilbPlatform account, with [their own AI coder connected through the connector](http://support.gilb.com/help/how-do-i-connect-my-computer-to-my-vault), the small GilbPlatform program on their computer. Their site gets its own name and its own address. A new name is a new site, and uses one of their 2. Your site stays at your address and keeps counting as one of yours; the answer [How do I take my app off the internet?](http://support.gilb.com/help/how-do-i-take-my-app-off-the-internet) says what can be done about it.

The data. Your app keeps its data in vaults, not in a database of its own. A vault is the place where a person or a group keeps their records. The people who use your app keep their data in their own vaults; it stays theirs, and no one hands it over. A vault you own, such as one you made for your app's shared records, you can hand over by giving the other person "Control" on it. Whoever holds "Control" on a vault decides who else may read or write there. "Control" gives no "Read" or "Write" by itself, but whoever holds it can take a copy of the whole vault, every record and file, and can give themselves "Read" or "Write". Giving someone "Control" does not make them the vault's owner. GilbApp shows no control that changes who owns a vault.

In GilbApp, someone who holds "Control" on a vault gives it under "▸ GRANT ACCESS" in the vault's pane: keep "Person" chosen, search for the person and select them, choose "Control" under "ACCESS", and press "Grant". The answer [How do I share a vault with a person?](http://support.gilb.com/help/how-do-i-share-a-vault-with-a-person) shows each step with pictures. The other person needs [their own account](http://support.gilb.com/help/how-do-i-sign-up) first: you share with a person's vault, not with an e-mail address.

Built for a client. The plainest way is that your client has their own GilbPlatform account and the app goes live from it, under a name they hold: give them the code, and "Control" on the vaults you made for the app. What you agree with your client about payment, ownership and support is between you. The Terms do not name apps that others build, so they say nothing about your app itself.

Selling. MyJackfruit's Terms say: "You own what you put in your vaults." \(https://myjackfruit.com/terms/, last updated November 11, 2026, read 13 November 2026\). What you make by following a standard is yours: your work, your apps and your data. The Terms and the licence say nothing more about the code of an app you build, such as where you may run it or whether you may sell it. If you need to know, write to support@gilb.com. Parts taken from GilbPlatform's library of ready-made code are different: the library's code has no licence, and before you ship one in an app of your own, you [ask Kai Gilb in writing](http://support.gilb.com/help/how-do-i-ask-for-licence-permission-and-when-does-it-end) through GilbPlatform; the answer [How do I reuse app code units?](http://support.gilb.com/help/how-do-i-reuse-app-code-units) says more. This is not legal advice; before you sell an app or sign a contract for one, ask someone who knows the law where you live. The answer [Who owns what I build, and what may I do with it?](http://support.gilb.com/help/who-owns-what-i-build-and-what-may-i-do-with-it) tells more.

This answer is written for a computer screen.

Source: GilbPlatform 0fc5a548 \(https://id.gilb.com/version, read 13 November 2026\): src/publish/records.ts:423 and :479 \(one owner per site, written when the name is claimed and when it is published\), :386-389 \(another person's name is refused\); src/routes/publish.ts:390 \("This site name is not held by this account."\), :277, :412, :441 \(the only publishing doors; none moves a site to another account\). Standard Rule\_Code\_deployment \(RuleDeployPagesDev: any signed-in person may publish; at most 2 sites\). GilbApp 49b1ae53 \(https://gilb.com/app/version.json, read 13 November 2026\): src/components/VaultAccessManager.tsx:823 \("▸ Grant access"\), :841-846 \("Share with", "Person"\), :932 \(access levels\), :983 \("Grant"\); src/components/records/recordIcons.tsx:310 \("Control"\); no control in src that moves a site or a vault's ownership. GitHub: https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository \(read 13 November 2026\). MyJackfruit: https://myjackfruit.com/terms/ \(Last updated: November 11, 2026, read 13 November 2026\). GilbPlatform.Licence \(YourWork\). Live help pages, sentences shared: How do I put my app or website live on the internet?; Who can see and use my app once it is live?; Who can give access, and to whom?; How do I share a vault with a person?; Where does all the code go, and can I get a copy of it?; Can I make a second app from the same plan or code?; Who owns what I build, and what may I do with it?; Do I need terms of use for my app?; How do I reuse app code units?
