Sign in and build · Free to start, no card needed · add a card when you want more credit · see pricing →

Bring your Bolt project

Bolt keeps it on GitHub. So does this.

Bolt’s help centre describes connecting a project to a GitHub repository for version control, and explains pushing commits to it. That repository is the project. Paste its link here and it is cloned with every commit, and the next change is priced in dollars, not tokens.

New project → “I already have one” → paste the link. Nothing in ${name} is changed.

ameliasagent.com/app

Build a moving-quote calculator — bedrooms, miles, and a packing add-on.

calculator · live pricelive in 1 min · $0.18

In short

Connect the Bolt project to GitHub if it is not already, copy the repository link, and paste it into New project → I already have one. It comes across with full history. Bolt's own hosting and database stay theirs; the code is yours.

What changes, what does not

Your project in Bolt and the same project here
QuestionBoltHere
Where the code livesA GitHub repository, connected for version controlA git repository here, cloned with its full history
Know the cost before you run itNo — billed in tokens as it worksYes — the rate under the composer, the cost printed on the answer
Unused allowanceRolls over one monthYou pay for the work that ran
Choose the modelNot published300+, each with its published price
Run it yourself for $0bolt.diy, your own keysYes, on your own computer with your own model keys

Bolt’s GitHub version control — repositories, commits and pushing them to GitHub — is as described in Bolt’s own help centre, read on 17 September 2026. Token billing and rollover are as read on bolt.new on 29 August 2026 and dated on the comparison.

Step by step

Out of Bolt, into a repository you own.

  1. In Bolt: connect the project to GitHubBolt’s help centre describes version control through a GitHub repository and pushing commits to it.
  2. Copy the repository linkFrom the repository on GitHub. The link a browser shows is fine.
  3. Here: New project → “I already have one”Paste the repository link. If it is private, connect GitHub and pick it from the list instead. GitLab and Bitbucket links work the same way.
  4. It is cloned with its full historyEvery commit comes across, into a repository that is yours here. It opens as a normal project from that point on — nothing about it is specific to us.
  5. Ask for the next change“Add a pricing page.” “Make the sign-up form send me an email.” The rate is under the composer before you send; what it cost is printed on the answer. Keys the app needs go in the project’s secrets.

The honest half

What Bolt does that this does not.

Their preview, their canvas

Bolt shows you the app while you build it, in its own way. Here you describe a change and read what came back, then open the preview. If the live canvas is the part you like, you will miss it.

Their hosting and services

Anything that ran on Bolt’s own hosting, database or auth does not come with the code. The repository is yours; those services were theirs. You will be asked before anything is rebuilt.

A price you can read

What you get in exchange: the model’s rate before you send, the cost printed on the answer, 300+ models each with its published price, and no credit with an unpublished exchange rate.

Related

Paste the link. Keep the history.

Free to start with no card. The repository comes across with every commit, and you ask for the next change from there.

Questions

Asked, answered

How do I get my code out of Bolt?

Bolt's help centre, read on 17 September 2026, describes connecting a project to a GitHub repository for version control and pushing commits to it. Copy that repository's link and paste it here under New project → I already have one.

Does the history come with it?

Yes. Every commit Bolt pushed is cloned into a repository that is yours here.

What about Bolt Cloud hosting and the database?

Services on Bolt's side are not in the repository. The app is published and hosted here when you ask; keys it needs go in the project's secrets; a database is rebuilt or reconnected with your say-so.

Is bolt.diy the same thing?

bolt.diy is Bolt's open-source sibling that runs on your own keys, and it is a real answer to owning the tool. This has a self-hosted path for the same reason. Importing the repository works the same from either.