Deployment Cost Budget Enforcer in CI

WHAT IT DOES

The Deployment Cost Budget Enforcer in CI is a developer tool that enforces deployment cost budgets in CI pipelines. It parses deployment cost reports from hardhat-deploy, Foundry, or other EVM deployment tools, extracts gas usage and estimated ETH costs for each contract deployment, and compares them against configurable gas and ETH budgets. The tool identifies contracts that exceed budget limits and detects cost regressions compared to baselines, helping teams control deployment expenses and prevent unexpected cost increases.

HOW TO USE

Paste your current deployment cost report JSON into the first text area and your baseline report into the second text area. Click "parse current" and "parse baseline" to extract deployment cost data from each report. Set your gas budget (default 3,000,000 gas) and ETH budget (default 0.05 ETH). Click "enforce budget" to evaluate the deployment costs. The tool displays a detailed report showing each contract's gas usage and ETH cost, budget status, and a pass/fail summary. The report also indicates whether the CI check would pass or fail with the appropriate exit code.

TECHNICAL MECHANISM

The tool parses deployment cost reports with support for multiple formats. It handles hardhat-deploy's "contracts" object structure with gas fields, array-based deployment lists, and simple key-value objects where keys are contract names and values are gas costs. For each contract, it extracts the name, gas used, and calculates an estimated ETH cost using a 30 Gwei gas price (configurable by the user's actual deployment settings). The tool also calculates total gas and total estimated ETH across all contracts. When comparing against a baseline, it identifies regressions where gas costs increased. The budget check compares each contract's gas and ETH cost against the user-defined thresholds—any contract exceeding either budget triggers a failure. Results are displayed with color-coded status indicators showing whether each contract is within budget and whether it represents a regression from the baseline. The tool also provides a summary of budget status and a CI exit code recommendation.

WHAT IT CANNOT SEE

The tool cannot actually deploy contracts or measure deployment costs—it only analyzes already-collected data. It cannot detect cost increases caused by changes in compiler version or optimizer settings. The tool cannot automatically update budget thresholds. It cannot determine if a cost overrun is acceptable without manual review. The tool cannot analyze why deployment cost changed, only that it did. It cannot differentiate between changes in contract code and changes in deployment environment. The tool cannot validate that gas measurements are accurate or reproducible across different runs. It cannot account for gas price fluctuations or network conditions. The tool cannot predict deployment costs on different networks.

PLEASE NOTE

This tool is designed for Ethereum Virtual Machine (EVM) compatible chains only. The ETH cost calculation uses a 30 Gwei gas price estimate—actual costs will vary based on the gas price at the time of deployment. The tool requires deployment cost reports in JSON format—ensure your deployment framework is configured to output these reports. The tool is intended for CI/CD pipelines and local development testing. Always run deployment cost reports under consistent conditions (same compiler version, same network) to ensure accurate comparisons. The tool provides recommendations only and should be used as part of a comprehensive cost management process.