Connect cost spikes to the events that caused them
When cloud costs spike, teams scramble to answer: “What changed?”Often the root cause is known — a deployment, new region, or event like Black Friday — but there’s no structured correlation between these events and the cost data.
Costory ingests technical and business events and aligns them with cost timelines.Supported inputs include:
AWS commercial events (SPs, RIs, EDP renewals)
GitHub metadata (PRs, deploys, labels)
CI/CD pipelines (custom events via API)
Manually created events (e.g., traffic spikes, client onboarding)
All events are timestamped and visualized alongside cost time series.They also improve the accuracy of Digest summaries and ML-driven anomaly detection.