Use Cases

One integration model. Different outcomes.

QIP keeps the same chain understandable from its first design decision through deployment and production support.

Integration developer

Build and evolve integration flows faster

Use the visual graph, reusable services, mapping tools, and an extensive element library to turn integration requirements into deployable chains.

  1. 1Model the flow on the graph
  2. 2Transform messages and call services
  3. 3Save a snapshot and deploy

Application developer

Connect an application without owning integration plumbing

Expose and consume integrations through familiar protocols while the platform handles routing, transformations, retries, and service connectivity.

  1. 1Describe the endpoint or event
  2. 2Reuse a governed service definition
  3. 3Observe processing by session

Solution architect

Keep complex integration landscapes understandable

Review chain structure, service dependencies, sequence diagrams, snapshots, and generated design documentation from one model.

  1. 1Review dependencies
  2. 2Compare snapshots
  3. 3Document the integration design

Platform engineer

Run integration workloads consistently

Deploy platform services and engine domains on Kubernetes, manage runtime configuration, and scale execution independently from design-time services.

  1. 1Configure the platform
  2. 2Deploy engine domains
  3. 3Track chain deployment state

Operations and support

Find the failing step, not just the failed request

Search recorded sessions, inspect exchanges and element-level context, follow correlation data, and retry eligible processing from checkpoints.

  1. 1Locate the session
  2. 2Inspect element context and errors
  3. 3Resolve or retry with evidence