This is something I’ve been thinking about a lot recently. Operaton already has users who run it in production and actively engage with our community. From what I’ve seen, most of them are using modern technology stacks and are not heavily dependent on legacy frameworks.
I believe our focus should be on these real users - understanding their use cases, learning from their feedback, and evolving the product based on their needs rather than trying to anticipate what potential users might want.
Over the next few months, the (ex C7) community/customers will naturally decide whether Operaton serves as a sufficient replacement for C7 for them or not. After that, our goal should be to continue building a solid, modern solution that can stand alongside other open-source BPM systems like jBPM, Kogito, Flowable or other systems that may arise in the next years.
So, I’m fully in support of taking a pro-modernization path here.