Talk to your SAP Integration Suite, navigate complex iFlows without dragging across the canvas, and debug every trace step to find where a value became null and why.
No tenant to connect? Upload an exported iFlow ZIP and get an AI explanation — no tenant required.
Most SAP integration work isn't building iFlows.
It's understanding them. Monitoring them.
Finding failures before the business does.
CPI Copilot means less time searching dashboards, and more time solving the actual problem.
Steps turns a complex iFlow into its true execution order and jumps to any palette with one click. Trace follows the selected SAP message and finds the first place its data went wrong.
No earlier body value, non-empty header or exchange property was found. Seven later steps inherited the same null.
A red row in the log is the easy case. These are the ones that reach the business first.
A scheduled iFlow never ran. Nothing technically failed, so nothing alerted anyone — and your FAILED count still says zero. You find out when the business calls.
Your integrations still succeed. But today's runtime is 3x yesterday's, messages are piling up in retry, and nothing in the dashboard is red yet.
Open the MPL. Open the log. Open the package. Open the artifact. Cross-reference. Repeat — every single time something breaks.
Built around the work you actually do — understanding and operating your integrations.
Read a large iFlow in true execution order and jump directly to the step you need.
Follow one message across every captured step and see where its data changed.
See what changed between two iFlow states without reading raw BPMN by hand.
Plain-English answers from live data.
Watch only the integrations you care about — and hear about it the moment they break, by email.
See what's stuck in your queues — and know exactly what to do about it.
Upload a ZIP — no tenant required.
Ask for any report and have it emailed.
Know what got slower, and which step did it.
Generates roughly 60% of an iFlow — the structure, so you spend your time on the logic.
We're still refining accuracy. It's strongest on standard patterns — complex custom mappings still belong to you.
Three steps, one read-only credential, nothing installed in your tenant.
A monitoring-only OAuth client in your tenant. Least access possible.
Paste it into Settings. We verify the connection immediately.
Choose the integrations that matter. Monitoring starts right away.
The boundaries are in the code, not in a promise.
It reads message logs and metadata. There is no code path that lets monitoring change anything in your tenant.
Generation is the only feature that writes, it runs only when you explicitly click it, and only into the package you choose. Nothing happens in the background.
Every tenant credential is encrypted with a key unique to your account, and never shown back to you or anyone else.
Cloud monitoring reads errors and operational metadata. Trace payloads are inspected inside your SAP browser tab and are not sent to our backend or an AI provider.
Prefer your own Azure OpenAI, Anthropic or Gemini key? Use it. Your key, your bill, your data path.
We count without downloading. A tenant doing 130,000 messages an hour answers as fast as one doing ten — and your volume never changes what you pay.
CPI Copilot sits on top of SAP Integration Suite — it doesn't replace anything.
| Today | With CPI Copilot |
|---|---|
| Search through dashboards | Ask in plain English |
| Read the MPL manually | AI root-cause analysis |
| Drag around a large iFlow canvas | Execution-order list with click-to-locate |
| Compare trace steps by hand | First missing field and source identified |
| Build reports by hand | Reports generated and emailed |
| Hunt for which package it's in | Instant discovery |
| A missed run nobody notices | An alert before the business calls |
| A queue quietly backing up | Diagnosed — retry or move, in one click |
| Raw runtime numbers | What changed, and which step did it |
The public beta is free. Flat pricing comes later — your message volume will never change what you pay.
No credit card required
Enterprise plans coming soon
Navigate the iFlow in execution order, open the exact trace run, and find the first step where the data went wrong.