If you work in DevOps, you’ve probably had this experience: You ship something. It works. Performance looks good. Deployment is clean. A few weeks later, someone from finance shows up asking why costs spiked 30%. Now you’re digging through logs, trying to reconstruct decisions you made weeks ago, in a completely different context. That’s not a FinOps problem. That’s a workflow problem. The Real Issue: Cost Lives Outside the Pipeline Most DevOps teams have spent years tightening feedback loops: Code quality → caught in PRs Security → caught in CI Performance → caught in testing Cost is the outlier. It typically shows up: After deployment In a separate dashboard Owned by a different team Which means it’s not actionable when it matters. You can’t fix what you can’t see *in context*. Why DevOps Teams End Up Owning Cloud Cost Anyway ...
SmartBear today added capabilities to its platform for designing and managing application programming interfaces (APIs) that make it easier to both keep track of them and detect drift. A revamped Swagger Catalog, in addition to providing a unified view of APIs, also makes it possible to govern them. At the same time, SmartBear is adding Swagger Contract Testing with drift detection that verifies the API is behaving as specified in a contract. Additionally, SmartBear later this quarter plans to revamp its API editor along with artificial intelligence (AI) tools for generating APIs, a context-aware ability to create documentation, Spectral-based governance enforcement, a Model Context Protocol (MCP) Server and expanded multi-protocol support, including OpenAPI 3.1. AsyncAPI 3.0, and GraphQL. Laura Kennedy, director of product management for SmartBear, said both additions extend the API lifecycle management capabilities of the company’s platform. For example, Swagger Catalog combi...