Operations | Monitoring | ITSM | DevOps | Cloud

Why you should use Language Server Protocol (LSP) with Claude Code

Agentic coding tools like Claude Code can write, refactor, and debug across an entire codebase, but by default they read code as plain text, the way grep does. The Language Server Protocol (LSP) changes that: it’s the same code-intelligence layer an IDE uses, and wiring it into an agent lets it read code by meaning instead of by string match. The bigger the codebase, the more a wrong guess about a symbol costs, and the more that structural view pays off.

CloudZero Dimension Studio: A drag-and-drop UI at the foundation of AI ROI

The core of ROI is visibility. If you can clearly see … 1. What it costs to produce the thing you make, and 2. How much money it makes you … then calculating ROI is easy. But with AI, as with the cloud before it, getting that visibility is extremely challenging. Why? Because the cost data associated with each is inherently chaotic.

6 use cases for agentic AI in major IT incident management

Enterprise IT operations leaders are realizing that legacy incident management processes cannot keep pace with today’s sprawling, hybrid-cloud enterprise environments. Enterprise IT doesn’t look anything like it did even five years ago. Hybrid cloud architectures, distributed microservices, and increasingly rapid CI/CD cycles have increased the speed and complexity of IT operations by orders of magnitude, leaving ITOps teams struggling to keep up.

How AI Shopping Assistants Are Turning E-Commerce Search Into an Operational Advantage

Conversational AI in retail crossed into production faster than most technology adoption cycles typically allow. What started as a novelty chat widget is now treated by operations and product teams as a core piece of the customer-facing stack, the case for that reclassification rests entirely on operational outcomes rather than interface aesthetics.

Escaping the AI Tokenomics Trap in Enterprise IT

AI adoption has accelerated faster than most organizations expected. What started with chatbots has quickly evolved into AI systems capable of making decisions across enterprise environments, with the promise of faster service and more efficient teams. But many organizations are discovering an unexpected challenge: as AI usage expands, costs become harder to predict. Most AI platforms operate on token-based pricing models.

Introducing Upsun Dispatch

AI has made writing code fast, and you can feel it. Commits are up, pull requests are up, new repos spin up over a weekend, and your engineers swear they are faster. But where are all the new products? If every team really got faster, the software you use every day should be getting visibly better. AI helped your engineers ship more code. It didn't help your team ship more products.

Stop Treating Coding Agent Plugins Like Settings: Introducing Agent Plugins Repositories

Your developers install agent plugins every day: pulling from unmanaged GitHub repos, copying Cursor commands out of Slack, pointing Codex at a personal Git fork. Each of those is a new, uncontrolled distribution channel inside your software development lifecycle, and your platform team has zero visibility into any of it. A plugin is not a preference file. It is executable software, and right now it’s arriving on developer machines with no versioning, no provenance, and no audit trail.

Stop Token Maxing The Future of Al Budget Management

The era of token maxing is over. When Claude Fable 5 launched last week at $10/$50 per million tokens - double the price of Opus 4.8 - it was a clear reminder that the most powerful model isn't always the right model. Not every task needs the Ferrari. The fastest way to burn your Al budget is sending every request to the most expensive model by default. The real question for the next phase of Al cost management isn't "can this model do the job?" — it's "is it the right model for the job?".