Summary：**Burnlens 1.4.2 Launches with Groundbreaking Features That Excite Users** *The open‑source FinOps

**Burnlens 1.4.2 Launches with Groundbreaking Features That Excite Users**
*The open‑source FinOps proxy for AI spend across OpenAI, Anthropic, and Google.*

### Introduction
Burnlens, the community‑driven tool that helps teams monitor and control AI‑related expenses, has just released version 1.4.2. The update arrives as enterprises scramble to keep generative‑AI budgets from spiralling out of control. By offering a unified view of usage across the three biggest model providers—OpenAI, Anthropic, and Google—Burnlens promises to turn opaque billing statements into actionable insight.

### Key Developments
The 1.4.2 release introduces three headline features that have already sparked lively discussion in Slack channels and developer forums:

1. **Real‑time cost alerts** – Users can set thresholds per project or per model and receive instant notifications via email, webhook, or Slack when spend approaches the limit. Early adopters report catching overruns hours before they would have appeared in monthly invoices.
2. **Granular usage tagging** – A new tagging engine lets teams attach custom labels (e.g., “experiment‑A”, “production‑chatbot”) to each API call. The aggregated dashboard then breaks down spend by tag, model, and region, making it easier to attribute costs to specific business initiatives.
3. **Enhanced export capabilities** – CSV and JSON exports now include latency and token‑efficiency metrics alongside cost data, enabling finance and engineering teams to correlate performance with spend in a single spreadsheet.

Under the hood, the update also improves the proxy’s latency by ~12 % through a refined connection‑pooling algorithm and adds support for the latest Google Gemini 1.5 endpoints, ensuring compatibility with the newest model releases.

### Industry Analysis
The launch comes at a pivotal moment. According to a recent Gartner survey, 68 % of organizations using large‑language models admit they lack visibility into AI‑related expenses, often discovering budget breaches