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
Wednesday, 4 November 2026
iFlowTailor“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 Firefox1 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.
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.
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 sourcesiFlowTailor recognises tenant, package and iFlow1 as soon as you open it in the editor. Everything else refers to exactly that iFlow – no copying, no second login.
A hundred failed messages, one cause: grouped by error signature2, with a suggested solution from 23 known error patterns.
REST, OData and SOAP with environments and assertions, through the Cloud Connector if you need it3.
XSD editor, XSLT mapping as a diagram, XPath with one click4 and sample payloads from XSD, WSDL or OData.
Your naming standard as a rule file, checked live and shown as a rate per package5.
Alias, type and expiry date – and where it is used, down to the step6. Private keys stay untouched.
Quick Review checks the open iFlow against 40 rules in six categories7 – 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 policy8 switches rules off, reweights them or adds your own – then every iFlow is checked against your standard, not ours.
Everything for development →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 release9.
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 →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-compatible19, 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 →Review before deployment, testing without Postman, Groovy without the deploy loop.
Team policy, your own rules, tenant health and cost at a glance.
Dependencies, system map, migration analysis and security posture.
Errors by root cause, certificates, drift, trace and load forecast.
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 ideas21, the quote is binding – and during the beta22 all features are free.
Community
€0forever
Developers and operations staff who build, review and run individual iFlows.
Coacheverything in Community +
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.
Proeverything in Coach +
approx. €19per user and month, billed annually
Developers and operations teams who search, debug and compare across many iFlows every day.
Teameverything in Pro +
from approx. €2,500per tenant and year
Integration leads, platform teams and architects who are responsible for a tenant.
Enterpriseeverything in Team +
on requestframework agreement
Organisations with many tenants and users, central browser management and a procurement process.
A review tool that only knows its advantages has not reviewed itself. Here is our list.
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.
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.
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.
Browser extension for Chrome, Edge and Firefox ↑Product · iFlowTailor product documentation, README and Security Whitepaper, section 1 · checked on 2026-11-04
Error analysis by cause ↑Product · iFlowTailor product documentation, User guide, Error analysis · checked on 2026-11-04
Test Studio and relay ↑Product · iFlowTailor product documentation, User guide, Test Studio; helper iFlows · checked on 2026-11-04
XML Workshop ↑Product · iFlowTailor product documentation, Changelog 1.0.0, XML Workshop · checked on 2026-11-04
Naming Studio ↑Product · iFlowTailor product documentation, User guide, Naming Studio · checked on 2026-11-04
Security material as metadata only ↑Product · iFlowTailor product documentation, Security Whitepaper, section 2 · checked on 2026-11-04
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
Team policies and custom rules ↑Product · iFlowTailor product documentation, Enterprise rollout and Security Whitepaper, section 5 · checked on 2026-11-04
“In the works”: built, not yet in any release ↑Product · iFlowTailor product documentation, Changelog, “Unreleased” section, 4 November 2026 · checked on 2026-11-04
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
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
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
Privacy guard (in the works) ↑Product · iFlowTailor product documentation, Changelog, “Unreleased” section, Privacy guard · checked on 2026-11-04
No vendor server, no telemetry ↑Product · iFlowTailor product documentation, Security Whitepaper and the extension’s privacy policy · checked on 2026-11-04
Existing SAP session, no SAP password ↑Product · iFlowTailor product documentation, Architecture decision 0002 and Security Whitepaper, section 2 · checked on 2026-11-04
Read-only by default, writes only with a preview ↑Product · iFlowTailor product documentation, Security Whitepaper, section 2 · checked on 2026-11-04
Licence verified offline ↑Product · iFlowTailor product documentation, Editions, technical section · checked on 2026-11-04
Secrets encrypted locally ↑Product · iFlowTailor product documentation, Security Whitepaper, section 3 · checked on 2026-11-04
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
iFlow from requirement ↑Product · iFlowTailor product documentation, Changelog 1.0.0, iFlow from requirement · checked on 2026-11-04
Editions and price ideas ↑Product · iFlowTailor product documentation, Editions; Coach edition proposal · checked on 2026-11-04
Beta: all features unlocked ↑Product · iFlowTailor product documentation, Editions, technical section; licence key configuration · checked on 2026-11-04
Distribution via browser policy ↑Product · iFlowTailor product documentation, Enterprise rollout · checked on 2026-11-04
Message Usage ↑Product · iFlowTailor product documentation, Changelog 1.0.0, Message Usage · checked on 2026-11-04
Your question isn’t here? Talk to me: +43 664 1964199 office@clouddna.at Demo on your tenant
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.