November 28, 2025
Workflow Wars ignite
Open-Source n8n Alternative for Workflow Building (GUI and Docker Included)
New DIY workflow tool sparks cheers, n8n fans cry copycat, everyone wants a website
TLDR: Nyno 3.0 launches as an open-source tool to build automations in plain text while coding steps in Python, JavaScript, PHP, or Ruby, with a Docker GUI. The community is split: some love the flexibility, others say n8n already does this, and many demand clearer docs and a proper website.
Move over, n8n—there’s a new open-source automation toy in town, and it’s called Nyno 3.0. The pitch? Build workflows (aka “if-this-then-that” chains for your apps) using simple text files, but write the steps in the languages you already know—Python, JavaScript, PHP, or Ruby. It even ships with a GUI via Docker and claims a turbocharged engine that spins up workers across your CPU cores for speed. Sounds slick, right? The crowd is… divided.
Fans like theyogadev swooned over the “multi-language workflow engine” and human-readable YAML setup, while skeptics stormed in with the biggest mood of the day: isn’t n8n already open source? User TZubiri dropped the mic: “I thought n8n was open source though,” sparking a mini-identity crisis for Nyno. Meanwhile, tomhallett spoke for every confused newcomer: where do you even start—“just TCP?” Do workflows auto-run? The docs felt like a treasure hunt without a map.
And then came the roast that united the thread: “Needs a website,” declared popalchemist, earning instant upvotes. People want a homepage, clearer examples (show us the YAML!), and a friendlier on-ramp. Still, the idea of writing workflow steps in your favorite language got real love, especially with Docker one-liners and a local GUI. Verdict from the court of public opinion: promising power, confusing packaging—ship the docs and the site, and the hype might stick.
Key Points
- •Nyno 3.0 is an open-source, multi-language workflow engine using human-readable YAML (.nyno) to define automation.
- •Each supported language (Python3, PHP8 with Swoole, JavaScript with NodeJS, Ruby) runs in its own multi-process worker engine.
- •Worker scaling: dev mode spawns 2 workers per language; prod mode spawns 3 workers per language per CPU core.
- •Scripts become reusable commands by exporting functions (args and context), callable from YAML; examples include TCP-triggered routes.
- •Installation via Docker/Podman is recommended; a Linux manual install requires Best.js and provides dependency checks and a GUI at http://localhost:9057.