Operations | Monitoring | ITSM | DevOps | Cloud

Introducing Spike's new look: designed to scale.

Today, we are introducing Spike’s new logo, a new website, and honestly, a new identity from the ground up. This is very exciting day for all of us at Spike. More companies are being built today than at any other point in history. Small teams are making big products. And no matter the size of the team, every single one of them needs reliability. Reliability should not be a second-class citizen for any company, no matter where they are in their journey.

We made our blog easier to read

Two weeks ago, we asked ourselves a simple question: How can we improve the reading experience of Spike’s blog? There are about two hundred articles on the blog, covering alerting, on-call, incident response, and more. Kaushik and I discussed each of these topics thoroughly before turning them into articles. But when someone landed on the blog, they couldn’t easily discover these articles. It was mostly one long scroll, and though we had some categories, they weren’t organized well.

Introducing Spike's MCP

You probably spend most of your day next to an AI now. Code reviews, debugging, writing, it all happens in Claude Code, Cursor, or a chat window. But when an incident fires, you still have to leave. Open Spike, read the payload, copy the important bits over, explain the background, and only then start fixing. That gap is gone. Spike now has an MCP server. Your AI can fetch incident payloads, dig into root causes, acknowledge and resolve incidents, and set up on-call schedules and escalation policies.

We rebuilt Spike app for Slack

The new Spike app for Slack brings incident response into the channel your team already works in. This walkthrough covers the @Spike AI assistant, the redesigned incident alert template, Statuspage syncing, and on-call overrides. To get started, head to Slack settings inside Spike and reconnect the app. Chapters Statuspage syncing is available on all plans. Spike is an incident response and on-call management platform. Alert routing, escalation policies, on-call schedules, and incident management, built for engineering teams.

Slack overview video

The new Spike app for Slack brings incident response into the channel your team already works in. This walkthrough covers the @Spike AI assistant, the redesigned incident alert template, Statuspage syncing, and on-call overrides. To get started, head to Slack settings inside Spike and reconnect the app. Chapters Statuspage syncing is available on all plans. Spike is an incident response and on-call management platform. Alert routing, escalation policies, on-call schedules, and incident management, built for engineering teams.

We rebuilt our Slack app

We are launching a new version of our Slack app for Spike. New architecture, a proper incident workflow you can run end to end without leaving Slack, and our first real go at bringing AI into the mix. We didn’t get here in a straight line though. This is the story of why we rebuilt our Slack app from the ground up, how we did it, and what we ran into along the way.

A 'new' space for our voice

Today I’m really excited to share the new look of our blog. Spike has had this blog for a while. Early on, it was just me and I wrote about the decisions I was making as we built Spike. Then we slowly started growing and wrote about incidents, response, escalations, on-calls and even many guides. It’s safe to say now that we are doubling down on this space! With the new design, we have intentionally kept it minimal and put the content first.

We redesigned Spike

Last Christmas, after everyone had gone quiet for the holidays, I sat down with a pen and some paper and started drawing Spike. Not the Spike we actually had, but the Spike I wanted, the one I had been carrying around in my head for a long time without ever really putting it down anywhere. A little while later I brought a few of those screens into Figma and showed them to the team over coffee one afternoon.