# When running your own orchestrator isn't worth it anymore -- and why EvenUp chose Temporal

DevFeed: [When running your own orchestrator isn't worth it anymore -- and why EvenUp chose Temporal](<https://devfeed.tech/articles/when-running-your-own-orchestrator-isn-t-worth-it-anymore-and-why-evenup-chose-temporal-36105.md>)

Original publisher: [Read original article](<https://temporal.io/blog/when-running-your-own-orchestrator-isnt-worth-it-anymore-and-why-evenup>)

Author: Michael Millerick

Published: 2026-03-17T00:00:00Z

Content type: article

Language: en

Sources: [Temporal Blog](<https://devfeed.tech/sources/temporal-blog.md>)

Topics: [Orchestration](<https://devfeed.tech/topics/orchestration.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Development](<https://devfeed.tech/topics/development.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [community](<https://devfeed.tech/tags/community.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [observability](<https://devfeed.tech/tags/observability.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

## AI overview

EvenUp migrated workloads from a custom workflow execution system to Temporal so engineers could focus on business logic. The article describes using Temporal metrics and latency-based scaling to monitor and scale asynchronous workloads while keeping near-real-time processing delays low.

## Source excerpt

Stop firefighting your workflow plumbing. Michael Millerick, Staff Software Engineer at EvenUp, explains why they migrated from a custom orchestrator to Temporal to improve scaling, observability, and engineering focus on AI-powered legal tech.