iFlowTailor 1.2.0 is out (3 November 2026): Implementation Coach, endpoint catalog, message flow analysis and downtime optimizer. In the works: debugging in the editor and testing without deploying. What’s new → +43 664 1964199Book a demo →
The workbench for SAP Cloud Integration

Ten tabs closed. One panel open.

Monitor, Postman, XPath tester, keystore, the Excel sheet with the naming rules: if you build iFlows, you work in ten windows today. iFlowTailor is a browser extension for Chrome, Edge and Firefox that puts all of this in a side panel next to the iFlow editor – with Health Score, errors by root cause, Test Studio and search across the whole tenant.

The small numbers are sources: tap one to see where a statement comes from and when it was checked; all of them are listed at the bottom of the page.

  • No backend, no new login
  • Read-only by default
  • Community edition free
  • No cookies on this site

iFlow flywheel – Every iFlow makes the next one better – because the rules, snippets, tests and docs from this round are already there in the next.

  1. Build (XML Workshop · Snippets, Community, in the product): You build in the SAP editor as usual. Right next to it: XSD editor, XSLT mapping as a diagram, XPath by click and Groovy snippets – no second tab. In the next round: What you saved as a snippet or sample last round is now a template. With Pro, Ask Tailor drafts the next iFlow from your requirements.
  2. Review (Quick Review, Community, in the product): One click: health score from 0 to 100, findings by severity with reason, location and fix. Clicking a finding jumps to the step in the editor. In the next round: Accepted risks are listed with their justification, and the team rules are checked too. Today’s score is the bar for tomorrow.
  3. Test (Test Studio · Groovy Runner, Community, in the product): REST, OData and SOAP with environments and assertions, through the Cloud Connector if you need it. With Pro, the Groovy script runs in the Runner against a sample payload, without a deploy. In the next round: Collections and test suites from the last round run again before and after the deploy.
  4. Compare (Version Diff · Tenant Compare, Pro, in the product): Before the transport: version against version, DEV against PRD. The changelog suggestion lands in SAP’s “Save as Version” dialog. In the next round: The version history shows what is new since your last visit – and who changed it.
  5. Operate (Monitor · Error analysis, Community, in the product): Failed messages grouped by cause instead of one by one, with a suggested fix. Plus deployments with drift and certificates with their expiry dates. In the next round: The cause is known, and so is the fix. With Pro, Trace Explorer and Message Journey follow the message across several iFlows.
  6. Understand (Forecast · Heatmap, Pro, in the product): When does the load arrive, which step is the slowest, which iFlow has been changed but not deployed? In the next round: More history, a more accurate forecast – the view measures its own accuracy and shows it.
  7. Document (Documentation generator, Pro, in the product): Interface documentation from the tenant as Markdown, PDF or straight into Confluence. In the next round: The docs are accurate because they come from the tenant. Whoever builds the next iFlow starts with them – back to station 1.

Fig. 1 — The iFlow flywheel. Tap a station or let it run; all five flywheels.

REVIEWED.

A word that today often means a screen share on a Friday afternoon. With iFlowTailor it means a score with a formula, and every finding with a reason and a fix. And the yellow highlights on this page? Each one has a source with the date it was checked – we review our own sentences too.

All sources
Ten tabs, one panel

What is open alongside today – and where it lives now.

iFlowTailor recognises tenant, package and iFlow as soon as you open it in the editor. Everything else refers to exactly that iFlow – no copying, no second login.

  1. Instead of the monitorErrors by root cause

    A hundred failed messages, one cause: grouped by error signature, with a suggested solution from 23 known error patterns.

  2. Instead of PostmanTest Studio

    REST, OData and SOAP with environments and assertions, through the Cloud Connector if you need it.

  3. Instead of an XPath testerXML Workshop

    XSD editor, XSLT mapping as a diagram, XPath with one click and sample payloads from XSD, WSDL or OData.

  4. Instead of ExcelNaming Studio

    Your naming standard as a rule file, checked live and shown as a rate per package.

  5. Instead of the keystore tabSecurity Material

    Alias, type and expiry date – and where it is used, down to the step. Private keys stay untouched.

Quick Review

One click. One score. And why.

Quick Review checks the open iFlow against 40 rules in six categories – security, error handling, performance, maintainability, operations, standards. The Health Score is not a black box: each rule deducts from the remaining score – the first finding 15 % if critical, 7 % if high, 3 % if medium, each further finding of the same rule half as much. A bad iFlow tends towards 0 yet stays distinguishable from a very bad one.

