Skip to main content

Saving & publishing

Studio works a little differently from most "build your site" tools: your project's site is live the whole time you're working on it. Every change the AI makes is visible at your project's web address within seconds. There is no separate "go live" or "deploy" button.

This page covers what does exist around that: saving versions of your work, and (if you've linked GitHub) backing your code up there.

Your site is always live​

The address you saw when you created the project —

https://your-slug.sites.vectrforce.ai

— is your real, public site. Anyone with the link can open it, and it always shows the latest version of your project as the AI has left it. The preview pane inside Studio and that public address point at the same running site.

This is what makes the AI loop feel immediate: you ask for a change, the assistant makes it, and your site updates on the spot.

If you'd like a more memorable address than your-slug.sites.vectrforce.ai, see Custom domains.

Saving a version​

In the sidebar's git section, the Commit button (the git-commit icon) saves a snapshot of your project. Think of it as marking a known-good state: "the site looked like this on Tuesday afternoon, with the new About page in place."

You don't have to commit to keep your site live — your changes are live the moment the AI makes them. Saving a version is about having a clear history you can refer back to. It's useful when:

  • you've finished a meaningful block of work and want to mark a checkpoint,
  • you're about to ask for a big change and want a snapshot to compare against later, or
  • you're about to back up to GitHub (see below).

Behind the scenes, Studio is also auto-saving the AI's work as it goes, so nothing is ever lost between commits — the Commit button is for your checkpoints, the ones you'd want to come back to.

Backing up to GitHub​

If you linked a GitHub repository when you created the project (or added one later), the Push button (the upload icon, next to Commit) sends your saved versions to that repository.

This is a backup: your code is mirrored to GitHub, where you (or a developer working with you) can browse it, clone it, or open pull requests against it. Push doesn't change your live site — it only updates the GitHub copy.

If you didn't link a GitHub repository, you don't need to push. Your project is still safely stored on Studio's servers.

Other controls in the git panel​

The sidebar's git section also has:

  • Pull — bring in changes from GitHub. Useful if someone else has pushed to your repository and you want their work in your project.
  • Hard Reset — discard everything since your last saved version and reset to that state. The site will visibly snap back. Use this carefully; it can't be undone.

Most of the time, you won't need either of these — just Commit when you want to mark a checkpoint, and Push if you're using GitHub.

Next​