Most automation stories start with a platform and end with a bill. The version worth telling starts smaller. A form submission has to reach the CRM. An order needs a fulfillment call and a confirmation text. A daily report gets assembled by hand every morning because nobody ever wired it up. That glue work is the same in every business, and it does not need a cluster. It needs somewhere to live that you control.
Workflow Chain Engine is the open source engine I maintain for exactly that job. You draw a flow in the browser, it calls your APIs, branches on the answers, loops over lists, and records every run. It is one PHP application with a single SQLite file, MIT licensed, and it is at home on a three dollar shared host, a VPS, or a Docker container.
Why Self Hosted Automation Keeps Coming Back
Cost is the obvious reason, and it is not the interesting one. The interesting one is that automation touches your credentials. Every flow you build holds API keys for your CRM, your payment provider, your chat tool. When those keys live inside somebody else's platform, your blast radius is their incident report.
Running the engine yourself puts the workflows, the credentials and the run history in one folder you can back up by copying it. The editor library ships inside the project, so the whole tool works on your server with nothing loaded from anyone else's. There is no build step and no dependency install, which is why it fits on hosting you might otherwise be embarrassed to admit you use.
