See exactly what moves
EVE resolves the diff between the running environment and the incoming version - which syncs, models, checks, and dashboards change, and what the contract diff implies.
Package syncs, dbt models, quality checks, and dashboards into a single versioned data product, then move it from dev to prod as one atomic transaction - plan, gate, apply. Your data never moves; only the specs do.
A data product carries semver and a content-addressed manifest. Promotion runs plan, then gate, then apply - and either the whole product moves forward or nothing does.
EVE resolves the diff between the running environment and the incoming version - which syncs, models, checks, and dashboards change, and what the contract diff implies.
Gates run the product's quality checks and a contract diff. A breaking change, or a failed check, stops the promotion before anything is applied.
Apply is one atomic transaction. The whole product lands together, or the environment is left exactly as it was. Rollback re-materializes the previous version.
Access and residency are decided at the org level and carried into every environment - so a product is governed the same way in dev as it is in prod.
The product model makes the safe thing the default. You cannot mislabel a breaking change, edit prod behind the platform's back, or lose the record of who shipped what.
A contract diff computes the bump for you. Add a nullable column and it is a minor; drop a field and it is a major. You cannot ship a breaking change as a patch.
Promoted assets are read-only in production. You edit in dev and promote forward - never hand-patch the live copy.
EVE compares the running prod product against its manifest and raises a drift badge on anything that no longer matches.
Each plan, gate, and apply is logged - who promoted, which version, and the gate result. The history is queryable.
The EVE promotion model removes three patterns that data teams carry today. Each card names the pattern, not a logo.
In legacy warehouses, every role x database x schema combination is its own grant, and the access matrix balloons. In EVE, one group grant carries role, domain, and every environment - including workspaces created later.
In most catalogs a domain is a filter chip on a view - it organizes, it does not enforce. EVE domains restrict access at the org level, in every environment and every product.
Hand-promotion means re-pointing dashboards, re-binding connections, and hoping nothing drifts. EVE promotes the whole product - pipelines, models, tests, dashboards - as one atomic, versioned transaction with rollback.
A 30-minute demo that ships a product from dev to prod - gate, apply, and rollback included.