Connect GitHub for PR Cost Impact

6 min readUpdated June 2026

How it works

Cloptima connects to GitHub as an organization-installed GitHub App with least-privilege access. It reads the workload definitions in a pull request — Kubernetes manifests, Helm values, and related config — calculates the projected monthly cost delta against your cluster's real pricing, and posts it as a comment before merge.

Installed as a GitHub App — no personal access tokens to manage
Reads manifest/Helm/config files in the PR, never your application source
Posts a before/after monthly cost delta with budget context
Optional guardrails can flag PRs that exceed a cost threshold

Access is scoped to the repositories you explicitly grant, and analysis is limited to infrastructure definitions — not application code or data.

Install the GitHub App

From Cloptima Settings → Integrations → GitHub, install the Cloptima app into your organization and select the repositories you want analyzed. You can add or remove repositories at any time.

Map repositories to applications

Relate each repository to the application or team it deploys, so cost deltas attribute to the right owner. This is what powers app-level chargeback when a change drives costs up.

Open a PR and review the comment

Change a replica count, resource request/limit, or add a new workload, and Cloptima comments on the PR with the projected monthly impact and how it affects the namespace or team budget — so the decision happens in code review, not after the invoice.

Optional: enforce in CI/CD

Use the Cloptima CI helper to upload a redacted PR cost-impact artifact and fail builds that exceed policy. The latest run is also available to the console and API for dashboards and audits.