June 26, 2026
Competitors who collaborate. What the Drupal community is showing the rest of us.
Author: Niklas Franke, Marketing & Community Manager
FlowDrop, ECA, and Maestro are technically competitors. Their maintainers sat down anyway — to find common ground rather than defend territory. This is what that conversation produced, and what it says about the Drupal community.
Three modules, three maintainers, one conversation — and why it matters beyond open source.
There are moments in a community that reveal what it actually stands for.
Shibin Das, maintainer of FlowDrop, recently sat down with the module maintainers Jürgen Haas (ECA) and Randy Kolenko (Maestro). Three people spread across the planet, each with their own module, their own user base, their own roadmap. Technically speaking: competitors in the same space. In practice: collaborators.
Their subject was orchestration in Drupal. Their finding: less overlap than the outside world tends to assume, more complementarity than even they had expected. And a shared question that has stayed with them since — how to build a common foundation so that users no longer have to choose between modules, but can focus on what they actually want to build.
That is not a small thing. It means investing energy into something that does not immediately benefit your own project. It requires trust, openness, and the willingness to see your own work in context — not in opposition to others, but alongside them.
The other story being told right now
Anyone paying attention in the Drupal community recently will have noticed a second, parallel conversation: about how companies that build on open source choose to compete.
Dries Buytaert, Drupal’s founder, put his position plainly: companies that profit from an open source ecosystem carry a responsibility — to the project, to the community, and to the ecosystem as a whole. Growing at the expense of others, rather than growing together with them, breaks the social contract that makes open source work in the first place.
You do not have to agree with every detail of that argument. But the underlying question is legitimate: how do we want to compete with each other?
What FlowDrop, ECA and Maestro demonstrate
The conversation between Shibin Das, Jürgen Haas and Randy Kolenko is not a rejection of competition. It is an example of what competition can look like when the ecosystem and user needs come first — not market share.
FlowDrop focuses on targeted orchestration — well suited for use cases where events from Drupal core need to be processed directly, without requiring a complex framework. ECA (Event-Condition-Action) provides a powerful rule-based engine for sophisticated workflows. Maestro brings visual process modelling and structured task management. Three distinct approaches that, in practice, frequently complement each other.
The vision they are working toward: a shared technical base that all three can build on. So that the first question in a project is no longer “which module do I pick?” — but simply: what do I want to build?
That, incidentally, is what open source is actually for. Not innovation in silos, but innovation in dialogue.
About FlowDrop
For enterprise Drupal teams and AI-agent builders, FlowDrop is the only Drupal-native orchestration system where an explicit, typed dataflow graph is at once the specification, the execution engine, and the audit trail — runnable sync / async / stateful from one definition, and versioned as git-friendly config.
Think n8n/Activepieces breadth with Flowise/Langflow’s AI-flow building, but Drupal-native, typed end-to-end, and deployable as version-controlled config rather than rows in an external SaaS database.
Its distinctive move: the graph itself is the legible, deployable artifact. The logic lives in typed, inspectable nodes and data is visible on the wires. The spec, the running engine, and the audit trail are one and the same.
Why Flowdrop exists
FlowDrop is a community contribution. It is built to fill a genuine gap in Drupal’s orchestration story and give the project a capability it lacked, then released back to the community.
The visual editor at its core is decoupled and reusable beyond Drupal, so the design has been validated in more than one context — not just this module.
The goal is to give Drupal something real and useful.
What Collaboration means for us
At Factorial, we work with the Drupal ecosystem every day — as developers, as integrators, as partners for organisations that want to structure and orchestrate their digital processes. The idea behind FlowDrop, giving Drupal a seamless solution for integrating AI capabilities into content and editorial workflows, created a spark worth supporting. From early on, Factorial decided to sponsor the development of FlowDrop in order to foster innovation in the Drupal community.
What Shibin Das, Jürgen Haas and Randy Kolenko are doing here is not a footnote from the community. For us, it is a quality signal about an ecosystem we are proud to be part of.
Open source depends on the conviction that building together produces better outcomes than protecting individual territory. Sometimes that principle needs a concrete face. Three maintainers who sit down together — because they chose to, not because they had to — are exactly that.
If you are building or evolving orchestration workflows in Drupal: we know the ecosystem. And we know which modules make sense, and when.
