Upgrades
Move to new releases safely, and roll back if something goes wrong.
Updated August 28, 2026
Upgrades are designed to be boring: pull newer images, recreate the containers, keep the data volumes. Your projects, knowledge bases, and license are preserved across upgrades.
Standard upgrade
- Take a fresh backup (see Backup & restore).
- Re-run your install command — it detects the existing install and upgrades it — or pull the latest images and recreate containers with Docker Compose.
- Verify with the health check and confirm the new version at
/api/version.
Database migrations
Schema migrations run automatically on startup and are designed to be forward-safe. The pre-upgrade backup is your safety net — take it every time.
Rolling back
- Stop the application services.
- Start the previous image version.
- If the newer release migrated the schema, restore the pre-upgrade database backup as well.
Running CrestBid for a team and need zero-downtime upgrades or high-availability patterns? Those are documented for Enterprise deployments — contact sales.