Branches, PRs, review, merge
Not a shadow system - real GitHub branches and pull requests. Review a diff, merge it, and it is in your repo like any other change.
A real dbt IDE, SQL and Python notebooks, and a native visual orchestrator - all in one place, on your governed data. No local setup, no shadow git, no glue between four tools.
dbt-core under the hood - the full --select grammar, multi-adapter. No shadow system: real GitHub branches, pull requests, review, and merge, so the work you do here is the work in your repo.
-- models/marts/orders_daily.sql
{{ config(materialized='incremental', unique_key='order_date') }}
with orders as (
select * from {{ ref('stg_orders') }}
)
select
order_date,
count(*) as orders,
sum(amount) as revenue
from orders
{% if is_incremental() %}
where order_date > (select max(order_date) from {{ this }})
{% endif %}
group by 1Not a shadow system - real GitHub branches and pull requests. Review a diff, merge it, and it is in your repo like any other change.
State-aware runs use state:modified+ to build exactly the models a change touches, and their downstreams - nothing more.
Autocomplete models, sources, macros, and columns with inline SQL lint - plus test results, docs, the DAG, and source freshness per run.
Labs is a Jupyter-grade notebook environment on your governed data - folders, keyboard shortcuts, and clean export to .ipynb, .py, or .html.
Query in SQL, analyze in Python, in the same notebook. Jupyter-grade editing with folders, shortcuts, and export to .ipynb, .py, or .html.
Start from a Data Science, ML, or Data Engineering image with the libraries already installed - no environment wrangling before the first cell.
Kernels carry no database credentials. SQL routes through the governed API, so access and masking are enforced no matter what the notebook runs.
Wire syncs, dbt, quality, and dashboards into one DAG on a canvas - with real control flow, not a wall of cron entries.
Any worksheet, dbt project, or notebook becomes a real pipeline - scheduled from the surface where you authored it, not rebuilt as a separate job.
Hit schedule on a worksheet, dbt project, or notebook. No exporting, no re-authoring it somewhere else as a job.
schedule: 0 8 * * *What you scheduled becomes a real Eve Pipeline - runs, retries, and history included, not a copy that quietly drifts.
worksheet → pipelineEvery task streams full tracebacks in-app, so a failure is one click from its stack instead of a log hunt.
traceback in-appCompute underneath: sized warehouse fleets scale 0 to N on queue depth and suspend when idle - you pay for work, not for waiting.
A 30-minute demo on your use case, or a free workspace on your own isolated cluster.