ETLMaestro

ETLMaestro is a metadata-driven orchestration layer for Azure Data Factory and Microsoft Fabric. It doesn't move data. It orchestrates, monitors, and automatically recovers the pipelines and notebooks a team already owns.

The problem it targets has a name on our site: the master pipeline problem. ADF development that grows without a metadata approach ends up as one sprawling parent pipeline calling children calling children. One person in the company can tell you what happened when it fails, and the safe recovery is re-running everything from zero. When that person resigns, the architecture leaves with them.

ETLMaestro moves the orchestration design into metadata: processes, schedules, dependencies, and phases as rows in a database you own. Runs execute in checkpointed phases with automatic retry from the point of failure. The status report is a Power BI report over that same metadata, readable by anyone on the team without Azure portal access. Monitoring this way also costs zero capacity units, which matters because Fabric's native workspace monitoring bills against the same capacity your pipelines run on. We've watched teams turn it off to protect the budget.

The product is the third build of this framework. Noel Levine, the founding engineer, spent 20 years building Microsoft ETL across 50+ projects; the first version ran a critical infrastructure client's estate, the second sold on the Azure Marketplace as ChillETL, and ETLMaestro is the rebuild that turned it into a product.

Scope, stated plainly: it's for teams consolidating data into a central repository on ADF or Fabric, with an Azure Function integration for anything else with an API. Pricing is published, from $200/month, and every tier starts with a free two-month trial with no payment information. There's also a free 10-question pipeline health check on the site that asks for no email.