Support executing exported Dify DSL in Graphon as an independent service

[Blackoutta]

Self Checks

• I have read the Contributing Guide and Language Policy.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report, otherwise it will be closed.
• Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Yes.

Some users have very large Dify workflows, and those workflows may contain multiple levels of nested workflows. In real production scenarios, a single execution can take around 2 hours.

These users want to export the workflow DSL from Dify, then use Graphon to take that exported Dify DSL as input, and execute it as an independent service outside the Dify low-code runtime.

There is also a second acceptable path: export the Dify DSL first, then use Graphon-based code generation to convert that low-code workflow into high-code that can run as an independent service. In other words, users need support for low-code to high-code migration based on exported Dify DSL, not only direct DSL execution.

This is important because the available resources inside Dify may be limited for long-running and complex workflows. In addition, users may need stronger runtime isolation, operational stability, observability, and service-level control than the low-code environment can easily provide.

The requested workflow is:

1. Build and maintain the workflow in Dify.
2. Export the workflow as Dify DSL.
3. Use one of the following execution paths:
4. Let Graphon load the Dify DSL directly and run it as an independent service.
5. Or use the exported Dify DSL as the source for code generation, producing high-code that can run as an independent service.

For this to be practical, both paths should be able to handle workflows exported from Dify, including workflows with multi-level nested workflow structures.

Illustration of the requested flow:

flowchart LR
    A["Build workflow in Dify"] --> B["Export Dify DSL"]
    B --> C["Graphon loads Dify DSL directly"]
    B --> D["Graphon code generation from Dify DSL"]
    C --> E["Run as independent service"]
    D --> F["Generated high-code service"]

Loading

2. Additional context or comments

Suggested acceptance criteria:

• Graphon can directly accept exported Dify DSL as input.
• Or Graphon can use exported Dify DSL as the source for code generation into high-code services.
• The execution behavior remains consistent with the original Dify workflow semantics.
• Multi-level nested workflows are supported, not only a single level of nesting.
• The exported workflow can be run as an independent service outside Dify, either through direct DSL execution or generated code.
• The solution is suitable for long-running production workloads that require better stability and observability.

From a user perspective, this would provide a practical migration path from Dify low-code orchestration to a more controllable service-based runtime, without requiring users to manually rebuild large workflows from scratch. It would also create a clear low-code to high-code upgrade path for teams that start in Dify but eventually need stronger engineering control.

3. Can you help us with this feature?

• I am interested in contributing to this feature.