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

We've worked in both worlds — software and manufacturing. We've built incident management systems for tech teams, and we've been on the factory floor at 3 AM when a production line goes down. We know what good incident response looks like, and we know how far most manufacturing operations are from having it.

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 by a small team in Sweden. We're not a faceless company — we're people who care about making operations work better.

Jonatan

Founder

Background in distributed systems and manufacturing operations. Has worked on both sides of the incident — building the software and being on the floor when things break.

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.