head to head · open source
Temporal vs osmedeus
Temporal has 23,133 GitHub stars, 1,905 forks, 956 open issues and last shipped yesterday. osmedeus has 6,568 stars, 1,031 forks, 3 open issues and last shipped 6 days ago. Temporal leads on adoption by 252% (23,133 vs 6,568 stars). Temporal is written in Go under MIT; osmedeus is written in Go under MIT. Temporal has attracted 8% as many forks as stars, osmedeus 16%. 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 8884 open source comparisons
Side by side
| Temporal | osmedeus | |
|---|---|---|
| GitHub stars | ★ 23K | ★ 6.6K |
| License | MIT | MIT |
| Written in | Go | Go |
| Last push | 2026-09-17 | 2026-09-12 |
| Forks | ⑂ 1.9K | ⑂ 1.0K |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick Temporal if
- You weight community size — 23K stars and counting
- You want the MIT license terms
- Your stack matches Go
- You value the larger contributor base for long-term maintenance
pick osmedeus if
- You want the osmedeus feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Go
- You evaluated both and osmedeus fits your workflow better
About Temporal
Temporal is a durable execution platform for building resilient applications with workflows. It lives in the infrastructure and operations ecosystem, specifically within orchestration and scheduling. The server executes units of application logic called Workflows and automatically handles intermittent failures by retrying failed operations. Temporal originated as a fork of Uber's Cadence and is developed by Temporal Technologies, a startup formed by the creators of Cadence.
read the full Temporal overview →
About osmedeus
Osmedeus is a security focused declarative orchestration engine written in Go and released under the MIT license. It turns complex security workflow automation into auditable YAML definitions, and it pairs that declarative model with encrypted data handling, secure credential management, and sandboxed execution. The project has been public for roughly eight years, carries about 6,563 stars and 1,030 forks, and lives in the penetration testing, reconnaissance, and attack surface management corner of the open source security ecosystem. It is distributed both as shell installed binaries and as the npm package @j3ssi…
read the full osmedeus 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 osmedeus more popular?
Temporal has 23,133 GitHub stars and osmedeus has 6,568. Temporal has the larger community by that measure.
Are Temporal and osmedeus free?
Both are open source. Temporal is licensed under MIT and osmedeus under MIT. Neither carries a licence fee.
What is the difference between Temporal and osmedeus?
Temporal is written in Go and osmedeus 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 osmedeus?
Choose Temporal if you want the larger community (23,133 stars) or its MIT licence terms. Choose osmedeus if its feature set, stack or MIT licence fits better. Both are self-hostable.