After-Hours Resource Governance

Dev Resources Don't Need
to Run at 3am.

Clusters left running overnight. Warehouses idling all weekend. Platform teams set allowed schedules once. Kostavo scans continuously and stops resources running outside their window.

Start Free Trial

Where After-Hours Waste Comes From

Forgotten Overnight Clusters

A developer spins up an interactive cluster at 5pm and forgets to stop it. It runs all night and through the weekend.

Idle SQL Warehouses

Dev and test warehouses stay running outside business hours with no active queries: pure waste.

Misconfigured Triggers

Pipeline triggers and job schedules firing at unexpected times, running workloads that weren't intended to run off-hours.

Overspend Surfaces Too Late

By the time anyone notices, days or weeks of after-hours compute have already run for nothing.

Schedule Policies. Continuous Scans.

Platform teams define the allowed window for dev and test resources. Kostavo scans continuously. Anything running outside that window gets stopped and the resource owner is notified.

Define Allowed WindowsSet business hours per workspace or resource type. Weekday-only, custom hours, or environment-specific rules.
Continuous EnforcementKostavo scans running resources against the policy. Resources outside their window are stopped automatically.
Pipeline & Schedule PoliciesPolicies for pipeline triggers and job schedules configured to fire outside allowed hours.
Tag-Based ScopeTarget dev and test environments by tag. Production is never touched.
Owner & Admin NotificationsThe resource creator and workspace admins are notified by email when a resource is stopped. Your platform team follows along in Slack or Teams.

Allowed Window: Mon–Fri 8am–7pm

Mon

Tue

Wed

Thu

Fri

Sat

Sun

Allowed window Outside window: resources stopped

Real schedules from the product: business-hours protection on weekdays, 24/7 freeze for production.

Most of the Week is Outside Business Hours

Dev resources running 24/7 means 128 hours a week where no one is working, but you're still paying.

Business Hours

40 hrs/week

24% of the week. The rest is waste if left running

What Kostavo Scans

Interactive Clusters

Detect and stop dev/test clusters running outside allowed hours

SQL Warehouses

Flag warehouses running idle outside business hours

Job Schedules

Scan for jobs configured to trigger outside their allowed window

Pipeline Triggers

Flag Lakeflow Declarative Pipelines with triggers set to fire at off-hours times

How It Works

Platform Team Sets the Policy

Define allowed hours for dev and test workspaces. Tag-based rules target the right environments.

Kostavo Scans Continuously

Running resources are checked against the policy. Anything outside the window is flagged as a violation.

Resources Stopped, Teams Notified

Out-of-window resources are stopped automatically. The resource creator and workspace admins are notified.

Stop After-Hours Waste Today

Connect a workspace and see what dev compute is running after hours.