---
title: Maintenance window
description: Apply platform updates during a scheduled weekly time slot instead of immediately as they are released.
hidden: true
---

<Note>

Available on the [Enterprise plan](https://cube.dev/pricing) with the
[Single-tenant infrastructure](/admin/deployment/infrastructure#dedicated-infrastructure)
add-on.

</Note>

Cube can apply platform updates to your infrastructure during a scheduled weekly
time slot instead of immediately as they are released. This gives you control
over **when** updates happen, reducing the risk of unexpected changes during
peak hours.

## How it works

Cube automatically takes daily snapshots of all current service versions. Each
snapshot captures a consistent, known-good combination of service versions at
that point in time.

A snapshot must be at least **24 hours old** before it becomes eligible for
deployment. This ensures that only versions confirmed stable in production are
promoted to tenants with a maintenance window enabled.

During the configured maintenance window, the system automatically advances your
deployment to the latest eligible snapshot. Outside of the window, no updates
are applied.

<Info>

You do not choose specific versions. The system manages version progression
automatically — the maintenance window only controls **when** the update
happens.

</Info>

## What gets updated

The maintenance window applies to all services for your deployment, including:

- **Control-plane services** — the infrastructure serving the Cube UI, API, and
  orchestration.
- **Data-plane services** — the infrastructure responsible for query execution,
  builds, and worker lifecycle in single-tenant regions.

Both control-plane and data-plane services are updated to the same snapshot
during the window.

## Configuration

Go to **Admin → Settings → Maintenance Window**:

<Frame>
  <img
    src="https://ucarecdn.com/e6db33a7-0d5e-4e28-8494-554393eaf2cb/"
    alt="Maintenance window settings"
  />
</Frame>

1. Toggle **Enable Scheduled Maintenance Window** to on.
2. Select the **Day of week** (e.g., Sunday).
3. Select the **Time (UTC)** — the hour when the update window opens (e.g.,
   02:00 UTC).

Settings are saved automatically.

<Warning>

The maintenance window spans **one hour** starting from the selected time. For
example, selecting 02:00 means updates may be applied between 02:00 and 02:59
UTC on the selected day.

</Warning>

When you enable the maintenance window for the first time, the day defaults to
**Sunday** and the time defaults to **02:00 UTC**. Your deployment is
immediately assigned the latest eligible snapshot so that it starts from a
known, stable version.

## Active version

When the maintenance window is enabled and your deployment has been updated at
least once, an **Active Version** section appears below the schedule settings.

The **Active Version** dropdown shows all snapshots that were active for your
deployment within the last 7 days. The currently active snapshot is pre-selected
and marked with `(current)`. To switch to a different version, select it from
the dropdown. The change takes effect on the next reconciliation cycle.

<Warning>

Only snapshots from the last 7 days are available. If you need to revert to an
older version, contact [support](/admin/account-billing/support).

</Warning>

## Upgrade now

If a critical fix has been released and you don't want to wait for the next
scheduled maintenance window, you can upgrade to the current production versions
immediately.

When the maintenance window is enabled, an **Upgrade Now** section appears at
the bottom of the settings page. Click **Upgrade Now** to create a snapshot from
the service versions currently running in production and switch your deployment
to it right away. The button is disabled while the upgrade is in progress. Once
complete, the new version will appear in the **Active Version** dropdown.

<Info>

Unlike the scheduled maintenance window, **Upgrade Now** does not require a
24-hour eligibility buffer — it always uses the versions running in production
at the time you click the button. If your deployment is already running those
versions, the button will return an error.

</Info>

## FAQ

### What happens if I disable the maintenance window?

Your deployment returns to the default behavior — receiving updates immediately
as they are released.

### What if no new snapshot is available during my maintenance window?

Nothing happens. The system only advances your deployment if a newer eligible
snapshot exists. If you are already on the latest eligible snapshot, the
maintenance window is a no-op.

### How far behind the latest release will my services be?

At most, your services will be behind by the interval between your maintenance
windows (typically one week) plus the 24-hour eligibility buffer. For example,
with a Sunday 02:00 UTC window, your services could be up to ~8 days behind the
latest release in the worst case.

### Can I roll back to a previous version?

Yes. When the maintenance window is enabled, the settings page shows an **Active
Version** dropdown listing all snapshots from the last 7 days. Select any of
them to switch back. See [Active version](#active-version) above for details.

### Can I trigger an immediate upgrade without waiting for the window?

Yes. Use the **Upgrade Now** button on the settings page to upgrade to the
current production versions immediately, without waiting for the 24-hour
eligibility buffer. See [Upgrade now](#upgrade-now) above for details.
