head to head · open source

compose vs Temporal

compose has 38,573 GitHub stars, 5,899 forks, 111 open issues and last shipped yesterday. Temporal has 24,138 stars, 2,068 forks, 956 open issues and last shipped yesterday. compose leads on adoption by 60% (38,573 vs 24,138 stars). compose is written in Go under Apache-2.0; Temporal is written in Go under MIT. compose has attracted 15% as many forks as stars, Temporal 9%. Temporal was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (golang), so they are genuine substitutes rather than adjacent tools.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

compose ★ 39K Temporal ★ 24K category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

compose Temporal
GitHub stars ★ 39K ★ 24K
License Apache-2.0 MIT
Written in Go Go
Last push 2026-11-02 2026-11-02
Forks ⑂ 5.9K ⑂ 2.1K
Self-hosting Yes Yes
Data ownership Your server Your server

pick compose if

  • You weight community size — 39K stars and counting
  • You want the Apache-2.0 license terms
  • Your stack matches Go
  • You value the larger contributor base for long-term maintenance

full compose profile →

pick Temporal if

  • You want the Temporal feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches Go
  • You evaluated both and Temporal fits your workflow better

full Temporal profile →

About compose

Table of Contents Docker Compose Where to get Docker Compose + Windows and macOS + Linux Quick Start Contributing Legacy Docker Compose Docker Compose is a tool for running multi container applications on Docker defined using the Compose file format. A Compose file is used to define how one or more containers that make up your application are configured. Once you have a Compose file, you can create and start your application with a single command: docker compose up . Note : About Docker Swarm Docker Swarm used to rely on the legacy compose file format but did not adopt the compose specification so is missing…

read the full compose overview →

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 →

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 compose or Temporal more popular?

compose has 38,573 GitHub stars and Temporal has 24,138. compose has the larger community by that measure.

Are compose and Temporal free?

Both are open source. compose is licensed under Apache-2.0 and Temporal under MIT. Neither carries a licence fee.

What is the difference between compose and Temporal?

compose is written in Go and Temporal 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, compose or Temporal?

Choose compose if you want the larger community (38,573 stars) or its Apache-2.0 licence terms. Choose Temporal if its feature set, stack or MIT licence fits better. Both are self-hostable.