HoropterHoropter

One record of every change, from every system.

Deploys, rollouts, migrations and incidents happen in many systems, and each records them its own way. Horopter takes their events in one shape, joins the ones that belong together into changes, and serves them to whatever needs to know what changed.

Why Horopter

Correlated
Events from different systems become one change: CI starts a deploy, the cluster controller finishes it, and Horopter knows they are the same deploy.
Yours to query
Every change, and the events behind it, over an HTTP API and the horo command line, as JSON, for scripts, reports and analysis.
Any reader
Grafana draws changes as regions on your graphs; anything that speaks HTTP reads them as they are.
A Grafana graph of request rate with a shaded region marking a deploy: the rate climbs inside the region, then falls back.A Grafana graph of request rate with a shaded region marking a deploy: the rate climbs inside the region, then falls back.
One reader of many: Grafana, drawing a deploy as a region on a request-rate graph.

Get started

Works with

Records from
Read by