Skip to main content
Bounded by policy

Keep it running.
Just not
forever.

Every scheduling tool has the same failure mode. Someone disables a schedule on a Friday for a release, and nobody re-enables it. An override is the fix: it holds the resource against its schedule, and then it expires on its own.

2directions, on or off
1active override per target
Policycapped duration
3notification events

An exception with an end date.

The expiry is the feature. Everything else is plumbing.

01

Hold it

Force a resource or an entire group on or off, against whatever its schedule says. Overnight testing, a release window, a frozen environment before an audit.

02

Bound it

Every override carries an expiry, capped by an org-wide maximum duration policy. Indefinite is not a value you can pick by accident at five on a Friday.

03

Expire in the right timezone

Expiry is derived from the schedule attached to that resource or group, not from the org default. A team on a Singapore schedule gets a Singapore expiry, which is the only reading that is not surprising.

04

Know it happened

One active override per resource or group, refused at the backend rather than merely hidden in the UI. Set, cleared and expired each raise a notification.

Built for the Friday afternoon.

The details that decide whether a control gets used or worked around.

Scope
Resource level or group level. A group override covers every member without you unpicking the group first.
Conflict handling
One active override per target. The UI prevents the conflict before you submit, and the backend returns a 409 if something tries anyway. Two people cannot fight over the same resource.
Finding them again
Server-side filtering by search, status (active, expired or all), target type (resource or group), and action (keep running or force stop). An override you set last week is findable, not archaeology.
Before you change one
Editing or deleting a schedule opens a blast radius view first: the resources directly attached, the groups expandable to their members, and the monthly cost impact of each. Modify warns. Delete, pause and stop mark as affected.

Make the exception safe to grant.

Overrides expire on their own so your schedules stay meaningful. See it on your own accounts.

Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console·