Learn how n8n and Temporal differ in their key features, development activity, technology stack and community adoption, so you can decide which of these workflow orchestration tools is best for you.
Stars
Forks
Last commit
Repository age
Self-hosted
Activity score

Activity score

Both n8n and Temporal have their unique strengths and serve similar purposes effectively. Consider your specific needs regarding popularity, activity, technology, maturity, licensing and features when making your decision.
n8n significantly outpaces Temporal in community adoption with 193,468 stars compared to 21,113 stars on GitHub. This 9.2x difference suggests n8n has a much larger and more active community. In terms of developer contributions, n8n has 58,727 forks, indicating strong developer engagement.
Both projects show recent activity, with n8n last updated 8 hours ago and Temporal 7 hours ago.
Both tools share common technology foundations, being built with Bash. However, they differ in their additional technology choices: n8n uses JavaScript, CSS, Typescript, SCSS, Vue while Temporal leverages Golang.
Both projects started around the same time, with n8n beginning 7 years ago and Temporal 7 years ago.
Temporal is licensed under MIT, while n8n's license terms are not publicly specified.
Both tools serve similar use cases in Workflow Orchestration. However, they also have distinct specializations: n8n also focuses on Low-Code/No-Code, Workflow Automation.
Both n8n and Temporal offer self-hosting capabilities, giving you full control over your data and infrastructure.