How We Built FinGarage: Turning Cloud FinOps Invoices into Verified Code Refactors with Switch & Google Antigravity
Published for the Flip the Switch Hackathon (WeMakeDevs) The $14,487/Month Question Nobody Can Answer Alone Every month, FinOps teams open their cloud and LLM billing dashboard and see a horror story: a single internal endpoint— GET /orders/summary —just burned $14,487.60 in 30 days ( $0.048292 per request , nearly 10x over budget ). FinOps files a Jira ticket. Three weeks later, a backend…
FinGarage, a product developed as part of the Flip the Switch Hackathon, aims to address the challenge of managing cloud FinOps invoices. The $14,487/month billing spike on a single internal endpoint was a pain point for FinOps teams. FinGarage leverages Switch and Google Antigravity to bring Finance and Engineering together in a live environment.
FinGarage consists of two agents: finops-agent and dev-agent. The finops-agent has exclusive access to invoice data and budget policies, while the dev-agent has access to the application code. Both agents work together to instrument the checkout-service, adding cost telemetry to every HTTP request.
The probes run in the Switch Room to detect cost inefficiencies and code quality issues. The golden accuracy probe checks for compliance with budget policies, and the golden accuracy probe verifies the financial accuracy of the code changes.
The dev-agent can make shortcuts to reduce costs, but if the golden accuracy probe detects a loss in accuracy, the finops-agent will block the fix. The final fix involves optimizing the SQL queries, caching LLM responses, and adding structured metric counters. This results in a 92.5% reduction in unit cost, a 25.7x improvement in latency, and a 100% golden accuracy rate. The finops-agent updates the Switch Room Document with the savings and attaches a receipt card as proof.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
