ODataTailor 0.1.0 is built (21 November 2026): the workbench for OData services – free, no account, no server. What’s inside → +43 664 1964199Contact →
The story behind ODataTailor – and behind all the Tailors

Never give up. The sky is the limit.

My name is Martin Koch. Formerly a pilot and air traffic controller, in SAP integration since 2006, SAP Champion, author of 17 books for SAP PRESS, today the founder of CloudDNA – and a single father of three. With 24 people from southern Burgenland we build a family of industry software. ODataTailor is one of its tools for SAP developers and sits close to what my team and I wrote about in the books on Fiori elements and SAPUI5: annotations, bindings and OData. This is the story behind it.

01Who I am

Every life counts. Not 999 out of 1,000.

Before I built software, I learned two professions in which there is no such thing as 99.9 %: airline pilot with Austrian Airlines and air traffic controller with Austro Control. The entrance tests for both are among the toughest in the world – the DLR test in Hamburg with a failure rate north of 98 %, the multi-day assessment at Austro Control in which people find out how resilient they really are. Tens of thousands apply, a few dozen get through. I passed both.

IQ measures how fast someone thinks. The cockpit test measures how calm someone stays when the display at the top right has been showing something wrong for five seconds and you have to be the first to notice. In aviation, the second one counts. And above everything stands one principle: every life counts. Not 999 out of 1,000. All of them.

A professional pose or an operating system? When I took up tennis again in autumn 2025 after a thirty-year break, I looked for a coach who had worked with ATP top-10 players for decades. Not because I want to go on tour – but because when I take something seriously, I want to know where my ceiling really is.

02At home

Three children, one father, no autopilot.

I am a single father of three children. The two younger ones are of school age, the eldest is an adult. Anyone who knows this knows: there is no roster that holds and no day that ends the way it was planned. You learn to set priorities in seconds – and to re-sort them the next morning.

My eldest son is severely disabled. He lives with a rare genetic defect, a microdeletion. He has taught me more about patience, reliability and what really matters than any assessment and any project.

My three children are the centre of my life and my motivation – every single day.

When I say “every life counts”, it is no longer a phrase from the cockpit. It is everyday life. And it is the reason I build software that gives people time back – time that is needed more urgently elsewhere.

My life has changed massively through all of this. I have become even more structured than I was used to from the cockpit – and that is exactly why, in the early morning hours before the house wakes up, there is room every day for an hour of sport: kettlebell, rope skipping, boxing. Not despite the responsibility, but because of it.

I am convinced: what matters most is the daily routine.

Big goals are not reached with big days, but with many ordinary ones that reliably start the same way. That is exactly how we build software: it should carry the daily routine – unspectacular, reliable, every day – so that head and time remain for the unplannable.

Never give up.
The sky is the limit.

My motto. Not a poster on the wall – a decision, every morning.

03One sentence in Hamburg

How KSIC became CloudDNA.

I founded CloudDNA more than ten years ago – originally not under that name. I came from SAP, where I had spent years at one of the largest software companies in the world. A safe harbour. I left it anyway.

It started with an unwieldy name: KSIC GmbH – Koch Security, Integration and Cloud Consulting. Four letters nobody could pronounce. Rescue came over dinner in Blankenese, Hamburg, at a fish restaurant on the Elbe. My old SAP colleague Jörg listened to my explanation for the third time, raised his glass and said a single sentence:

“Martin, you have the cloud in your DNA.”

Two weeks later KSIC GmbH was no longer called KSIC. Daniel, my first employee, was already there – on his very first business trip. (Daniel, I am still sorry about the turbot.)

We started in a tiny office in Oberwart. Today we work in the former Raiffeisen bank in Loipersdorf, in the middle of the spa and wine region of southern Burgenland, and draw on two talent schools you will not find on any world map: HTL Pinkafeld and the University of Applied Sciences Burgenland. The duo has become a team of 24 people, and we have published seventeen books with SAP PRESS – always from practice, never from marketing.

04The upheaval

Custom software was a red rag. Until 2023.

I built CloudDNA to create SAP integrations for large corporations – heavy software, paced in months. In that world custom software was avoided like the plague: too expensive, too slow, too risky.

Then came the language models.

I realised: this is not a gradual improvement, it is the upheaval that rewrites our craft. So I sat down myself and built software – at night, in my own editor, with the same tools I recommend to my team. You cannot explain AI-assisted development to anyone with a PowerPoint. You have to live it.

What used to take three months and a six-figure sum now takes weeks. Not because programmers work magic, but because copilots take over the drudgery and developers become what they should be: craftspeople with a head.

05We build it

From “We deliver” to “Wir bauen das”.

For more than ten years our promise was “We deliver”: a customer describes, we deliver. That made us big. But it has a limit: whoever only delivers what is ordered rarely builds what is needed.

That is why we are rebuilding ourselves. Consultants and developers are becoming forward deployed engineers and product owners. Forward deployed means: they sit where the problem arises – in the property management office, at the winery, in the law firm – and build on site. Product owner means: they stay until it is solved and own the product, not the ticket.

