Operations | Monitoring | ITSM | DevOps | Cloud

The latest News and Information on DevOps, CI/CD, Automation and related technologies.

GPT-5.6 pricing: Sol, Terra, and Luna costs

GPT-5.6 pricing runs across three tiers, per million tokens. Sol costs $5 input / $30 output. Terra costs $2.50 / $15. Luna costs $1 / $6. All three share a 1.05 million token context window. The twist nobody priced in: OpenAI’s own system card admits Sol sometimes takes action nobody approved, then reports the job as done. For finance teams, that behavior is a governance issue worth understanding before engineering routes production traffic to it.

Best AI cost management tools [2026]

The best AI cost management tools in 2026 are CloudZero (best overall for connecting AI and cloud spend to business outcomes), Langfuse (best open-source LLM tracker), Portkey (best LLM gateway with cost controls), Datadog LLM Observability (best for teams already on Datadog), and CAST AI (best for Kubernetes AI infrastructure). The right tool depends on whether your primary problem is token-level LLM visibility, cloud infrastructure spend, or understanding whether your AI is generating real ROI.

5 Optimization Blockers You Didn't Know Were Inflating Your Cloud Bill

Most cloud-native cost tools are built to find and address waste reactively. Underutilized nodes, oversized requests, and idle workloads are revealed in the utilization data, the fixes are well documented, and the initial savings these tools drive are very real. But what we’ve seen consistently across clusters is a different category of blocker, one that quietly prevents consolidation and strands capacity your autoscaler can never reach. They don’t surface in dashboards as obvious waste.

Shipped: Allocate AWS cost by account name, not account ID

Until now, allocating by account name meant doing the work yourself: hand-building a custom dimension that mapped every twelve-digit AWS ID to a readable name, then maintaining it by hand in CostFormation. That mapping is fragile. Rename a definition or edit the wrong line and dashboards that depended on it quietly break. Now the account name is built in for accounts connected through AWS CUR 2.0.

Bitbucket Tests now supports tracking tests from multiple branches

Tracking tests on non-default branches was one of the most requested capabilities during the Bitbucket Tests (beta). We heard you, and today, we’re shipping it. Most teams don’t ship from main. Integration happens on develop, stabilisation on staging, releases cut from release. Until now, Bitbucket Tests only tracked the tests from default(main) branch, leaving the branches that actually matter invisible. Multiple branch tracking in Tests changes that.