netflix/maestro

Maestro: Netflix’s Workflow Orchestrator

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 57 minutes ago
Added to GitGenius on September 18th, 2026
Created on April 17th, 2024
Open Issues & Pull Requests: 38 (+0)
GitHub issues: Enabled
Number of forks: 310
Total Stargazers: 3,839 (+0)
Total Subscribers: 162 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 34.1 hours
Mean response time: 20.3 days
90th percentile: 36.1 days
Tracked items: 37

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 13
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 509 days
Stale 30+ days: 11
Stale 90+ days: 10

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Maestro is a workflow orchestrator that provides a fully managed workflow-as-a-service platform for orchestrating data and machine learning pipelines at scale.

Maestro addresses the challenge of scheduling and managing complex workflows across diverse teams and use cases. It operates as a general-purpose orchestrator built to handle directed acyclic graph (DAG) workflows, supporting data engineering, machine learning operations, analytics, and batch processing. The system is designed for high throughput and reliability, operating under strict service-level objectives even during traffic spikes. It includes extensibility through modules like maestro-extensions, which adds capabilities such as foreach step flattening via event-driven processing through SQS and SNS integration.

Organizations running large-scale data and ML operations should consider Maestro if they need a managed orchestration service capable of handling thousands of concurrent users and millions of daily jobs. The tool suits teams already invested in Java-based infrastructure, as it requires Java 21 and Gradle for deployment. It works well for enterprises requiring strict SLO guarantees and the ability to scale horizontally. The project provides local development setup through Docker Compose and includes AWS module support for cloud deployments, making it accessible for both on-premises and cloud environments.

The project maintains active development with regular enhancements to core performance and functionality. The codebase includes comprehensive test resources and sample workflows demonstrating typical usage patterns. The team has published detailed technical documentation covering architectural decisions, performance optimizations, and integration patterns with complementary technologies like Apache Iceberg. The project provides clear build and deployment instructions, suggesting ongoing attention to developer experience and operational clarity.