Events show up as timeline markers in Costory. You can filter by source, category, and labels to explain cost changes in seconds.
Supported event sources
GitHub deploys
Pull request merges, releases, and deployment metadata.
CI/CD pipelines
Post build and deploy events directly from your pipelines.
Custom API events
Send any event that explains spend via the Events API.
Provider events
AWS live; Azure and GCP on the roadmap.
How events work in Costory
- Connect a source (GitHub, CI/CD, or API).
- Categorize events as BUSINESS, TECHNICAL, or PROVIDER.
- Overlay events on cost charts for fast in the Cost Explorer.
- Share context in saved views and Slack reports.
Event categories
Costory groups events into three categories so you can filter consistently across teams:| Category | What it represents | Examples |
|---|---|---|
| BUSINESS | Go-to-market or product events | Launches, pricing changes, marketing campaigns |
| TECHNICAL | Engineering and infrastructure changes | Deploys, incidents, migrations, CI/CD runs |
| PROVIDER | Cloud provider and billing changes | purchases, activations, price changes |
Frequently asked questions
How fast do events appear in Costory?
How fast do events appear in Costory?
GitHub and provider events typically appear within minutes. API events appear as soon as they are accepted by the Events API.
Can I backfill historical events?
Can I backfill historical events?
Yes. Post events with historical timestamps and Costory will place them on the correct date in your cost timeline.
Do events change my cost data?
Do events change my cost data?
No. Events are metadata overlays only. They help explain costs but do not modify billing data.
Can I filter or export events?
Can I filter or export events?
Yes. Use category, label, source, and environment filters in the Events page and in Cost Explorer views.
Next steps
Add Usage Metrics
Combine events with KPIs for full context.
Explore Cost Explorer
See how events drive cost changes in your dashboards.