OneCloud

Anomalies

Catch the 2am cost spike
automatically.

Combine AWS Cost Anomaly Detection with OneCloud’s own rules engine to catch sudden egress surges and runaway services. Slack, email, and Webhook alerts trigger the moment something moves.

Learn the “normal,”
then surface only the spikes

Learn baseline patterns by service, account, and region, then flag statistically significant moves. Weekday/weekend and month-start/end seasonality are learned automatically to reduce false positives.
Request a demo

An anomaly is an alert,
and an alert comes with evidence

Every anomaly ships with “which service moved how much vs. baseline” and the top contributing resources/tags as line-item evidence — into Slack, email, or Webhook. AWS Budgets and GCP Pub/Sub events join the same routing.
Alerts guide

Detection

Two detection engines in tandem

AWS’s ML-based detection paired with OneCloud’s rules engine — comprehensive, but not noisy.

ML

AWS Cost Anomaly Detection

Pull AWS’s ML-based anomalies (GetAnomalies) straight into OneCloud alerts and reports.

Rules

Custom rules engine

Compose thresholds (>$X), growth (>30% WoW), new-service events, and egress-share rules without writing code.

Routing

Slack, email, Webhook

Split routing per anomaly — infra to Slack #cost-alerts, finance to email, automation to Webhook.

Evidence

Line-item evidence

Every alert attaches the line items that contributed most. “Why was I paged?” is immediately visible.

Sensitivity

Per-team sensitivity

Tune sensitivity and learning windows per team or environment. Production and sandbox don’t share the same alerts.

Triage

Acknowledge & note

Mark each anomaly as acknowledged, resolved, or ignored, with notes — so context survives into the next close.

Start anomaly detection, free

Rule-based anomaly detection with Slack and email alerts is included with Starter.