About Haveri

Incidents are normal.
Let's get good at them.

Haveri exists because the people who keep production lines running deserve better tools than a group chat and a phone tree.

Why this exists

Haveri started because two people from different worlds kept having the same conversation. Cecilia has spent her career in manufacturing operations — she knows what it's like to manage a production facility, get woken up at 3 AM, and lose hard-won fixes to chat history. Jonatan has built products and founded companies — he's seen how structured incident management transformed reliability in tech teams.

In software, structured incident management has been standard for years. Tools like PagerDuty and incident.io are the norm. When something breaks, there's a process. It's calm, it's documented, and the team learns from it.

In manufacturing, the same severity of incidents gets handled with a group chat and a phone call. The fix someone figured out at 3 AM disappears into chat history. The same equipment fails the same way three months later because the knowledge left with the person who was on shift.

We built Haveri to bridge that gap. Not an enterprise platform that takes six months to implement. Something that meets manufacturing teams where they already are — in Teams, on their phones, between shifts. Named after the Swedish word for a breakdown, because pretending incidents don't happen is what makes them catastrophic.

What we believe

  • Incidents are learning opportunities, not failures. The goal isn't zero incidents — it's zero repeated incidents.
  • Knowledge should stay with the team. When a senior operator retires, their experience shouldn't leave with them.
  • Tooling should meet people where they are. If your team lives in Teams, your incident tool should too.
  • Calm is a feature. Good process removes drama. The right person gets notified, not everyone.

The team

Haveri is built in Sweden by people who've lived the problem on both sides.

CS

Cecilia

Co-founder

Manufacturing operations background. Has managed production facilities, handled incidents at 3 AM, and knows firsthand what works on the floor and what doesn't.

JS

Jonatan

Co-founder

Product engineer and founder. Has built large-scale critical systems where every minute of downtime is expensive, and knows what good incident management looks like from the inside.

Want to talk?

If you're dealing with the same problems — incidents that repeat, knowledge that disappears, escalations that don't work — we'd genuinely like to hear from you.

Get in touch → Read the blog