Your code
Your code, and how to take it with you
Builddu writes a real codebase for your project, and it is yours. Our terms say so in one sentence — “Generated code and content are yours.” This page is the rest of the answer: what you can read, change, download and move somewhere else, and what stays here.
Edit the code yourself
The code panel opens the project as it actually is — every file, not a summary.
- Open any file in the project and read it. The whole tree is there, not a curated subset.
- Edit a file and save it. Saving code spends no credits — it is not an AI run, and it is not charged like one.
- Ask for an AI edit from inside the editor when a change is larger than the file you are looking at.
Download the whole project
Not a sample, and not a copy of the preview: the project's files.
- Download the whole project as an archive, from the code panel.
- It is the project's files, not a summary or a snapshot of the preview.
- Downloading costs nothing. There is no limit on how often you take a copy.
Sync it to your own GitHub repository
Connect a repository you control and decide which side is the source of truth.
- Connect a repository you already own, with a token you provide.
- Choose the direction when you connect: push the project into the repository, or pull the repository into the project.
- Either direction replaces what is on the receiving side. It is not a merge, so point it the way you mean before you run it.
- Disconnecting leaves your code alone — in the product's own words, your project code is not affected.
Every build is a version you can go back to
The reason an experiment is cheap: a change you dislike is not a change you are stuck with.
- Every build is kept as a version of the project.
- Restore an earlier one when a change went the wrong way, without rebuilding from the prompt.
- Restoring costs a small fixed amount — one or two credits, depending on the project.
So how locked in are you?
The direct answer, including the part that is not in our favour.
What you own
The code and content Builddu generates. Our terms put it in one sentence: “Generated code and content are yours.”
What you can export
The project's files, as an archive, whenever you want them — including the server-side code, not only the pages.
What you can sync
The project, to a GitHub repository you control, in either direction. After that the repository is yours to work in like any other.
What stays with Builddu
The running app itself: the hosting, the live URL, the managed database and the version history live here. A downloaded archive is your code, not a running copy of your app — you would host and run it yourself.
Common questions
Do I own the code Builddu generates?
Yes. Our terms say: “Generated code and content are yours.” You are responsible for what you publish with it.
Can I download my code?
Yes, as an archive of the project's files, from the code panel. It costs nothing and you can do it as often as you like.
Can I edit the code myself?
Yes. Every file is open in the code panel, and saving a file spends no credits.
Can I connect GitHub?
Yes. Connect a repository you own and choose the direction — project into repository, or repository into project. Each direction replaces what is on the receiving side rather than merging.
Can I restore an earlier version?
Yes. Every build is kept, and you can restore one for a small fixed cost of one or two credits.
Am I locked into Builddu?
Your code is not locked in: you can read it, edit it, download it and push it to your own repository at any time. What lives here is the running app — the hosting, the live URL and the database behind it.
How other builders answer the same question is set out in our side-by-side comparisons and guides. The full terms are on the terms page.
Build something and keep it