We deliverWir bauen das – we build it
Requirements documentData sample with real data
Ticket closedProblem solved
Months to the first resultWeeks, piloted next to the legacy system
Hand-over at project endResponsibility afterwards
Consultant at the customerForward deployed engineer and product owner

“Wir bauen das.” Three words you may only say to a customer if you mean them.

06We speak AI

Inside the AI bubble and, above all, outside it.

Inside the AI bubble everyone talks about models, benchmarks and agents. Outside – with the property manager running a thousand units, the winemaker in southern Burgenland, the restaurateur with twenty tables – a different question counts: Will this save me an hour tomorrow, and can I rely on it?

We translate between these worlds. We build with Claude by Anthropic every day and are well on the way to becoming an Anthropic partner. But what reaches the customer is not a model, it is a workflow that works:

  • The AI proposes, a human decides. More autonomy comes only after a passed probation period.
  • Every action is in the audit trail. What the AI did can be read back.
  • AI has to pay for itself. Own key, fixed cost cap per tenant.
  • Data stays where it belongs. Tenants separated down to the database.

Anthropic and Claude are trademarks of Anthropic PBC. The mention describes how we work.

07The Tailor family

Made to measure instead of standard with a hundred compromises.

Instead of just talking about AI-assisted development, we picked industries I know well enough – or in which I have friends who explain the problem to me until it sticks. Every Tailor shares the same foundation with its siblings, but speaks the language of its industry:

  • FrontTailor – for SAP Fiori development and operations, because in my projects I too often needed ten tabs, three transactions and a network trace to answer one single question: why is the app doing this?
  • iFlowTailor – for SAP integration, which I have been building since 2006: the tools for development and operations never did the job for me – so we are building the workbench for development, operations and administration in one.
  • AuthTailor – for single sign-on, because in my SAP projects logins keep failing without saying why. We first built the tracer for ourselves in iFlowTailor – now we give it to everyone for free.
  • ProbeTailor – for acceptance tests in SAP projects and business software, because in all my years of SAP consulting I have seen too many acceptance tests in Excel lists and too many screenshots in e-mails.
  • JournalTailor – for accounts payable before SAP, BMD and DATEV, because in SAP projects I have too often watched invoices being retyped although the posting behind them has long been routine.
  • DocumentTailor – for SAP shops, because I spent fifteen years building forms on SAP Adobe Document Services and did not want to leave the succession question unanswered any longer.
  • RecordTailor – for everyone who needs a DMS that does not just store but reads – because I have too often seen someone secretly open Excel because the DMS is too slow.
  • ImmoTailor – for property managers and developers, because accounting, maintenance and portals get in each other’s way there more than anywhere.
  • TaxTailor – for tax firms, because a friend told me about his Windows terminal server over a glass of wine.
  • DineTailor – for restaurants, because for years I have been sitting at other people’s tables selling champagne to restaurateurs.
  • StayTailor – for hotels, because the spa region is full of businesses ducking under the booking portals’ terms.
  • MeetingTailor – for meetings and boards, because foundation boards, councils and club committees among my friends keep describing the same late-night scene.
  • Weintailor – for winemakers, because we sit in the middle of a wine region and every other trip turns into a wine trip anyway.
  • BuildTailor – for construction and trades, because defects, plans and daily reports happen on site – not in the office.
  • ODataTailor – for OData services, because in my SAP projects almost every question about a Fiori app sooner or later becomes a question about its OData service. We first built the metadata explorer and the OData console in FrontTailor – now they are a workbench of their own, for any service and for free.

CloudDNA is therefore no longer just an SAP supplier, but a workshop with a growing product line. Bolder in business. Humanly the most honest thing we could do.

08Why ODataTailor

Every question about a Fiori app sooner or later becomes a question about its service. And the service answers in XML.

With Rene Glavanovits, Daniel Krancz and Maximilian Olzinger I wrote the books on SAP Fiori elements, SAPUI5 and full-stack development. They explain how annotations build a list report, how a binding fetches its data and how a request travels from the browser into the backend. What no book covers: what it is like when everything seems correctly annotated and the field is still missing. Between the screen and the database there are many layers:

  1. Fiori app
  2. Annotations
  3. $metadata
  4. Request
  5. Gateway
  6. Backend

And every layer has its own tool: the $metadata as XML in the browser, the request in Postman, the annotations in a second file, the error in the Gateway log, the role in SU53. Anyone hunting an error jumps between five windows – and still ends up assembling the URL by hand.

You read the service in pieces. You would need to understand it as a whole.

In aviation there is a chart for that. No pilot flies by a list of coordinates; you see the airspace, the airways and the restricted areas at a glance. That is exactly what I wanted for a service: the chart instead of the coordinates.

So we built the chart.

First in FrontTailor, our developer tools for SAP Fiori and UI5: the graphical metadata explorer and the OData console, right on the running app. Then it became clear that this question is not only asked by whoever sits in front of a running Fiori app. Anyone building a RAP service, testing a CAP service or wanting to know before a transport what changed in the $metadata needs the same workbench – without an app. That is why ODataTailor exists as an extension of its own, built from the same packages as FrontTailor.

