Integrations & Workflows

Plug FinOps Co-Pilot
Into How Your Team Operates

GitHub for pre-merge governance, Slack and Teams for approvals, CLI and VS Code for developer feedback, and event delivery for everything else.

GitHub PR Comment
+$3,100/mo
High risk. Blocking policy triggered for staging cost threshold.
Comment upsertPolicy result
finops estimate
terraform plan -out plan.tfplan
finops estimate plan.json → projected delta +$113.20/mo before PR creation
Event Delivery
finding.created → PagerDuty
Signed webhook delivered with retry and dead-letter safety.
Org-WideGitHub App rollout
CLI + IDEDeveloper feedback loops
Slack / TeamsApproval workflows
WebhooksEventBridge + Pub/Sub

GitHub at Org Scale

Install once, then bring cost governance into every repository that ships Terraform.

FinOps Co-Pilot supports both GitHub App installation and workflow-driven automation, so teams can choose between zero-YAML rollout and custom CI control.

  • GitHub App installs once at the organization level for automatic PR cost analysis
  • PR comments include monthly delta, risk score, policy result, budget impact, tagging compliance, and estimate confidence
  • Comment upsert keeps one evolving review thread instead of spamming every push
  • GitHub Actions remains available for teams that want custom workflow YAML and pipeline-level control
Install ModelOrg-wide GitHub App or custom GitHub Actions workflow
TriggerTerraform and HCL pull requests with automatic webhook analysis
OutputPR comment with cost delta, risk, policy result, and budget posture
Review MotionAdvisory findings or blocking enforcement before merge

Developer Tooling in Local Workflows

Catch cost impact before a pull request even exists.

The open-source FinOps CLI and VS Code extension move cost awareness closer to where engineers write and review infrastructure.

  • Run finops estimate locally against Terraform plan JSON for fast feedback
  • Use the same CLI in GitHub Actions, GitLab CI, Jenkins, or any custom pipeline
  • Access a public pricing endpoint for lightweight, unauthenticated cost estimates
  • Surface inline Terraform cost hints in VS Code while engineers are still editing
CLILocal estimates, CI/CD integration, plan-file based analysis
VS CodeInline monthly cost hints directly in Terraform authoring workflows
CI TargetsGitHub Actions, GitLab CI, Jenkins, and generic pipelines
BenefitShift cloud cost review from “after merge” to “while writing code”

ChatOps Approvals and Team Routing

Approve, reject, and triage cost actions without leaving Slack or Microsoft Teams.

FinOps Co-Pilot turns communication channels into governed operations surfaces for remediation approvals, commitment reviews, and anomaly response.

  • List pending actions with /finops pending
  • Approve or reject requests directly from Slack or Teams
  • Route alerts, weekly digests, and approval cards to the right operating channels
  • Create downstream tickets for Jira, Linear, or incident systems from high-severity findings
/finops pendingList all pending approvals in the active workspace
/finops approve <id>Approve a remediation or commitment request
/finops reject <id>Reject a request with context or notes
/finops helpShow available ChatOps commands and usage

Production-Grade Event Bus

Push FinOps signals into the rest of your operating stack with reliable delivery guarantees.

Every high-value workflow in FinOps Co-Pilot can emit events for ticketing, alerting, warehousing, and custom automations.

  • Delivery targets include HTTPS webhooks, AWS EventBridge, and GCP Pub/Sub
  • Event types cover findings, approvals, remediation execution, commitment purchases, and spend ingestion
  • Transactional outbox, exponential backoff, and dead-letter handling protect delivery reliability
  • HMAC-SHA256 signing keeps every outbound subscription verifiable and tamper-evident
AlertingPagerDuty or incident tooling for anomalies and budget breaches
TicketingJira or Linear issue creation for high-severity findings
Data FlowsCustom dashboards, warehouses, and internal FinOps reporting pipelines
SecurityPer-subscription signing secrets with replay-resistant delivery patterns

What You Can Route Out of the Platform

Use the event layer to feed ticketing systems, incident response, internal dashboards, or downstream automation.

  • Finding created, prioritized, or status changed
  • Approval requested, approved, rejected, or expired
  • Remediation queued, completed, failed, or skipped
  • Commitment strategy planned, approved, executed, or simulated
  • Spend ingestion completed with freshness and error posture
  • Budget threshold or policy violation triggered

Start Where Your Team Feels the Pain First

FinOps Co-Pilot does not force a single adoption path. Roll out through PR review, developer tooling, ChatOps, or platform events depending on where cost friction is already slowing your team down.

PR Governance First
GitHub App + policies
Start with PR Cost Diff, budget guardrails, and advisory or blocking enforcement before teams deploy anything new.
Ops Velocity First
Slack / Teams + approvals
Wire ChatOps into remediation and commitment workflows so operators can approve savings actions without dashboard hopping.
Developer Experience First
CLI + VS Code
Move feedback left with local Terraform estimation, pipeline integration, and inline editing hints for infrastructure teams.
Platform Integration First
Webhooks + EventBridge + Pub/Sub
Stream FinOps events into PagerDuty, Jira, warehouses, and custom automation so cost signals reach the rest of your platform stack.

Wire Cost Intelligence Into Your Existing Stack

Start with GitHub, expand into ChatOps, and connect the event bus when you are ready for fully governed FinOps workflows.