Our thresholds were wrong for everyone. Now you write them.

We shipped custom recommendation policies.

You set it. Pick the resources you care about, pick the metric to watch, set your threshold and the time window, and tell Zopnight what to suggest when it gets crossed. A few clicks, no YAML, no support ticket.

You pick the action, not just the alert. Stop something that's idle, schedule it off during quiet hours, or remove it if you're done with it. The recommendation shows up with the fix already attached.

Spikes count, not just averages. Averages hide things. A rule like "flag anything whose CPU ever crossed 80%" works now, so a short burst at 3am doesn't get smoothed away into looking healthy.

Still gated. Every custom recommendation explains why it fired, shows the savings you can expect, and warns you before you switch off anything critical like a database. Nothing moves until a human says yes.

Your rules sit right beside our built-in ones and behave identically. Same explanation, same one-click fix.

Why we bothered: our thresholds were ours. One team's idle is another team's batch job, and we kept tuning a number that was never going to be right for everybody. Handing over the knob was cheaper than guessing, and the rules people write themselves are the ones they actually act on.

You can poke at it in the Playground, no login needed: https://zop.dev/zopnight/playground

Curious where you land on this one. Do you ship opinionated defaults and defend them, or open up config early and let users build their own rules?