Assembly Line

iWF

iWF is a Workflow-As-Code microservice orchestration platform offering an orchestration coding framework and service for building resilient, fault-tolerant, scalable long-running processes

iWF is an open-source message queues project on GitHub under the MIT license (permissive), with 663 stars. It is built with Go and Gin. Its last push was 2 months ago.

Stars
663
License
MIT
Activity
Active
Latest release
v1.20.0

Code on GitHub

Judgement

What it is
Framework or platform
What it does
A workflow-as-code framework and server from Indeed for long-running processes that wait on events and timers, built on Temporal or Cadence.
Adopt it when
You already run Temporal or Cadence and want a simpler programming model for long-running workflows than writing raw Temporal workflows.
Watch out
It adds a layer on top of Temporal or Cadence, which you still have to operate, and its user base outside Indeed is small.
Ready for
Usable
Runs as
Self-hosted server and library
Built with
Go and Temporal
How established
Established: started 4 years ago, latest release v1.20.0.
What the license allows
You can build it into a product you sell, as long as you keep its copyright notice.

Judged on 2026-11-06 from the project's README and GitHub data. The license and age lines are worked out directly.

Built from

Follow it down: iWF → Go → runs on a microchip

How compilers were built, back to punched paper tape

Open-source alternatives to iWF

  1. 1
    Apache Kafka apache

    Apache Kafka - A distributed event streaming platform

    Building block Production-ready Several systems need to publish and replay large streams of events reliably, and you have the operations capacity to run a cluster or pay for a managed one.

    ★ 34k Apache-2.0 Java Active, pushed today
  2. 2
    NSQ nsqio

    A realtime distributed messaging platform

    Building block Production-ready You need simple, horizontally scaled pub/sub between Go services and can accept at-least-once delivery without ordering guarantees.

    ★ 26k MIT Go Active, pushed 3 months ago
  3. 3
    NATS nats-io

    High-Performance server for NATS.io, the cloud and edge native messaging system.

    Building block Production-ready You need lightweight messaging between services or devices and want streaming persistence without running Kafka.

    ★ 21k Apache-2.0 Go Active, pushed today
  4. 4
    Apache Pulsar apache

    Apache Pulsar - distributed pub-sub messaging system

    Building block Production-ready You need multi-tenant messaging at scale with both queue and stream semantics and can run a JVM cluster.

    ★ 15k Apache-2.0 Java Active, pushed today
  5. 5
    RabbitMQ Server rabbitmq

    Open source RabbitMQ: core server and tier 1 (built-in) plugins

    Building block Production-ready Your services need reliable asynchronous messaging with flexible routing.

    ★ 14k See repository JavaScript Active, pushed today
  6. 6
    Debezium debezium

    Change data capture for a variety of databases. Please log issues at https://github.com/debezium/dbz/issues.

    Building block Production-ready You need to stream every database change into Kafka or another system for caches, search indexes or analytics without changing application code.

    ★ 13k Apache-2.0 Java Active, pushed today
  7. 7
    Redpanda redpanda-data

    Redpanda is a streaming data platform for developers. Kafka API compatible. 10x faster. No ZooKeeper. No JVM!

    Building block Production-ready You want Kafka-compatible streaming with simpler operations and lower latency, and existing Kafka clients must keep working.

    ★ 13k See repository C++ Active, pushed 28 days ago
  8. 8
    RisingWave risingwavelabs

    Event streaming platform for agentic AI. Continuously ingest, transform, and serve event streams in real time, at scale.

    Building block Usable You want real-time aggregations over event streams written in SQL instead of building Flink jobs.

    ★ 9.4k Apache-2.0 Rust Active, pushed today

Stars, license and activity come from GitHub and refresh on a rolling hourly schedule. The project's own description is quoted as written.