← Running in production

Running in production

June 2026

• Jun 28, 2026 AI cost tracking & telemetry In the briefing →

  CNBC — the enterprise mood is flipping from "tokenmaxxing" to efficiency, and the reporting carries hard numbers rather than vibes. Companies that spent the past year incentivizing developers to "use as much AI as possible" are now tightening spend — a shift CNBC frames as a potential drag on OpenAI's and Anthropic's revenue growth. The sharpest example: the CEO of AI startup Lindy switched 100% of its traffic off Anthropic's Claude to DeepSeek, saying costs "crashed to the ground" and projecting millions in savings within months (though the ~25-person firm still expects to spend more on AI than on payroll). Behind the move is a widening price gap — DeepSeek's flagship V4-Pro reportedly fell from about $0.145 to $0.036 per million tokens — and companies are adding governance: Uber imposed spending tiers on some AI tools starting at $1,500/month. It matters because cost monitoring and per-team budgeting are becoming a first-order discipline, not an afterthought, and the savings math is now concrete enough to move production traffic off a premium-priced lab. (CNBC)

• Jun 28, 2026 AI cost tracking & telemetry Weekly recap Read the recap →

  Workload Identity Federation reached GA, retiring static sk-ant-… keys for short-lived OIDC tokens and per-workload service accounts with their own rate limits and audit trails; CNBC's "tokenmaxxing → efficiency" reporting put concrete numbers on the spend pullback.

• Jun 23, 2026 AI cost tracking & telemetry In the briefing →

  Anthropic — Workload Identity Federation (WIF) reached general availability on the Claude Platform, letting a workload authenticate to the Claude API with short-lived OIDC tokens minted from an identity provider you already operate — AWS IAM, Google Cloud, GitHub Actions, Kubernetes, SPIFFE, Microsoft Entra ID, or Okta — instead of a long-lived sk-ant-… API key (token lifetime 60–86,400s, default one hour, via the RFC 7523 jwt-bearer grant). It ships alongside service accounts: named non-human identities that each carry their own workspace rate limits, usage attribution, and audit trail, so you can see which workload acted as which account instead of sharing one key across everything. It matters on two fronts — there is no static secret to store, rotate, or leak, and per-workload service accounts turn opaque shared-key spend into usage you can attribute and audit. WIF covers all Claude API endpoints, including the first-party SDKs and Claude Code. (official, docs)

• Jun 21, 2026 AI cost tracking & telemetry Weekly recap Read the recap →

  quiet; the Agent SDK's per-user billing split took effect June 15, and Copilot CLI's per-subagent model/effort controls add a cost lever for multi-step workflows.

• Jun 14, 2026 AI cost tracking & telemetry Weekly recap Read the recap →

  FinOps X anchored the week: FOCUS 1.4, the Tokenomics Foundation, Gartner's case for upstream "use case forecasting" (98% of FinOps teams now manage AI spend), agentic/per-subagent cost attribution, and the AWS FinOps Agent.

• Jun 12, 2026 AI cost tracking & telemetry In the briefing →

  AWS — launched AWS FinOps Agent in public preview at FinOps X's closing day: an agentic system built on Amazon Bedrock that answers cost questions in natural language, investigates cost anomalies to root cause, surfaces optimization opportunities, and runs recurring FinOps workflows on a schedule, routing alerts into Slack and Jira. It runs in US East (N. Virginia), manages costs across regions and accounts from a management account, and is free during the preview. The anomaly-to-root-cause loop is the part FinOps keynotes spent the week saying teams lack for AI spend. (official, official, source)

• Jun 12, 2026 AI cost tracking & telemetry In the briefing →

  Anthropic — the June 15 Agent SDK billing split is now officially documented, resolving the unconfirmed reports carried here since June 2: a Claude Help Center article confirms that from Monday, Claude Agent SDK, claude -p, and third-party Agent SDK apps move off plan usage limits onto a separate monthly per-user Agent SDK credit on Pro, Max, Team, and Enterprise plans. Credits must be claimed once (eligible users get an email with instructions before June 15), refresh each billing cycle, and can't be pooled, transferred, or shared across an organization; interactive Claude Code, Cowork, and claude.ai are unaffected. Anyone running Claude in CI or via the SDK has three days to claim the credit — and decide whether to enable overflow usage credits — before automation hits the new meter. (official, source)

• Jun 11, 2026 AI cost tracking & telemetry In the briefing →

  FinOps Foundation — the FinOps X day-2 keynote pushed past token economics to agentic cost structures: when an agent executes a task it may also spin up VMs, consume KV-cache storage, and trigger RAG pipelines — costs that sit entirely outside the input/output-token line item — and orchestrator-style systems need per-subagent cost attribution (which model each subagent used, at what token cost), since routing small tasks to lighter models is where the savings live. Practitioners were urged to move to "use case forecasting" — modeling users × prompts × planned releases — rather than extrapolating last month's bill. (source, source)

• Jun 10, 2026 AI cost tracking & telemetry In the briefing →

  Gartner / FinOps Foundation — at FinOps X, Gartner analyst Marco Meinardi argued AI breaks the assumptions traditional cost management was built on: cloud and SaaS spend was driven by users and systems inside the organization's control, while AI cost is driven partly by external behavior — how customers interact with and prompt AI-powered apps — so forecasting has to move upstream (region selection, data residency, financial context before deployment) rather than trailing the bill. The State of FinOps 2026 data shows how fast this became mainstream: 98% of FinOps teams now manage AI spend, up from 31% two years ago. (source, official)

• Jun 9, 2026 AI cost tracking & telemetry In the briefing →

  FinOps Foundation / Tokenomics Foundation — at FinOps X (San Diego, June 8–11), last week's "intent to launch" turned into something teams can adopt: FOCUS 1.4 — the open billing spec for normalizing cost data — was released at the conference, and the roadmap names v1.5 as the version that will break AI spend down by token type and workload, so inference cost can be tied back to the team consuming it. The newly formed Tokenomics Foundation (Linux Foundation, in partnership with the FinOps Foundation) detailed its initial working groups and technical roadmap on stage. (source, source)

• Jun 7, 2026 AI cost tracking & telemetry In the briefing →

  Linux Foundation — announced intent to launch the Tokenomics Foundation, a body (in close partnership with the FinOps Foundation) to set open standards, benchmarks, and best practices for the economics of AI infrastructure. Its first named deliverable is extending the FOCUS open billing spec to cover token-based spending, so token usage can be normalized alongside existing cloud-cost data; backers named include Google Cloud, Microsoft, IBM, Oracle, Salesforce, SAP, ServiceNow, Accenture, and JPMorganChase. Technical roadmap and working groups are due at FinOps X (June 8–10, San Diego). (official, source) (Announced June 3; surfaced now as the window's notable cost-tracking development and because the formal rollout is days away at FinOps X.)