Every finding tells you where it is, why it matters and what the fix looks like. One click takes you to the step in the editor. What your team leaves as it is on purpose, you accept with a reason; the report goes into the pull request or the ticket as Markdown.

In a team, the team policy switches rules off, reweights them or adds your own – then every iFlow is checked against your standard, not ours.

Everything for development →
tenant.integrationsuite.cfapps.eu10.hana.ondemand.com · Orders_S4_Inbound
Fig. 2 — Quick Review next to the iFlow editor. Tap a finding: the step lights up, like the jump into the editor in the extension. Rules, texts and deductions as in version 1.2.0; the iFlow, systems and alias are made up.
In the works · next version

Debug where you build. Test without deploying.

iFlowTailor lays every run directly onto your iFlow diagram, sends messages through your iFlow locally and looks for the root cause before you read the logs. Built, but not yet in any release.

  • Inline debugger.Steps in green, red or grey, body, headers and properties before and after every step, time travel back to the point where a field goes empty. Pro
  • iFlow simulator.The message runs through the iFlow locally, without a deploy; one click turns a real run into a regression test. Pro
  • Root cause search with a checked fix.“Failing since version 1.4.2 was deployed at 14:02” – and the fix is checked before you see it. Pro
  • Stack traces and Privacy guard.The cause instead of 80 lines of Java, and personal data masked before it ends up in an export. Community
Architecture

No server. No new sign-in. No writing out of the box.

A tool that can read every iFlow on a tenant has to explain itself. That is why we built iFlowTailor so that there is little to explain.

Security in detail →
  1. Data stays in the browser and in the tenant. No CloudDNA GmbH server, no telemetry, updates only through the browser stores.
  2. Your role applies. The extension uses your existing SAP session and stores no SAP password – it can never do more than you can.
  3. Writing only with a preview. Write actions are off out of the box; once enabled, they go through a dialog with before and after, and into the audit log.
  4. No licence server. The licence is signed and checked offline; secrets are stored encrypted in the browser.
Ask Tailor

Your AI. Your key. Masked.

Ask Tailor explains errors in plain language, looks for the cause of a failed run, drafts Groovy scripts and changelogs – with the model you configure yourself: Anthropic, Gemini, Mistral, SAP AI Core, Azure OpenAI or OpenAI-compatible, including local models.

The request goes straight from your browser to your endpoint. Before anything is sent, masking replaces hosts, email addresses, tokens and your own terms with placeholders; the panel shows you what goes out. Ask Tailor stays off until you switch it on – and a team policy can block it.

All 18 Ask Tailor tasks →
  • Explain.Errors in plain language, the cause of a run, the path of a sample payload through the iFlow.
  • Draft.Groovy script, mapping suggestion, changelog text – and, in beta, a complete iFlow from your requirements, never deployed.
  • Advise.Recommendations in the views, for example on adapters or load – always as a suggestion, never as an action.
Who it’s for

For everyone who builds, owns or runs iFlows.

  1. Build and review

    Integration development

    Review before deployment, testing without Postman, Groovy without the deploy loop.

  2. Enforce standards

    Integration leads

    Team policy, your own rules, tenant health and cost at a glance.

  3. Understand the tenant

    Architecture

    Dependencies, system map, migration analysis and security posture.

  4. Keep it running

    Operations and AMS

    Errors by root cause, certificates, drift, trace and load forecast.

Editions

Start for free. Extend for the tenant.

Community covers the single iFlow and day-to-day operations. Coach supports you while you learn, Pro adds the whole tenant, Team adds governance, Enterprise central rollout. The amounts are price ideas, the quote is binding – and during the beta all features are free.

Community

Everything for your iFlow and day-to-day operations.

€0forever

Developers and operations staff who build, review and run individual iFlows.

  • Quick Review
  • Payload tools and Groovy Lint
  • XML Workshop
  • Test Studio
  • Adapter advisor
  • Naming Studio

Install for free

Coacheverything in Community +

Better with every iFlow – with a coach next to the editor.

approx. €9per user and month, billed annually

Beginners, juniors and people moving over from SAP PI/PO who want to learn best practices while building rather than reading up on them. Special terms are available for training and trainee programmes.

  • Restart guide
  • Implementation Coach
  • Live check against the iFlow
  • Learning path and flashcards
  • Versioning advisor
  • Special terms for training and trainee programmes

