Skip to main content
Everything you changed in the builder is saved, but visitors only see it after you publish. Publishing takes a few minutes, and your current live site stays up the whole time. In this example we publish all the Northwind changes from this series: the new headline, the readable menu, the new sentence, and the FAQ page.

​
Publish to your live site

1

Click Deploy

Click Deploy at the top right of the builder. A small dot on the button means at least one environment, such as Development, does not have your latest changes yet.
The Deploy button outlined at the top right of the builder

The Deploy button

The builder with the Deploy button outlined at the top right

Where Deploy is in the builder

Clicking Deploy only opens a menu. Nothing is published yet.
2

Find Production in the menu

The menu lists your site’s environments:
  • Production is your live site, the one visitors see.
  • Development is a separate copy of your site, for checking changes before they go live.
  • Staging also appears if you have turned it on for this site.
Each row shows how many files have changed since that environment was last updated (here, 13 files changed) and its web address.
Publishing to Production needs a paid plan. On the free plan the row says Paid feature. Upgrade to deploy production.
The Deploy menu with Development and Production rows, each showing files changed and a Deploy button; Production's Deploy is outlined

The Deploy menu, with Production's Deploy button outlined

3

Click Deploy on the Production row

Click Deploy in the Production row. Publishing starts right away. There is no extra confirmation.
The builder with the Deploy menu open at the top right over the Northwind preview

The whole builder with the Deploy menu open

Deploy All publishes to every environment at once. Use the Production row when you only want to update your live site.
4

Follow the progress

The row shows a progress bar with each stage, such as Queued…, Building… and Deploying…. You can close the menu and keep working. The Northwind publish took about four minutes.
The Production row with a green progress bar and the word Building

Publishing in progress

5

Check that it is live

When it finishes, the row says Live! for a moment, then Up to date, with the address of your live site.
The Production row with a green dot and Up to date

Production is up to date

6

Open your live site

Click the open-site icon (the square with an arrow) in the Production row to open your live site in a new tab. Every change from this series is now there:
The live Northwind Coffee Roasters home page with the new headline, the readable menu and the new sentence

The live Northwind site after publishing

Each publish also saves a restore point of your site as you published it, so you can come back to that moment from Project history. See Undo a Change.

​
If something goes wrong

If a publish cannot finish, the row says Build failed, with a link to the logs, and offers Retry and usually Ask AI to fix, which hands the problem to the AI chat. If Hiveku refuses a publish before building, the row says why and offers the button that fixes it. Most failed publishes stop before anything reaches your live site, so visitors keep seeing the version they had. See Deployments for more.

​
More about publishing

​
What’s next

You have opened your site, changed it with the AI and by hand, added a page, checked it on a phone and a tablet, undone a change, and published. Some good next steps:

Post a blog

Publish a new blog post three ways.

Try changes on a branch

Work on a bigger change without touching your live site.