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.”
iFlowTailor runs as a browser extension right next to the iFlow editor – no backend, no extra login, your data stays in the browser. Five editions, each including everything in the one before. The amounts are price ideas1; the quote is binding.
Beta While the beta runs, all features are free2 – including Pro, Team and Enterprise. With the first licence key, the split below applies.
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.
Pro pays off when someone is responsible for a whole tenant. If you are building your third iFlow, you need something else: a build plan, a check against the open iFlow and someone who remembers what was missing last time. For that we propose an edition of its own – cheaper than Pro, and Pro includes all of it.
At its centre is the Implementation Coach3 from version 1.2.0 – currently part of Pro in the app. It comes with the Restart guide4, because error handling and restart are exactly what is most often missing in first projects.
Click a feature to go to its description and source. With the next version, Pro gains debugging and testing without a deploy; stack traces and the Privacy guard come to everyone in Community.
| Feature | Community | Coach | Pro | Team | Enterprise |
|---|---|---|---|---|---|
| Develop | |||||
| Quick Review | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| Payload tools and Groovy Lint | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| XML Workshop | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| Test Studio | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| Adapter advisor | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| Naming Studio | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| Groovy snippets | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| Groovy Runner | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Test suites | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Migration analysis, ISA-M, data lineage | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Documentation generator | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Restart guide | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| Debugging and testing | |||||
| Inline debugger in the editor In the works | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Run comparison: good vs. bad In the works | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Watched values In the works | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Trace switch In the works | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Variable inspector In the works | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| iFlow simulator In the works | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Trace as a regression test In the works | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Path coverage In the works | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Contract check In the works | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Test suite from the specification In the works | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Test gate before deploy In the works | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| DEV against QA In the works | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Operations | |||||
| Error analysis | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| Deployments with drift | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| Certificates | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| Message Monitor and runtime data | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| Data Store and Message Store per iFlow Beta | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| Trace Explorer and Message Journey | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Runtime heatmap and performance | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Not deployed | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Message forecast | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Correlation graph | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Endpoint catalog | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| Message Usage Beta | ${u.no} | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} |
| Access Policies and Number Ranges Beta | ${u.no} | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} |
| Downtime optimizer | ${u.no} | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} |
| Stack trace decoder In the works | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| Root cause search with a checked fix In the works | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Incident report In the works | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Ask the monitor In the works | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Morning briefing In the works | ${u.no} | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} |
| Tenant and architecture | |||||
| Dependencies | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| Tenant index and grep | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Tenant Compare | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Version Diff and changelog | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Header and property finder | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Externalised parameters | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Tenant Health | ${u.no} | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} |
| Landscape and cleanup | ${u.no} | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} |
| System map and outage analysis | ${u.no} | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} |
| Message flow analysis | ${u.no} | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} |
| Security | |||||
| Security Material | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| Log analysis | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Vulnerability check | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Security Risk Radar | ${u.no} | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} |
| Privacy guard In the works | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| Learning with the Coach | |||||
| Implementation Coach | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| Live check against the iFlow | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| Learning path and flashcards | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| Versioning advisor | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| Ask Tailor | |||||
| Ask Tailor | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Advisor in the views | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| iFlow from requirements Beta | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Why is field X empty? In the works | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} | ${u.yes} |
| Team and rollout | |||||
| Command palette and audit log | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} | ${u.yes} |
| Policy Studio | ${u.no} | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} |
| Custom review rules | ${u.no} | ${u.no} | ${u.no} | ${u.yes} | ${u.yes} |
| Central rollout | ${u.no} | ${u.no} | ${u.no} | ${u.no} | ${u.yes} |
| Price | €0forever | approx. €9per user and month, billed annually | approx. €19per user and month, billed annually | from approx. €2,500per tenant and year | on requestframework agreement |
For a quote we need three details: tenants, users, preferred start date. We sort out the rest in 30 minutes.
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.
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
Implementation Coach ↑Product · iFlowTailor product documentation, Changelog 1.2.0, Implementation Coach · checked on 2026-11-04
Restart guide ↑Product · iFlowTailor product documentation, Changelog 1.1.0, Restart guide · 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
No vendor server, no telemetry ↑Product · iFlowTailor product documentation, Security Whitepaper and the extension’s privacy policy · checked on 2026-11-04
Licence verified offline ↑Product · iFlowTailor product documentation, Editions, technical section · 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
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.