Operations | Monitoring | ITSM | DevOps | Cloud

September is associated with football, foliage, flannel and, for some, the Financial Plan. As we put pen to paper (or agents to harnesses), there’s a few core elements that have always driven the P&L outlook for the following year: rep productivity and new product releases driving new sales, expansion and contraction against the install base, employee roster changes, and discretionary spend.

Somewhere in your company, a team is three weeks into the AI project that’s going to matter. Somewhere else, a support pilot from the spring is still summarizing every ticket with a frontier model, and nobody has looked at it since it started working. On the invoice they’re identical, and the company has two moves: leave everything open, which funds the waste, or cap everyone, which kills the bet.

15 AWS cost optimization tactics across compute, storage, networking, and monitoring plus a quick-reference table by effort and savings potential.

At some point this year, you likely approved a request to expand AI coding tool access across the team. The pitch was straightforward: engineers write code faster, the team ships more, the investment pays for itself. The first half happened. Engineers are writing code faster. If you're now being asked whether the investment paid off, and you're finding the honest answer is more complicated than a yes, you are not alone, and you have not been sold something broken.

An LLM inference provider hosts open-weight models like Llama, DeepSeek, and Qwen behind a pay-per-token API, handling GPUs, scaling, and serving for you. The same Llama 3.3 70B model ranges from $0.10 to $1.04 per million input tokens depending on who serves it, so provider choice is a pricing decision. Top picks as of September 2026: Groq and Cerebras for speed, DeepInfra for price, Together and Fireworks for breadth, Baseten for custom models.

Learn why cloud cost optimization for engineers fails and how to fix it with developer-centric FinOps practices. See how Harness helps. Engineers often ignore cloud costs due to a lack of visibility, context, and ownership in their daily workflows. By shifting cost governance left and integrating real-time cost insights into CI/CD pipelines, teams build lasting cost accountability.

Several platforms now ship agents capable of investigating problems, proposing fixes, and deploying, with real permission models and sandboxing behind them. This is a genuine engineering achievement, not just a demo.

Build when the problem is narrow (one provider, one team, simple attribution) and the tooling is strategically yours to own. Buy when AI spend spans providers, arrives untagged, and needs unit costs finance will trust, because that build is a multi-quarter platform project with a permanent maintenance tail. Price both paths in engineer-years before deciding. CloudZero sells the “buy” side.

Perplexity pricing runs $0 for Free, $20 a month for Pro, and $200 a month for Max, with enterprise seats listed from $40 per user. Pro fits most people who search for work daily. Max exists for heavy automation. The prices are verified against Perplexity's live plans page as of September 2026. When Perplexity published a customer quote on its own pricing page, it chose an unusual one.