BeforeWith ODataTailor
Reading $metadata as XMLTypes, navigations and annotations as a diagram
Assembling the URL by handA query from the metadata, with value help and as a sentence
Guessing why Fiori hides a fieldThe annotation that hides it, with the reason
Type a body, send, hopeChecks against the metadata, preview, PROD lock
“400 Bad Request” and an error numberThe cause and the matching transaction in one click

And why free? Because we open, query and check OData services in our own projects every day – and because everyone who builds, tests or runs Fiori apps does the same. ODataTailor is free, with no account and no licence. Whoever needs the workbench on the running app, with the recorder and bound controls, finds it in FrontTailor. Five ideas ODataTailor is built on:

  1. Idea 1 · The chart

    See first, then ask.

    A service with a hundred types is not a text to read from top to bottom. ODataTailor shows it as a diagram with explained annotations, and the path finder tells you which navigation gets you from A to B.

  2. Idea 2 · How the app asks

    Not just any query. Fiori’s.

    Most questions are: what does the user see? That is why ODataTailor builds the request a list report would send and shows the result the way the app shows it.

  3. Idea 3 · Clearance for one system

    Access only where it is needed.

    As an air traffic controller you give clearance for exactly one flight, not for the whole airspace. ODataTailor works the same way: access is requested per system, and no call goes out without your click.

  4. Idea 4 · Every life counts

    On PROD there is no “let’s try”.

    In the cockpit some switches sit under a guard. In ODataTailor, changing requests go only with preview and click – and not at all on production systems, not even when in doubt.

  5. Idea 5 · Cause before symptom

    “400” is not a finding.

    A status code says something went wrong, but not where. ODataTailor names the likely cause and the transaction where you find it – on the same system, one click away.

“Fiori shows nothing? Ask the service.” Not a slogan – it is how we work ourselves.

The Tailor family

Fifteen 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. ODataTailor is one of the browser tools: no server, no data stored with us, just a workbench in your browser. It grew out of FrontTailor’s OData console and metadata explorer – and it still lives there too.

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

    Books on SAP Fiori elements, SAPUI5 and full-stack development ↑Vendor · Rheinwerk Verlag (SAP PRESS), search “martin koch” · checked on 2026-11-05

  2. 2

    Grown out of FrontTailor, same packages ↑Product · ODataTailor product documentation, ADR-001 and ADR-010 · checked on 2026-11-21

  3. 3

    Free, no account and no licence ↑Product · Product owner decision of 21 November 2026 · checked on 2026-11-21

  4. 4

    Diagram with path finder and explained annotations ↑Product · ODataTailor product documentation, implementation plan, phase 1, diagram · checked on 2026-11-21

  5. 5

    Query like Fiori, Fiori preview, “Why does Fiori not show …” ↑Product · ODataTailor product documentation, implementation plan, phases 1 and 2 · checked on 2026-11-21

  6. 6

    Permissions: storage, host access per system ↑Product · ODataTailor product documentation, manifest (wxt.config.ts), ADR-004 and ADR-009 · checked on 2026-11-21

  7. 7

    No network call without a visible request ↑Product · ODataTailor product documentation, ADR-003 · checked on 2026-11-21

  8. 8

    PROD lock, fail-closed ↑Product · ODataTailor product documentation, ADR-007 and manifest (managed_schema) · checked on 2026-11-21

  9. 9

    Errors with a way out and SAP transactions ↑Product · ODataTailor product documentation, implementation plan, phase 2, errorAdvice · checked on 2026-11-21

Frequently asked

Questions about CloudDNA.

Who is behind ODataTailor?
CloudDNA GmbH from Loipersdorf in southern Burgenland, founded by Martin Koch – formerly an airline pilot and air traffic controller, in SAP integration since 2006, SAP Champion and author of 17 books for SAP PRESS, among them the books on SAP Fiori elements, SAPUI5 and full-stack development. The team has 24 people.
Why is ODataTailor free?
Because we open, query and check OData services in our own SAP projects every day. We first built the workbench for FrontTailor; as an extension of its own we give it to everyone for free – no account, no licence, no server.
What does “Wir bauen das” mean?
CloudDNA is changing from a service provider (“We deliver”) into a product builder: developers work as forward deployed engineers directly at the customer and own the product as product owners beyond the project.
What are the Tailors?
A family of CloudDNA software, most siblings on a shared foundation, the Tailor-Plattform: among others for SAP Fiori and UI5 (FrontTailor), OData services (ODataTailor), SAP Cloud Integration (iFlowTailor) and single sign-on (AuthTailor), all as browser extensions, plus acceptance testing, incoming invoices, documents, property management, tax advisory, hospitality, hotels, boards, winegrowing and construction.

Your question isn’t here? Talk to me: +43 664 1964199 office@clouddna.at Get in touch

Contact

Service stuck? Talk to us.

ODataTailor is free. If you need help – with an OData service from SEGW, RAP or CAP, with annotations for Fiori elements, with a stubborn error or for a workshop with your team – get in touch. I reply within one working day, personally.

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