> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hiveku.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Versions

> Hiveku saves versions of your pages as you work. Go back to one, bring back a single page, preview an old version, or start a branch from it.

A **version** is a saved copy of your pages that you can go back to. Your site and every [branch](/editor/branches) keep their own versions, and Hiveku saves them for you as you work.

Versions hold your site's code and pages. Images, uploads and the database are not in versions: [Project history](/editor/project-history) restores those.

<Note>
  AI tools use developer words for the same things: a version is a commit, and Your site is `main`. The tools are `project_vcs_commit`, `project_vcs_history` and `project_vcs_rollback` (see [Branches and AI tools](/editor/branches-and-ai)).
</Note>

## How versions are saved

Every save lands at once, and the preview and the AI see it right away. Until it is in a version, it shows as **Latest changes**.

Hiveku turns your latest changes into a version on its own:

* **When you pause.** Three to six minutes after your last edit, your changes are saved as a version (Hiveku checks every three minutes for three quiet minutes). The timeline says "Editing now" and "Saved as a version when you pause" while you work.
* **During long sessions.** While editing goes on without a pause, a version is saved every half hour.
* **Before a step you may want to undo.** These versions are marked with why they were saved:

| Mark | Saved |
| - | - |
| Saved automatically before publishing | Before Your site is published |
| Saved automatically before merging | Before a branch is merged in |
| Saved automatically before starting a branch | Before a branch is started from Your site (started from another branch, the version is named "Editor changes (before branching)") |
| Saved automatically before switching branches | Before the editor moves to another branch |
| Saved automatically before going back | Before a rollback |
| Saved automatically before going back to an earlier point | Before a restore from Project history |
| Saved automatically before an AI request / after an AI request | Around each AI chat request |
| Saved automatically before bringing in changes from GitHub | Before a GitHub pull |

While an AI request is running, the automatic save waits, so a version never cuts a request in half.

### Save a version yourself

**Save as a version** in the branch selector, or in a branch's side panel on the **Branches** tab, saves your latest changes now.

* **Name (optional)**: leave it empty and Hiveku names the version from what changed, for example "Edited the Home and Contact pages" or "Changed site styles". A name you type can be up to 500 characters.
* On Your site the dialog reminds you: "Visitors don't see this until you put it on the live site."
* If nothing changed since the last version, it says "These changes are already saved as a version." instead of saving an empty one.

When it is saved: `Saved "Edited the Home page" as a version.`

<Tip>
  Name a version yourself when you reach a state you would want to come back to, such as "Before the redesign". The automatic versions keep you safe; named ones make the history easy to read.
</Tip>

## Find a version

Open the **Branches** tab and select Your site or a branch. Its side panel lists its newest versions (eight for Your site, five for a branch) and **See all *n* versions** for the rest.

Each version shows when it was saved and who saved it: a person's name, **Hiveku AI**, the name of the connected AI tool, or **A connected tool**. Some carry a mark that says what happened:

| Mark | What it means |
| - | - |
| **Merged "*branch*"** | A branch was merged in |
| **Rolled back to "*name*"** | Your site or the branch went back to an earlier version |
| **Saved automatically** | Saved on its own (see the marks above) |
| **Starting point** | Where the branch started |
| **Matched to the published site** | Hiveku lined Your site up with what was live |
| **Recreated from a backup** | Rebuilt from an older backup |

Your site's first version is named "Project created".

Click a version to open it. Its **What changed** section has two views:

* **In this version**: what this version changed compared with the version before it, with a side-by-side view for each file.
* **Compared with now**: what is different between this version and the site as it is now.

Hiveku began keeping versions on 27 September 2026 and turned the recent history before then into versions marked **Recreated from a backup**. For anything older, use [Project history](/editor/project-history).

## Go back to a version

Open a version and click **Roll back to this version**: "Adds a new version that matches this one. Newer versions stay, so you can undo it."

The confirm says what happens:

* Which version it goes back to, and when that was saved.
* "Your latest changes are saved as a version first."
* How many later versions it undoes, for example "The changes from 2 later versions are undone.", and that those versions stay in the timeline.

On Your site, the confirm also has **Also put this version on the live site now**, ticked by default:

* Ticked, the button reads **Roll back and put it live**, and "Visitors see it in a few minutes."
* Unticked, "Visitors keep seeing the current live version until you publish."
* A site that publishes from GitHub is not put live from here. Publish it from the **Deploy** menu once GitHub has it.

When it is done: `Rolled back to "Launch".`

<Warning>
  Images and uploads stay as they are: versions do not hold them. To put images and data back too, use [Project history](/editor/project-history). On a branch, images and uploads are shared with Your site, so a branch's rollback never changes them.
