Integrations
Plug Varcio 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.
High risk. Blocking policy triggered for staging cost threshold.
terraform plan -out plan.tfplanfinops estimate plan.json → projected delta +$113.20/mo before PR creationfinding.created → PagerDuty
Signed webhook delivered with retry and dead-letter safety.
- GitHub App rollout
- Org-wide
- Developer feedback loops
- CLI + IDE
- Approval workflows
- Slack / Teams
- EventBridge + Pub/Sub
- Webhooks
GitHub at org scale
Install once, then bring cost governance into every repository that ships Terraform.
Varcio 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 model
- Org-wide GitHub App or custom GitHub Actions workflow
- Trigger
- Terraform and HCL pull requests with automatic webhook analysis
- Output
- PR comment with cost delta, risk, policy result, and budget posture
- Review motion
- Advisory 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
- CLI
- Local estimates, CI/CD integration, plan-file based analysis
- VS Code
- Inline monthly cost hints directly in Terraform authoring workflows
- CI targets
- GitHub Actions, GitLab CI, Jenkins, and generic pipelines
- Benefit
- Shift 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.
Varcio 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 pending- List 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 help- Show 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 Varcio 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
- Alerting
- PagerDuty, Opsgenie, or incident tooling for anomalies and budget breaches
- Ticketing
- Jira or Linear issue creation for high-severity findings
- Data flows
- Custom dashboards, warehouses, and internal FinOps reporting pipelines
- Security
- Per-subscription signing secrets with replay-resistant delivery patterns
Event signals
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
Rollout paths
Start where your team feels the pain first
Varcio 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, Opsgenie, 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.