Dagster Consultant in Europe

I help European data platform teams design and operate Dagster. Engagements range from first implementations and upgrades to migrations from Airflow, cron, and other job-centric systems. I work with Dagster OSS and Dagster+, often on Kubernetes and alongside Databricks or dbt. The work covers asset modelling, deployment, ownership, checks, and recovery practices that the team can maintain after the engagement.

Book a Dagster architecture review

Who I help

I work best with data platform teams that are:

Running Airflow, cron, or fragmented orchestration and evaluating Dagster
Already on Dagster but struggling with asset modelling, code organisation, deployment, or observability
Deciding between Dagster OSS, Dagster+ Hybrid, and Dagster+ Serverless
Building on Databricks, dbt, Kubernetes, or cloud-native infrastructure
Trying to make orchestration reliable enough for AI, analytics, and production data products

Dagster problems I solve

Dagster implementation

Initial Dagster architecture, repository structure, asset model, deployment model, environments, CI/CD, and operational conventions.

Airflow or job-centric migration

Moving from task-first DAGs to asset-aware orchestration without simply recreating the old system in Dagster.

Dagster on Kubernetes

Production deployments with containerised code locations, secrets, environment separation, run launchers, and clear operational boundaries.

Dagster with Databricks and dbt

Modelling Databricks jobs, Delta tables, and dbt models as observable Dagster assets, with coherent ownership, lineage, freshness, and partitions.

Dagster+ EU advisory

Dagster+ is now available for European deployments, which changes the decision for EU-based teams that previously avoided managed orchestration over compliance, data residency, or control-plane concerns. I help teams decide between Dagster OSS, Dagster+ Hybrid, and Dagster+ Serverless, work out what metadata leaves their infrastructure, and design the platform so compliance does not block adoption.

Typical engagements

Dagster Architecture Review

A focused review for teams already using or evaluating Dagster: current-state assessment, target architecture, asset modelling review, deployment and CI/CD recommendations, and a 30/60/90-day roadmap.

Dagster Implementation Sprint

Hands-on help for teams starting with Dagster or rebuilding their orchestration layer: repository structure, asset conventions, deployment pattern, CI/CD baseline, and team enablement.

Airflow / Cron Migration Plan

A migration planning engagement: inventory of current jobs and dependencies, asset model design, a phased migration roadmap, and a rollback plan.

Why an independent specialist

Large delivery programmes need large teams. My engagements are smaller and senior-led: I work directly with the platform team on architecture, migration design, platform conventions, and technical enablement. The result should be a Dagster operating model the team understands and can maintain without a rotating delivery team.

Proof of expertise

Creator of the Orchestration Maturity Model
Author of practical writing on Dagster vs Airflow and asset-aware orchestration
Experience with enterprise data platform architecture across Dagster, Databricks, and Kubernetes
Referenced by Dagster Labs on orchestration maturity

I work remotely with teams across Europe, including the EU, UK, and Switzerland. Send a short note about what you’re building, where you’re stuck, and your timeline, and I’ll reply within a couple of days.

Discuss a Dagster engagement