Web Modeler Self-Managed Non-Prod Edition (Cloud)

Value Proposition Statement 🚀

Teams can try Web Modeler Self-Managed integrated into their Zeebe cluster

While trialing the product, some potential customers use Helm charts to deploy the entire stack to a cloud environment
Web Modeler will only be available for Enterprise users and with Docker at this time

Installation

[x] (M) When I install the platform using Helm charts, I want to have easy access to Web Modeler so I can develop my process quickly - depends on a Helm release referencing a Web Modeler release on the public docker hub (starting with alpha2)
[x] (M) While installing the platform, I want clear documentation so I can easily set it up on my cloud provider

Deployment

[ ] (M) As a developer, I want to easily execute the process development lifecycle on my cluster so I can test the flow (soft dependency on https://github.com/camunda/product-hub/issues/2073)

Telemetry

[ ] (S) As a Camunda PM, I want to know the level of adoption of Web Modeler Self-Managed so I can use SM data to validate epics

The "Management components" (Console, Modeler, and Identity) should always be together
This epic likely requires updates to the Helm charts
The licensing system should be modern
A simple place to start for telemetry is Monthly or Weekly active users (MAU\/WAU)
- A more advanced version involves tracking recurring usage (e.g. 1 fileview \/wk for 4 consecutive weeks) and requires data to be piped to our warehouse
- Telemetry is heavily based on feasibility - it may require a spike to learn about the options

^{:robot: This issue is automatically synced from: source}