Architecture that can be reviewed.

DataArkh exists because enterprise data architecture is real, and the record of it is usually not. Models live in a modelling tool, transformations in a pipeline, lineage in a catalog, and production change in a migration system that has never seen the model.

We keep those as one object, in your Git repository. A rename is stored as a rename. A review is a pull request. A migration is rendered from the same changeset you just approved.

What we are building is an architecture graph your team can change with the same discipline as code: impact before merge, governance as rules, production drift feeding the next model.

The name is inspired by Greek archē — foundation, origin, or first principle — written so the last two letters are the people who started it. The mark is three bars, because the product has three modelling tiers.