</Warning>

Other ways back, from a version's menu:

* **Undo this rollback**: "Goes back to how it was just before this rollback. Nothing is lost."
* **Roll back to before "*branch*" was merged**: on a merge, goes back to the version just before it.
* **Go back to this version**: on the newest version, when there are latest changes after it: "Your latest changes are saved as a version first, then this version comes back."

A rollback waits while Hiveku AI is working on the site: "The AI is working on this site right now. Wait for it to finish, then roll back." If someone saves a new version while you decide, nothing goes back: "A new version was saved while you were deciding, so nothing has gone back yet. Check the list again and confirm." If a rollback stops part way, **Try again** finishes it.

## Bring back one page

When a version changed a page you want back, you do not have to roll back everything. Open the version, find the page under **What changed**, and click **Bring back this page** (**Bring this back** for a part that is not a page, such as site styles): "Puts it back as it was in this version, as a new version. Nothing else changes."

For a page the version added that you want gone again, the same place offers **Remove it again**. You can bring back up to 50 files at once; for more, roll back the whole version.

## Preview an old version

**Preview this version** "Opens a private copy of the site as it was then. Your site is not changed." It takes 30 to 60 seconds to start, and opens in its own window. A version preview counts toward the project's five running previews (see [Branch previews](/editor/branches#branch-previews)).

## Start a branch from a version

**Start a branch from this version** "Starts a new branch with the files of this version." The **New branch** dialog says where it starts, for example `Starts from "Launch" on Your site`. Give the branch a name and click **Start branch**: `Started "spring-sale" from "Launch".`

## Share a version

**Copy link to this version**: "Anyone on your team with the link can open this version."

## Undo an AI request

In the AI chat, each request is marked "Before this request" with **Undo this turn**, which goes back to the version saved before the request. See [Undo an AI turn](/ai/undo-turn).

## Versions, restore points and backups

Hiveku has a few ways back. They cover different things:

| | What it brings back | Where | Works on |
| - | - | - | - |
| **Version** | Your pages and code | **Branches** tab | Your site and every branch |
| **Restore point** | Pages, images and data, to a moment in time | [Project history](/editor/project-history) | Your site |
| **Earlier copy** | One file | The code editor's **History** button | Your site |
| **Backup** | Files, assets and the database | **Hosting › Backups** | The whole project |
| **Deployment History rollback** | Your project files, as of an earlier deploy (deploy again to put them live) | **Hosting › Deployment History** | The whole project |
| **Instant rollback** | Which earlier build one environment serves, at once, without a rebuild | The Hosting page, under Deployment History | One environment |

## Who can do what

People who can see deployments (**Websites › Deployments: View**) can look at versions. Saving, rolling back, bringing back a page and previews need **Websites › Deployments: Manage**. Without it, Hiveku says: "You can look at versions, but only people who can publish can change them." See [Permissions](/settings/permissions).

## From AI tools

* `project_vcs_commit` with no files saves the latest changes as a version (`409 nothing_to_commit` when there is nothing new). With files, it writes them and saves a version in one step.
* `project_vcs_history` lists versions, newest first, with who saved each and which environments run it.
* `project_vcs_rollback` goes back to a version. It runs as a dry run by default. Applying it on Your site needs `expected_head_commit_id` from the dry run, so it never undoes a version saved while it was deciding. Send it on a branch too: without it, a repeated request can roll the branch back twice.
* The Claude Code plugin has `/hiveku:commit`, `/hiveku:history` and `/hiveku:rollback`, and VS Code has **Hiveku: Save a Version**, **Hiveku: Show History** and **Hiveku: Go Back to a Version…**.

See [Branches and AI tools](/editor/branches-and-ai) for the whole list.

## Common questions

<AccordionGroup>
  <Accordion title="Does rolling back change my live site?">
    Only if you tick **Also put this version on the live site now** on Your site. Otherwise visitors keep seeing the live version until you publish.
  </Accordion>

  <Accordion title="Are images rolled back with a version?">
    No. Versions hold pages and code. Use Project history to bring back images, uploads or data.
  </Accordion>

  <Accordion title="Can I undo a rollback?">
    Yes. A rollback adds a new version and keeps the newer ones. Open the rollback's version and click **Undo this rollback**.
  </Accordion>

  <Accordion title="Why didn't my change make a new version?">
    Hiveku saves a version when you pause, or when you click **Save as a version**. If nothing changed since the last version, there is nothing new to save.
  </Accordion>

  <Accordion title="How far back can I go?">
    Versions go back to 27 September 2026, plus the recent history before then that Hiveku turned into versions. For earlier moments, use Project history.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.