Halo

Halo runs the long-lived processes that hold a system together — financial settlements, supply-chain flows, compliance pipelines. Each workflow is a versioned, declarative artefact; each step is an event with provenance.

Operators see the whole system as a single map. Engineers extend it as a single language.

Conventional orchestrators express workflows in code that is hard to inspect and harder to evolve. Halo separates the shape of the work from the implementation of any single step, so the system can be reasoned about independently of who wrote which adapter.

Halo treats observability as primary, not as an export. Every state transition is queryable; every decision carries its evidence chain.

In production at four organisations, including the operator described in the Aurora engagement. Halo runs on the client's infrastructure; we do not require data to leave the perimeter.