Kentico’s SaaS infrastructure is designed to minimize downtime as much as possible, but downtime can occur under certain conditions, mainly for safety and data integrity reasons.
When Downtime Might Occur
- Schema Changes
- Adding or removing fields, content types, or altering structure in ways that affect the database schema.
- These typically trigger a brief maintenance window and may result in temporary downtime (10–30 minutes).
- Database-Level Changes
- Complex operations such as data migrations or structural changes to stored content.
- Triggers backups, consistency checks, and may require exclusive locks on resources, leading to longer downtime.
- Project Upgrades or New Version Rollouts
- If a deployment includes upgrading the core Xperience libraries or services, downtime may occur while the system restarts and migrates internal state.
- Manual SaaS Environment Reprovisioning
- When environments are manually reprovisioned or reset, either by support or advanced DevOps triggers.
When Downtime Is Unlikely (Safe for Daytime Deployments)
- Pure frontend changes (e.g., Razor/React/HTML/CSS updates).
- Adding or updating widgets, page templates, or views.
- Updating localization strings or styling.
- Adjustments in webhooks or content staging settings.
- Deployment of content changes only (via API or Xperience Admin).
Best Practices to Minimize or Avoid Downtime
- Bundle Structural Changes Together
- Avoid many small schema changes across multiple deployments. Group them if possible.
- Use Previews/Staging to Test
- Verify schema changes on staging environments before applying to production.
- Coordinate with Kentico Support
- For large changes, you can request scheduled downtime or get insight into the estimated duration.
- Deploy with Smart Windows
- If you don’t know whether your deployment causes downtime, aim for late evenings or early mornings until confident.