Ask about Coach

Proeverything in Coach +

The whole tenant in view – with Ask Tailor.

approx. €19per user and month, billed annually

Developers and operations teams who search, debug and compare across many iFlows every day.

  • Groovy Runner
  • Test suites
  • Migration analysis, ISA-M, data lineage
  • Documentation generator
  • Trace Explorer and Message Journey
  • Runtime heatmap and performance

Ask about Pro

Teameverything in Pro +

Governance, cost and security for the whole tenant.

from approx. €2,500per tenant and year

Integration leads, platform teams and architects who are responsible for a tenant.

  • Message Usage (Beta)
  • Access Policies and Number Ranges (Beta)
  • Tenant Health
  • Landscape and cleanup
  • System map and outage analysis
  • Security Risk Radar

Request a quote

Enterpriseeverything in Team +

For corporate IT: rolled out centrally, covered by contract.

on requestframework agreement

Organisations with many tenants and users, central browser management and a procurement process.

  • Central rollout
  • Support SLA and rollout support
  • Framework agreement with purchase order and invoice

Get in touch

To be honest

When you should not use iFlowTailor.

A review tool that only knows its advantages has not reviewed itself. Here is our list.

  • You are looking for an integration platform.iFlowTailor replaces neither SAP Integration Suite nor the iFlow editor. It sits next to them and works with what your tenant and your role allow.
  • Your browser does not allow extensions.Then IT has to come first. For them there is rollout through browser policy – with a fixed policy that users cannot change.
  • You need Message Usage guaranteed today.Message Usage, Access Policies and Data Store contents use interfaces that SAP does not document as a public API. We label them beta and confirm them on the tenant with our first customers.
  • You want the tool to do the repairs.iFlowTailor suggests the fix, jumps to the step and checks again afterwards. Changing, saving and deploying stays with you – on purpose.
30 minutes, your tenant

Bring your trickiest iFlow.

We open it together: Health Score, findings with fixes, errors by root cause, dependencies. Or install it yourself right away – the Community edition is free.

The Tailor family

Twelve siblings – each for its own craft.

Every Tailor solves a problem we know up close. Most siblings share the Tailor-Plattform with EU data residency and an AI layer. iFlowTailor is the tool among them: no server, no data storage, just an extension next to your iFlow editor. The language is different – JournalTailor talks about debit and credit, ProbeTailor about PASS and FAIL, iFlowTailor about steps, adapters and health score.

Sources on this page

