Evinor started with a question that annoyed us for years: why does software find out about the world by reading?
01The problem
Inside our systems, everything is an event — typed, deduplicated, delivered once. Outside them, everything is prose and noise. The same acquisition told forty ways across forty outlets. A cloud incident dribbled out as five status-page updates that are really one outage. A dozen APIs that each describe the same happening in a different dialect. The information was always there. The event never was.
Prose is a terrible API. So is a status page. So is a feed you have to poll.
02What we built
We built the thing we wanted to exist: an engine that listens to the noisy channels so nothing else has to. It resolves every alias to one canonical entity, collapses every retelling into one event, types the fields, counts the corroboration, and fires a webhook. One happening, one event, delivered once — with the receiver deciding how sure is sure enough to act.
03Where we started
We started where the noise is loudest and the cost of a missed or duplicated event is real money: acquisitions, funding, insolvencies, incidents. But the engine doesn’t care where a happening surfaces — an outlet, a filing, a status page, an API. Sources are adapters. The event is the product.
04Who we are
We’re a small team that cares about unglamorous things: entity resolution accuracy, schema stability, delivery guarantees, and a trigger log you can actually debug from. If that’s your idea of exciting, we should talk — we’re looking for design partners and, occasionally, colleagues.