Spiff Arena and Ed

Spiff Arena and Ed work with the same kind of BPMN process model files, but they serve different jobs.

Product Roles

Product

Primary role

Typical user

Ed

Author, edit, run, and refine process models in the browser

Process authors, business analysts, developers

Spiff Arena

Deploy, administer, and execute process models for end users

Process owners, admins, participants

Use Ed For

  • Creating BPMN diagrams.

  • Editing form schema and UI schema files.

  • Running diagrams during authoring.

  • Debugging process behavior before deployment.

  • Syncing process model files with GitHub.

  • Working with the Ed AI assistant.

Use Spiff Arena For

  • Running published process models with real users.

  • Managing process groups and process models.

  • Completing User Tasks and Manual Tasks.

  • Configuring secrets, authentications, permissions, and connector proxy settings.

  • Monitoring process instances.

  • Managing deployed runtime behavior.

Shared Concepts

Both products use shared authoring concepts:

  • BPMN diagrams.

  • JSON Schema and UI Schema forms.

  • Jinja-rendered task instructions and form files.

  • Service Tasks and connector proxies.

  • DMN decision tables.

  • process files stored with the model.

When documentation describes a modeling pattern, it usually applies to both Ed and Spiff Arena. When documentation describes navigation, administration, deployment, or production runtime behavior, follow the product-specific page.

Before Moving from Ed to Spiff Arena

Before deploying or handing off a model:

  • run the process in Ed with realistic data;

  • verify forms render with expected task data;

  • review gateway labels and conditions;

  • confirm connector proxy settings are available in the target environment;

  • confirm secrets or tokens are not stored in model files;

  • review GitHub diffs for BPMN, schema, UI schema, and DMN changes.