What OpenAI announced on November 4
On November 4, 2026, OpenAI said it will acquire Pierre Computer Company. OpenAI says the purchase is meant to expand the tools in Codex for building, understanding and reviewing code.
The deal is announced, not finished. OpenAI's own wording is that it will acquire Pierre, so read it as pending.
Most owners have never heard of Pierre, and that is fine. What matters is one product Pierre makes, and which website tools use it.
What Code Storage is and which site builders use it
Pierre's main product is called Code Storage. It is built on Git, the standard format for keeping code along with the history of every change made to it. It is designed to be used by software rather than by people. Think of it as a back room that other tools write into for you, not a place you would ever sign in to.
Pierre's site, as it read on November 4, 2026, names Lovable and Bolt among the companies that rely on Code Storage to store the code their tools generate.
Code Storage can also sync with GitHub, GitLab and Bitbucket. Your builder has its own version of that kind of setting, and that is the one you want.
Why this reaches a site built with Lovable or Bolt
If your website came out of Lovable or Bolt, the tool wrote its code. Pierre says those two tools keep the code they generate in Code Storage. So the files behind your site may sit on a service that OpenAI says it will buy.
Read that as a reason to keep a copy, not as a warning. This post makes no guess about what, if anything, changes for Lovable or Bolt sites.
The better reason is ownership. Right now your site's code lives inside the builder, and you reach it through the builder's account. A copy in a GitHub account in your business's name is yours to keep, whoever owns the companies in between.
Both builders have a setting for this. Lovable's Git sync keeps a project's code in your own GitHub, GitLab or Bitbucket repository and syncs changes both ways. A repository is the folder that holds a project's code and its history.
Put a Lovable site's code in your own GitHub account
You need a GitHub account first. If you don't have one, make it in the business's name, with an email address you will still read in five years. Then, in Lovable:
- Open the project that is your website.
- Open Project settings, then Git, then GitHub.
- Click Connect next to your GitHub account. Only a workspace or project owner or admin can connect a project to GitHub.
- Lovable creates a new GitHub repository, private by default, and starts syncing.
From then on, the copy in GitHub keeps up with the project, and changes go both ways. You don't have to remember to export anything.
When it is done, sign in to GitHub and open the new repository. You should see folders and files with names that mean nothing to you. That is the right result.
Put a Bolt site's code in your own GitHub account
Same idea, different buttons. In Bolt:
- Open the project you want to copy.
- Click the GitHub icon in the top-right corner of the screen.
- Approve access for StackBlitz, Bolt's parent company.
- Enter a name for the repository and click Create repository.
The new repository starts out private, on a branch called main. You don't need to touch the branch name.
Leave the repository private. Your site's code is not something to publish, and nothing here asks you to.
Whose GitHub account it should be
If someone else built the site for you, a freelancer or a relative, ask them to run these steps while signed in to a GitHub account that belongs to the business. For a Lovable site, if they are the project's owner or admin and you are not, only they can connect it to GitHub. A copy in their personal account is their copy, not yours.
Once the repository exists, sign in yourself and look at it. Write down the account email and keep that login with your domain and hosting logins. If the person who built the site moves on, the code stays with you.
What to do
- Find out which tool built your website. If it was Lovable or Bolt, set up the copy this week.
- Make a GitHub account in the business's name if there isn't one yet.
- In Lovable, open Project settings, then Git, then GitHub, and click Connect.
- In Bolt, click the GitHub icon in the top-right corner, approve access and click Create repository.
- Sign in to GitHub and check that the new repository is there and private.
- Leave the repository in place, because deleting a Lovable one stops the sync.
If you would rather start over with a site where you own the code and the accounts from the first day, that is how our websites are built.