head to head · open source

Inngest vs tork

Inngest has 5,853 GitHub stars, 358 forks, 234 open issues and last shipped yesterday. tork has 817 stars, 63 forks, 20 open issues and last shipped 2 months ago. Inngest leads on adoption by 616% (5,853 vs 817 stars). Inngest is written in Go under a custom or non-standard licence; tork is written in Go under MIT. Inngest has attracted 6% as many forks as stars, tork 8%. Inngest was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (workflow-engine), 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.

Inngest ★ 5.9K tork ★ 817 category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

Inngest tork
GitHub stars ★ 5.9K ★ 817
License Custom / other MIT
Written in Go Go
Last push 2026-09-19 2026-07-21
Forks ⑂ 358 ⑂ 63
Self-hosting Yes Yes
Data ownership Your server Your server

pick Inngest if

  • You weight community size — 5.9K stars and counting
  • You want the Custom / other license terms
  • Your stack matches Go
  • You value the larger contributor base for long-term maintenance

full Inngest profile →

pick tork if

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

full tork profile →

About Inngest

Inngest is an open source workflow orchestration platform that lets developers write durable, event driven step functions in their existing language SDKs and run them on serverless, long running servers, or the edge.

read the full Inngest overview →

About tork

Tork is a lightweight, distributed workflow engine written in Go and released under the MIT license. It runs each task of a job as a script inside its own container, so work is defined in YAML rather than as compiled code. The project lives in the Go ecosystem and uses Docker, Podman, or a plain shell as its task runtime, with PostgreSQL as the datastore and a message broker such as RabbitMQ for distributed operation.

read the full tork overview →

More in Infrastructure & Operations

kubernetes ★ 128K Immich ★ 115K frp ★ 110K Uptime Kuma ★ 92K worldmonitor ★ 87K mall ★ 85K

Related comparisons

n8n vs kestra langchain vs haystack kubernetes vs rancher ansible vs compose ansible vs conductor ansible vs xxl-job ansible vs gitleaks ansible vs kestra n8n vs huginn uptime-kuma vs worldmonitor uptime-kuma vs netdata uptime-kuma vs grafana worldmonitor vs netdata worldmonitor vs grafana uptime-kuma vs prometheus netdata vs grafana kubernetes vs docker kubernetes vs kong kubernetes vs portainer kubernetes vs trivy kubernetes vs opentofu kubernetes vs jenkins kubernetes vs pulumi kubernetes vs floci

More Orchestration & Scheduling projects

Compare either of these against the rest of the Orchestration & Scheduling field.

Inngest vs ansible Inngest vs compose Inngest vs conductor Inngest vs xxl-job Inngest vs gitleaks Inngest vs Kestra Inngest vs haystack Inngest vs rancher Inngest vs Prefect Inngest vs Archon Inngest vs Temporal Inngest vs rowboat

Frequently asked questions

Is Inngest or tork more popular?

Inngest has 5,853 GitHub stars and tork has 817. Inngest has the larger community by that measure.

Are Inngest and tork free?

Both are open source. Inngest has no licence declared in this registry, and tork is licensed under MIT. Both are free to self-host.

What is the difference between Inngest and tork?

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

Choose Inngest if you want the larger community (5,853 stars) or its Custom / other licence terms. Choose tork if its feature set, stack or MIT licence fits better. Both are self-hostable.