When a process spans several tools, each event needs to be related to the right entity and to the corresponding action, condition or wait.
09 / Event orchestration
In developmentBlazeBEP: coordinate processes from events.
Events that give your processes context. Blaze Event Platform is designed to receive what happens across different systems, relate it to its context and coordinate processes through workflows. Its development brings events, entities, correlation and integration capabilities together in a traceable platform.
Problem and audience
For processes that span several tools
Scope begins with the operating need, the people involved and the systems already in place.
An update in one system can begin another process. Integration teams need to identify the event, relate it to the correct entity and define which action or wait comes next. BlazeBEP addresses that journey through an event-driven architecture.
Use cases
Situations where it adds context.
Reference examples based on the documented scope. Their application depends on project configuration and validation.
Record an event
Bring a fact into a common entry point and preserve its journey.
Relate context
Associate identities, entities and facts that come from different systems.
Coordinate a workflow
Combine actions, waits, conditions and timing within a traceable execution.
In development
What we are developing.
These capabilities describe the documented product direction; they do not announce immediate commercial availability.
Event intake and record
A common entry point for bringing in events and reviewing their journey.
Context and entities
Tools for relating identities, facts and entities that come from different systems.
Correlation
Rules for interpreting sequences, counts or the absence of an expected event within a process.
Workflows
Flows that combine actions, waits, conditions and timing to coordinate an execution.
Capability catalog
A registry of the operations an integration declares and can make available to the process.
API and MCP access
Interfaces for building integrations and exposing capabilities according to configured scope and permissions.
Before you start Availability and scope are subject to validation. Demonstration connectors are not presented as active integrations, and no example assumes a production connection to external systems.
Reference example
An example of coordination.
Illustrative example: a demonstration event starts a workflow, relates an entity’s context, executes a simulated action and waits for the next event. The journey shows how the process is coordinated without assuming production connections to external systems.
Its place in the ecosystem
A clear responsibility.
BlazeConnector focuses on adapting systems and their interfaces. BlazeBEP coordinates events and workflows. BlazeDSP focuses on following service cases. These responsibilities help select the right tool; every connection between products is validated for the corresponding project.
Related products
Explore adjacent responsibilities.
A thematic relationship does not mean an active integration exists between products.
In development
Confirm status and scope with the team.
BlazeBEP is in development. Access and available integrations are confirmed with the team. Platform examples may use simulated services and must be distinguished from a real implementation.