Skip to main content
Shipping a change on Hiveku is one click (or one sentence). Here’s how to deploy, what happens behind the scenes, and how to roll back if something goes wrong.

Easiest

Click the Deploy button

Conversational

Ask the AI

For developers

Push to GitHub

​
Option 1: Deploy Button

1

Click Deploy

In the top bar of the Editor, click the Deploy button.
2

Pick the environment

Usually Production. For staging deploys, pick Staging from the dropdown.
3

Watch the status

The button shows progress — Building, Deploying, Live — usually under two minutes.

​
Option 2: Ask the AI

From the AI chat, just say: 
Deploy to production

Push the latest changes live
The AI confirms what will be deployed and kicks off the build. Great when you’re already in a chat and don’t want to switch contexts.

​
Option 3: Auto-Deploy on GitHub Push

If your project is connected to GitHub, every push to your default branch triggers a deploy automatically.
Auto-deploy is on by default for GitHub-imported projects. You can toggle it in Settings > Deployment.

​
What Happens When You Deploy

1

Build

Hiveku runs your build command (next build, npm run build, etc.) in an isolated container.
2

Push to CDN

Successful builds get uploaded to the global CDN.
3

Update routing

DNS and routing update to point at the new version.
4

Live

Your site is live. Full deploys typically finish in under two minutes.

​
Your Live URL

Your site is always reachable at: 
https://{project}.hiveku.com
If you’ve attached a custom domain, it’s live there too. See Custom Domain.

​
Deployment Status

StatusMeaning
QueuedWaiting for a build slot
BuildingRunning your build command
DeployingPushing to the CDN
LiveYour change is visible
FailedBuild or deploy errored (previous version still live)
A failed deploy never takes down your live site — the previous version stays up until a new deploy succeeds.

​
Deployment History

Every deploy is saved. View history from Settings > Deployment > History. Each entry shows:
  • Timestamp and who triggered it
  • Git commit or change summary
  • Build logs
  • Status and duration
  • A Rollback action

​
Rolling Back

1

Open Deployment History

Go to Settings > Deployment > History.
2

Find a healthy deploy

Scroll to the last successful deploy from before the problem.
3

Click Rollback

Hiveku restores the files from that deploy into your working tree.
4

Redeploy

Click Deploy to push the rolled-back version live. Your live site returns to that earlier snapshot.
Rollback restores files into your working project — it doesn’t instantly swap the live site. You need to deploy after rolling back.

​
Verifying the Deploy

After the status shows Live:
  1. Open your site URL in a new tab (https://{project}.hiveku.com)
  2. Hard-refresh with Cmd+Shift+R (Mac) or Ctrl+Shift+R (Windows) to bypass browser cache
  3. Spot-check the page you changed
  4. Check the console for errors

​
Troubleshooting

Open Settings > Deployment > History and click the failed entry for build logs. Common causes: missing env var, TypeScript error, a package that needs installing. You can also paste the error into the AI chat: “My deploy failed with this error — can you fix it?”
Open the browser console (right-click > Inspect > Console) and look for errors. Often a missing env var (NEXT_PUBLIC_ vars need to be set before build) or a client-side error. Ask the AI to investigate — paste the console output into chat.
Hard-refresh the page (Cmd+Shift+R / Ctrl+Shift+R) to bypass your browser cache. CDN propagation usually finishes within seconds of the Live status.
DNS propagation can take up to 48 hours (usually much faster). Run your domain through dnschecker.org to confirm. See Custom Domain for the full checklist.
A previous deploy may be stuck. Open deployment history, cancel the queued ones, and try again. If it persists, contact support — there may be a platform issue.

​
What’s Next?

Custom Domain

Point your domain at the site

Environment Variables

Configure secrets and settings