The superscript numbers in the text point here. Tap one to see the source right where it is used; all sources of this website are listed on one page.

  1. 1

    Browser extension for Chrome, Edge and Firefox ↑Product · iFlowTailor product documentation, README and Security Whitepaper, section 1 · checked on 2026-11-04

  2. 2

    Error analysis by cause ↑Product · iFlowTailor product documentation, User guide, Error analysis · checked on 2026-11-04

  3. 3

    Test Studio and relay ↑Product · iFlowTailor product documentation, User guide, Test Studio; helper iFlows · checked on 2026-11-04

  4. 4

    XML Workshop ↑Product · iFlowTailor product documentation, Changelog 1.0.0, XML Workshop · checked on 2026-11-04

  5. 5

    Naming Studio ↑Product · iFlowTailor product documentation, User guide, Naming Studio · checked on 2026-11-04

  6. 6

    Security material as metadata only ↑Product · iFlowTailor product documentation, Security Whitepaper, section 2 · checked on 2026-11-04

  7. 7

    Quick Review: Health Score with 40 rules ↑Product · iFlowTailor product documentation, Rule catalogue and score formula (packages/rules), status after 1.1.0 · checked on 2026-11-04

  8. 8

    Team policies and custom rules ↑Product · iFlowTailor product documentation, Enterprise rollout and Security Whitepaper, section 5 · checked on 2026-11-04

  9. 9

    “In the works”: built, not yet in any release ↑Product · iFlowTailor product documentation, Changelog, “Unreleased” section, 4 November 2026 · checked on 2026-11-04

  10. 10

    Debugging in the editor (in the works) ↑Product · iFlowTailor product documentation, Changelog, “Unreleased” section: inline debugger, run comparison, watched values, trace switch, variable inspector · checked on 2026-11-04

  11. 11

    Testing without deploying (in the works) ↑Product · iFlowTailor product documentation, Changelog, “Unreleased” section: iFlow simulator, trace as regression test, path coverage, contract check, test suite from specification, test gate, DEV against QA · checked on 2026-11-04

  12. 12

    Root cause search, incident report, ask the monitor, morning briefing (in the works) ↑Product · iFlowTailor product documentation, Changelog, “Unreleased” section; editions, cut for debugging, testing and AI · checked on 2026-11-04

  13. 13

    Privacy guard (in the works) ↑Product · iFlowTailor product documentation, Changelog, “Unreleased” section, Privacy guard · checked on 2026-11-04

  14. 14

    No vendor server, no telemetry ↑Product · iFlowTailor product documentation, Security Whitepaper and the extension’s privacy policy · checked on 2026-11-04

  15. 15

    Existing SAP session, no SAP password ↑Product · iFlowTailor product documentation, Architecture decision 0002 and Security Whitepaper, section 2 · checked on 2026-11-04

  16. 16

    Read-only by default, writes only with a preview ↑Product · iFlowTailor product documentation, Security Whitepaper, section 2 · checked on 2026-11-04

  17. 17

    Licence verified offline ↑Product · iFlowTailor product documentation, Editions, technical section · checked on 2026-11-04

  18. 18

    Secrets encrypted locally ↑Product · iFlowTailor product documentation, Security Whitepaper, section 3 · checked on 2026-11-04

  19. 19

    Ask Tailor with your own model and masking ↑Product · iFlowTailor product documentation, Security Whitepaper, section 4; AI providers and tasks · checked on 2026-11-04

  20. 20

    iFlow from requirement ↑Product · iFlowTailor product documentation, Changelog 1.0.0, iFlow from requirement · checked on 2026-11-04

  21. 21

    Editions and price ideas ↑Product · iFlowTailor product documentation, Editions; Coach edition proposal · checked on 2026-11-04

  22. 22

    Beta: all features unlocked ↑Product · iFlowTailor product documentation, Editions, technical section; licence key configuration · checked on 2026-11-04

  23. 23

    Distribution via browser policy ↑Product · iFlowTailor product documentation, Enterprise rollout · checked on 2026-11-04

  24. 24

    Message Usage ↑Product · iFlowTailor product documentation, Changelog 1.0.0, Message Usage · checked on 2026-11-04

Frequently asked

Short answers.

What is iFlowTailor?
iFlowTailor is a browser extension for SAP Integration Suite (SAP Cloud Integration, CPI) in Chrome, Edge and Firefox. It puts review, testing, error analysis and operations in a side panel next to the iFlow editor: Health Score with findings and fixes, errors grouped by root cause, Test Studio, XML Workshop, tenant search, comparison and documentation. It is made by CloudDNA GmbH, Austria.
Do I need a server or a new account?
No. iFlowTailor has no backend and uses the SAP session you are already signed in with in your browser. Your SAP role applies – the extension can never do more than you can. Data stays in the browser and in the tenant.
Can iFlowTailor break anything on my tenant?
Not out of the box: write actions are switched off. If you enable them, you see a dialog with before and after for every action, and every result is recorded in the local audit log. A team policy can enforce read-only.
Does Ask Tailor send my iFlows to an AI?
Only if you switch Ask Tailor on, and only to the model you configure yourself – Anthropic, Google Gemini, Mistral, SAP AI Core, Azure OpenAI or an OpenAI-compatible endpoint, including a local one. Before anything is sent, masking replaces hosts, email addresses, tokens and your own terms with placeholders. Script code is only sent after you explicitly allow it.
What does iFlowTailor cost?
The Community edition is free. For Pro, Team and Enterprise we have published price ideas (Pro approx. €19 per user and month, Team from approx. €2,500 per tenant and year); the quote is binding. While the beta runs, all features are free.
Is iFlowTailor an SAP product?
No. iFlowTailor is a product of CloudDNA GmbH. It works with SAP Integration Suite and replaces neither it nor the iFlow editor.

Your question isn’t here? Talk to me: +43 664 1964199 office@clouddna.at Demo on your tenant

Contact

Bring your hardest iFlow.

In 30 minutes we open it together on your tenant: health score, findings with fixes, errors by cause, dependencies. No slides, no newsletter. I will get back to you within one working day.

Martin KochManaging Director, CloudDNAI read every request myself and reply personally.