Taking your code with you

The output is a conventional project. There is no proprietary runtime to keep it working and nothing that stops building the day you stop paying. Three ways out, and they do different things.

Export

Downloads the accepted checkpoint as an archive: the files, as they are, ready to open in an editor and run with the package manager the project declares. Nothing is rewritten on the way out and nothing phones home.

This is the option that owes nothing to any account, including yours. It works the same whether you are on the hosted service or running your own copy.

Push to GitHub

Writes the accepted checkpoint into a repository you connected: a branch named vibld/<revision>, one commit carrying the generated files, and a pull request against the repository’s default branch. It opens a pull request rather than committing to your default branch, because a generated change is a change to review.

Two things about the access it uses:

• It is scoped to the single repository you approved. The token minted for a push names that repository explicitly, so it cannot reach the rest of an installation even if the installation covers more.
• The grant expires after 90 days. A revoked or expired grant blocks new pushes and keeps its record rather than vanishing, so the history of what was authorised stays readable.

A push is safe to retry. The parent commit and the commit timestamps are recorded before the first call that could succeed without reporting back, so retrying a checkpoint produces the identical commit rather than a second one.

Publish

Builds the accepted checkpoint and serves it at a vibld URL. Unlike a sandbox, it is not a dev server on a timer: it is the built output, which is what you want when somebody needs to look at it tomorrow.

Publishing is still vibld hosting your project. If you want it on your own domain and your own account, export it or push it and deploy from there.

What you own

What vibld generates for you is yours. The terms covering the vibld core itself, the starter templates, and what you build with it are set out on the Open-Source Notices page, which is the authoritative statement rather than this summary.