head to head · open source
Temporal vs agent-orchestrator
Temporal has 24,173 GitHub stars, 2,072 forks, 956 open issues and last shipped yesterday. agent-orchestrator has 14,059 stars, 1,912 forks, 711 open issues and last shipped yesterday. Temporal leads on adoption by 72% (24,173 vs 14,059 stars). Temporal is written in Go under MIT; agent-orchestrator is written in Go under Apache-2.0. Temporal has attracted 9% as many forks as stars, agent-orchestrator 14%. Temporal was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| Temporal | agent-orchestrator | |
|---|---|---|
| GitHub stars | ★ 24K | ★ 14K |
| License | MIT | Apache-2.0 |
| Written in | Go | Go |
| Last push | 2026-11-04 | 2026-11-04 |
| Forks | ⑂ 2.1K | ⑂ 1.9K |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick Temporal if
- You weight community size — 24K stars and counting
- You want the MIT license terms
- Your stack matches Go
- You value the larger contributor base for long-term maintenance
pick agent-orchestrator if
- You want the agent-orchestrator feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Go
- You evaluated both and agent-orchestrator fits your workflow better
About Temporal
Temporal—durable execution platform Introduction • Getting Started • Contributing • Temporal Docs • Temporal 101 Introduction Temporal is a durable execution platform that enables developers to build scalable applications without sacrificing productivity or reliability. The Temporal server executes units of application logic called Workflows in a resilient manner that automatically handles intermittent failures, and retries failed operations. Temporal is a mature technology that originated as a fork of Uber's Cadence. It is developed by Temporal Technologies, a startup by the creators of…
read the full Temporal overview →
About agent-orchestrator
Agent Orchestrator Plan, run, and supervise coding agents from one place. Give every coding task its own agent, workspace, and feedback loop. Plan and delegate larger outcomes with a project aware orchestrator. Follow every worker, pull request, CI run, and review in a live Kanban. Download AO • Documentation • Releases • Contributing • Discord English · 简体中文 · 日本語 · 한국어 · Español · Français · Deutsch · Português (Brasil) A workspace for agent driven development One coding agent can handle a task. Running several across a project creates a different job: deciding what matters, splitting work…
read the full agent-orchestrator overview →
More in Infrastructure & Operations
Related comparisons
More Orchestration & Scheduling projects
Compare either of these against the rest of the Orchestration & Scheduling field.
Frequently asked questions
Is Temporal or agent-orchestrator more popular?
Temporal has 24,173 GitHub stars and agent-orchestrator has 14,059. Temporal has the larger community by that measure.
Are Temporal and agent-orchestrator free?
Both are open source. Temporal is licensed under MIT and agent-orchestrator under Apache-2.0. Neither carries a licence fee.
What is the difference between Temporal and agent-orchestrator?
Temporal is written in Go and agent-orchestrator in Go. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, Temporal or agent-orchestrator?
Choose Temporal if you want the larger community (24,173 stars) or its MIT licence terms. Choose agent-orchestrator if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.