When things go wrong, customers notice

They notice the silence, the conflicting answers, the gap between what support says and what engineering knows. We built Obsession to fix that.

Why Obsession exists

When something goes wrong, customers don't ask whether it's an incident, a bug, or an upstream dependency. They just want to know what's happening.

Inside companies, those answers are often scattered across tools, teams, and conversations. Support hears one thing. Engineering sees another. Status pages tell a third story.

Obsession was built to connect those worlds. No drama, just honest updates.

Work with us

We're small and want to stay that way for a while. Here's how we operate:

  • Say what's happening, not what sounds good
  • Fix the problem before writing the postmortem
  • Write things down so anyone can understand them
  • Assume people are trying their best

If that sounds like you, get in touch. Bonus points if you've been paged at 2am before.

View open roles

Build the tools you'd want to use on a bad day

Get in touch