https://github.com/elevata-labs/elevata
elevata is an Architecture Runtime for modern data platforms — metadata-native, warehouse-agnostic, and deterministic by design.
https://github.com/elevata-labs/elevata
analytics-engineering architecture-first architecture-runtime data-architecture data-engineering data-modeling data-platform elevata lakehouse metadata-driven metadata-management modern-data-stack open-source platform-agnostic sql warehouse-agnostic
Last synced: 5 days ago
JSON representation
elevata is an Architecture Runtime for modern data platforms — metadata-native, warehouse-agnostic, and deterministic by design.
- Host: GitHub
- URL: https://github.com/elevata-labs/elevata
- Owner: elevata-labs
- License: other
- Created: 2025-10-06T06:12:23.000Z (8 months ago)
- Default Branch: main
- Last Pushed: 2026-05-18T04:44:42.000Z (13 days ago)
- Last Synced: 2026-05-18T06:45:59.310Z (13 days ago)
- Topics: analytics-engineering, architecture-first, architecture-runtime, data-architecture, data-engineering, data-modeling, data-platform, elevata, lakehouse, metadata-driven, metadata-management, modern-data-stack, open-source, platform-agnostic, sql, warehouse-agnostic
- Language: Python
- Homepage: https://elevata-labs.github.io/elevata/
- Size: 36.6 MB
- Stars: 4
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
- Notice: NOTICE.md
Awesome Lists containing this project
README
# elevata®
**elevata® is an Architecture Runtime for modern data platforms.**
It turns **metadata into deterministic, executable data architecture**.
Architecture is defined declaratively and executed consistently across warehouses.
SQL becomes an artifact. Architecture becomes metadata.
---
## ⚡ What elevata enables
The same metadata-defined platform can run consistently on:
Snowflake · Databricks · Fabric · MSSQL · Postgres · DuckDB · BigQuery
without rewriting logic or introducing dialect-specific modeling.
elevata separates:
- **Logical architecture**
- **Dialect rendering**
- **Execution backend**
This makes data architecture portable, reproducible, and governable.
## License & Dependencies
[](https://github.com/elevata-labs/elevata/blob/main/LICENSE)
[](https://www.djangoproject.com/)
[](https://htmx.org/)
[](https://getbootstrap.com/)
---
## 🧭 What is elevata?
elevata is a **metadata-first** data platform engine.
It models datasets, lineage, governance, and execution semantics declaratively.
From these definitions, elevata derives deterministic logical plans, renders dialect-owned SQL,
and executes warehouse-native pipelines.
Schema evolution, incremental loads and historization are planned,
validated, and applied deterministically before execution.
Dataset detail view with lineage, metadata, and dialect-aware SQL previews
## ✨ Why elevata is different
Most data platforms encode architecture implicitly in SQL and pipeline code.
elevata makes architecture explicit.
- Metadata defines behavior.
- Dialects own SQL shape.
- Execution is deterministic and observable.
The result is governed, explainable, and portable data architecture.
---
elevata models datasets, lineage, keys, and execution semantics declaratively.
From this metadata, it derives deterministic logical plans and renders dialect-owned SQL.
The same architecture executes across supported warehouses without changing dataset definitions.
> *Modern data platforms often fail not because of missing tools, but because*
> *architecture, lineage, and governance are encoded implicitly in SQL and pipeline code.*
> *elevata exists to make these concerns explicit, declarative, and reproducible.*
---
## 🧩 Architecture Overview
elevata consists of four layers:
1. **Metadata Model**
2. **Deterministic Logical Plan**
3. **Dialect Rendering**
4. **Warehouse-Native Execution**
Each layer is explicitly separated.
---
## 📚 Example Workflow
1. Define datasets and lineage in metadata
2. Inspect generated SQL and lineage
3. Execute pipelines deterministically on your target warehouse
---
## 💻 Execution
Pipelines are executed dataset-driven and lineage-aware.
Execution supports full and incremental loads, historization,
schema evolution, and structured load logging.
Behavior is deterministic and observable.
Schema drift is reconciled through Architecture MigrationPlan-driven materialization:
renames, adds, type evolution and controlled rebuilds are derived from architecture state,
while destructive changes remain explicitly policy-gated.
---
## 🧭 Architecture Control
elevata makes architecture changes reviewable before execution.
Architecture State, Change Reports, Promotion Reports, Approval Artifacts and Execution Records
expose deterministic fingerprints, MigrationPlan actions, policy decisions, review decisions and execution outcomes.
This supports controlled review, CI checks and environment-to-environment architecture promotion
while keeping execution guardrails inside the load runner.
The Architecture Control UI makes approval state, scope, policy status, change summary,
execution preview, dependency mode, captured output and execution records visible for controlled scopes.
Users can inspect reports, download report JSON, create Approval Artifacts, verify approvals,
execute approved or no-change scopes, and inspect the resulting Architecture Execution Record.
---
## 📐 Query Builder
elevata models transformations explicitly using **Query Trees**.
Each TargetDataset may define a query tree composed of well-defined
operators such as SELECT, JOIN, AGGREGATE, UNION and WINDOW.
These operators are represented as metadata objects, not as opaque SQL fragments.
The Query Builder models transformations explicitly using structured metadata.
It produces deterministic SQL with stable contracts and field-level lineage.
---
## 🔮 Roadmap
elevata evolves along three strategic axes:
**1. Ingestion & Source Abstraction**
Expanding source patterns (files, APIs, cloud transports)
while preserving deterministic RAW semantics.
**2. Metadata Governance & Contracts**
Versioning, breaking-change detection, lineage validation
and reproducible execution snapshots.
**3. Performance & Adaptive Execution**
Warehouse-specific optimization layers and adaptive materialization strategies.
See `/docs` for architectural depth.
---
### ♟️ Architecture & Strategy
For a deeper architectural and strategic overview of elevata’s direction,
see the [elevata Platform Strategy](https://github.com/elevata-labs/elevata/blob/main/docs/strategy/elevata_platform_strategy.md).
---
## 🛡️ Data Privacy (GDPR/DSGVO)
elevata itself does not require personal data.
If used with customer datasets, responsibility for compliance remains with the implementing organisation.
The system supports pseudo-key hashing and consistent anonymisation strategies via its hashing DSL.
---
## Disclaimer
This project is an independent open-source initiative.
- It is not a consulting service.
- It is not a customer project.
- It does not store or process customer data.
- It is not in competition with any company.
The purpose of elevata is to contribute to the community by providing a metadata-centric framework for building data platforms.
The project is published under the AGPL v3 license and open for use by any organization.
---
## 🧾 License & Trademark Notice
© 2025-2026 Ilona Tag — All rights reserved.
**elevata®** is an open-source software project for data & analytics innovation.
elevata® is a registered trademark in Germany.
Other product names, logos, and brands mentioned here are property of their respective owners.
Released under the **GNU Affero General Public License v3 (AGPL-3.0)**.
See [`LICENSE`](https://github.com/elevata-labs/elevata/blob/main/LICENSE) for terms and [`NOTICE.md`](https://github.com/elevata-labs/elevata/blob/main/NOTICE.md) for third-party license information.