conductor-oss/conductor

Choose this fork if you want a customized, ops-focused Conductor branch and are willing to carry upstream lag. Choose upstream if you want the newest features, fewer upgrade risks, and a more actively current codebase.

Choose this fork if you want Conductor tailored to a specific AWS/ECS deployment and are willing to own a substantial upstream merge gap. Choose upstream if you want the broadest feature set, faster access to recent fixes, and less maintenance overhead.

Choose the upstream project instead unless you specifically need an older, frozen snapshot. This fork appears stale and offers no added features.

Prefer upstream unless you specifically need an older frozen baseline; this fork adds no visible value over current Conductor and is significantly behind.

Prefer this fork only if you specifically want an unchanged snapshot and are prepared to catch up 413 upstream commits yourself. For most adopters, upstream is the better choice because this fork adds no visible value and is substantially stale.

Prefer upstream unless you specifically need this exact older snapshot. This fork adds no visible functionality, while upstream has substantial newer workflow, AI, UI, and reliability improvements.

Prefer upstream unless you explicitly need this old snapshot. This fork adds no visible capabilities and is too far behind to recommend for production or new adoption.

Prefer upstream unless you explicitly need an old, unmodified Conductor baseline. This fork adds no visible value over upstream and is materially behind current development.

Choose upstream unless you specifically need an old frozen snapshot; this fork shows no added capability and is materially behind active development.