How to deploy
- Click the Deploy button in the top toolbar
- Or type “deploy my site” in the AI chat
What happens during deployment
1
Build
Hiveku runs your build process (if configured) and prepares the output files.
2
Publish
The built files are pushed to the hosting infrastructure.
3
CDN update
The global CDN cache is invalidated and updated with your new files.
4
Live
Your site is live at its URL with the latest changes.
Deployment status
Pre-deploy GitHub sync
When your project is connected to GitHub, every deploy starts with a quick reconciliation against the GitHub branch you’re deploying from. This guarantees the build matches what’s on GitHub right now. Three outcomes are possible:
The third case is rare in practice because AI session edits auto-commit to GitHub at the end of each chat session. The only way to reach a real conflict is to edit a file in Hiveku and edit the same file outside Hiveku (e.g. via VSCode) before either side commits.
For projects without GitHub connected, this step is skipped entirely — the database is already the source of truth.
Deployment history
Every deployment is recorded with a timestamp, status, and the user who triggered it. Open the Deployments tab in the hosting dashboard to browse the full history.Changes since last deployment
The deployment panel shows a summary of files that have been added, modified, or deleted since the last deployment. Review these changes before deploying to make sure everything looks right.Rolling back
If a deployment introduces a problem, you have two ways to roll back depending on the scope:Project-wide rollback (recommended for broken deploys)
Every deployment is anchored to a checkpoint Hiveku creates right before the deploy started. To restore the entire project to the state it was in before that deploy:1
Open the Hosting page
Navigate to Hosting. The Checkpoints section lists every checkpoint, with the one tagged
pre-deploy matching each deployment.2
Restore the pre-deploy checkpoint
Click Restore on the checkpoint that was created just before the problematic deployment. Hiveku snapshots your current state as a safety backup first, then restores all files and assets to that point.
3
Redeploy
Click Deploy again to publish the restored files as a new deployment.
Single-file rollback
If only one or two files are causing problems, use per-file version history instead — it’s faster:1
Open version history
Go to the file tree, right-click the affected file, and select Version History.
2
Restore the file
Browse to a previous version and restore just that file.
3
Redeploy
Click Deploy again to publish the restored file as a new deployment.
Rollbacks create a new deployment rather than reverting to an old one. This means your deployment history always moves forward, making it easy to audit what happened and when.