Costory includes a connector for GitHub, enabling us to write insights or metadata to your repositories or issues. While the technical connection is live, we’re still actively exploring the best ways to integrate cloud cost data into GitHub workflows.
Why This Matters
GitHub is where product and engineering work happens. We believe there’s strong potential to surface cost signals closer to the code — but we want to make sure we do it right.
We’re experimenting with use cases where:
Cost anomalies become tracked engineering issues
Optimization tasks are auto-suggested and linked to services or teams
Cost insights are attached to relevant PRs, workflows, or repo-level dashboards
Looking for Input
If your team uses GitHub as a core part of engineering operations, we’d love to learn from your workflow.
We’re especially looking to collaborate with teams on:
Turning cost changes into GitHub issues for triage or resolution
Linking cost data to specific services, repos, or workflows
Embedding usage or savings context into pull requests or CI pipelines
Let’s build it right, not just fast.
Get in touch via Intercom to share how you’d like to see Costory and GitHub work together.