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, all under Ship in the top bar, and they do different things. Each acts on the last finished checkpoint: while a new build is still being checked, that is the one before it.

Export

Downloads the 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.

It needs no account, including yours, and works the same on the hosted service and on your own copy.

Push to GitHub

Each project pushes to a repository of its own. The first push from a project offers two choices, both through a GitHub sign-in:

• Create a new repository, named from the project (you can change the name) and private unless you untick it, on your own GitHub account.
• Use an existing repository, from the ones the vibld GitHub App can reach and you can push to.

A push writes the checkpoint as a branch named vibld/<revision>, one commit carrying the generated files, and a pull request against the repository’s default branch.

Disconnect on a project stops that project pushing there and touches no other project, even one using the same repository. Disconnect GitHub in the settings menu ends every project’s connection and the sign-in. Duplicating or remixing a project does not copy its repository.

The access it uses:

• It is scoped to the single repository the project uses. 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 its record is kept.

A push is safe to retry: retrying a checkpoint produces the identical commit rather than a second one.

Publish

Builds the checkpoint and serves it at the project’s own address, <slug>.vibld-preview.dev. Unlike a sandbox, it is the built output, not a dev server on a timer. Each project has its own site, and deleting the project takes its site down. Images and fonts the build itself emits are not published yet; files from your media library are.

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

Everything else a project holds, from its earlier checkpoints to its conversation, and how each part comes out, is on Data portability.

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.