Operations | Monitoring | ITSM | DevOps | Cloud

Why you're (probably) doing service catalogs wrong

Service catalogs promise a lot of things: powerful automations, insights into your technology estate. But over the last few years, many of us have learned that setting up and maintaining a service catalog is really hard. Building out a catalog from a standing start can take months, or even years. Too many people get stuck in a chicken-and-egg situation, where you can’t deliver value because you don’t have the data in your catalog, and you can’t convince anyone to spend time helping you because the catalog doesn’t do anything yet.

Why we vibe coded a marketing campaign for Anthropic

Let’s start with the obvious: we’d like to have Anthropic as a customer. We greatly admire the work they are doing at the intersection of frontier models + safety. We use lots of different AI tooling at incident.io. We’re all-in at AI at incident.io, both to improve the productivity of our internal team and, more importantly, to provide our customers with superpowers in the form of an AI incident responder.

The EU AI Act and what it means for managing incidents

If you've been in earshot of tech leadership lately, you've probably heard the words 'EU,' 'AI,' and 'compliance' in conversation. The EU AI Act is officially upon us, and with it comes a whole new set of incident response and reporting requirements that might feel like a yet another bureaucratic set of requirements to worry about. But there's a different way to look at this legislation.