Workflow vs Statesman

Our great sponsors

InfluxDB - Power Real-Time Data Analytics at Scale

WorkOS - The modern identity platform for B2B SaaS

SaaSHub - Software Alternatives and Reviews

Our great sponsors

Workflow		Statesman
	Project
-	Mentions	3
1,730	Stars	1,727
-	Growth	1.5%
0.0	Activity	7.3
2 days ago	Latest Commit	1 day ago
Ruby	Language	Ruby
MIT License	License	MIT License

The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

Workflow

Posts with mentions or reviews of Workflow. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning Workflow yet.
Tracking mentions began in Dec 2020.

Statesman

Posts with mentions or reviews of Statesman. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-01-22.

Why Developers Never Use State Machines (2011)
2 projects | news.ycombinator.com | 22 Jan 2023

I’d strongly recommend Statesman instead: https://gocardless.com/blog/statesman/
I’m unaffiliated, just have used a lot of Ruby SM libraries.
State Machines in Ruby: An Introduction
1 project | news.ycombinator.com | 23 Jun 2022

Honestly state machines are fantastic in Rails too. My last company built [Statesman](https://github.com/gocardless/statesman/) and being able to lean on it to prevent you getting into invalid states is fantastic. You also get the bonus of tracking the history of states your resources went through (which is especially useful when you're dealing with payments).
At some point you'll have to think about query performance on the state transition table, but it'll go further than you think and is firmly in the realm of problems of success.
Code review of an Order object implemented as a state machine
2 projects | /r/ruby | 21 Mar 2021

I know you were doing educational proof of concent. But when I write them, I usually reach for the statesman gem. Makes state machines pretty trivial IME.

What are some alternatives?

When comparing Workflow and Statesman you can also consider the following projects:

AASM - AASM - State machines for Ruby classes (plain Ruby, ActiveRecord, Mongoid, NoBrainer, Dynamoid)

State Machine - Adds support for creating state machines for attributes on any Ruby class

FiniteMachine - A minimal finite state machine with a straightforward syntax.

transitions - State machine extracted from ActiveModel

FeatureFlags - Feature flags for Rails application.Manages ‘flags’ within your Rails app that determine whether various features are enabled or not.

state_machines - Adds support for creating state machines for attributes on any Ruby class

StatefulEnum - A very simple state machine plugin built on top of ActiveRecord::Enum