At Operaton, we’re all about making things simple, efficient, and user-friendly. That’s why we’ve adopted a centralized approach to managing community plugins:
Popular plugins will be forked and maintained directly within our official GitHub organization.
No extra “community hubs,” no scattered repositories – just a single, reliable source for all plugins under the Operaton umbrella. 
This ensures:
Up-to-date plugins
Consistent quality
Easy access for contributors and users alike
Our first fork? The Keycloak plugin!
By integrating the Keycloak plugin into Operaton, we make it easier to manage authentication and authorization for your BPMN workflows. Secure, seamless, and developer-friendly – that’s our promise!
Why a centralized plugin strategy?
• It keeps our ecosystem clean and cohesive.
• Contributors can focus on improving a unified codebase.
• Users know exactly where to find trusted, maintained plugins.
But we want to hear your thoughts! 
• Do you think this centralized approach works best for plugin management?
• What challenges or benefits do you foresee?