RequestTailor Preview (22 November 2026): requests as files in Git, no account, offline – on the Mac, in the browser and in the pipeline. What’s inside → +43 664 1964199Contact →
The story behind RequestTailor – and behind all Tailors

Never give up. The sky is the limit.

My name is Martin Koch. Former pilot and air traffic controller, in SAP integration since 2006, SAP Champion, author at SAP PRESS, today founder of CloudDNA – and single father of three. With 24 people from southern Burgenland we build a family of software. RequestTailor is the member for APIs: a client in which the requests belong to you. 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:

  • 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.
  • 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.
  • RequestTailor – for APIs, because in my projects the requests we use to test a system too often lived in someone else's account instead of next to the code – and because a request that is green in the app should be green in the pipeline too.

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 RequestTailor

The request was in the wrong account. Again.

Almost every integration project has this moment. An interface test fails, and someone asks: “Which request did you test that with?” The answer is in a workspace only one colleague can open. Or in an export from last week. Or in a cURL command in the ticket, with a token in it that nobody should see any more.

  1. A colleague's workspace
  2. Export in the wiki
  3. cURL in the ticket
  4. Script for CI
  5. Token in the chat
  6. Screenshot in the acceptance report

The code lives in the repo, with review, history and pipeline. The requests we use to test exactly that code every day live everywhere else. And whoever needs them in the pipeline writes them again – so something is green in the app and red in CI.

A request is code. It belongs next to the code.

In aviation, what is not in the logbook did not happen. For requests that means: what is not a file in the repo cannot be reviewed, traced or run by a pipeline.

So we built an API client that is only a view on the folder.

RequestTailor keeps every request as a readable YAML file. The same core runs in the app, in the browser, in the pipeline and as an MCP server – what is green in the app is green in CI. And there are rules we gave ourselves before the first line of code was written.

In the project beforeWith RequestTailor
“Which request did you test that with?”The one in the repo, commit such-and-such
Token in the exportOnly the name in the repo, the value in the keychain
Everything again as a script for CIrt run with the same collection
An agent with full access to productionReading allowed, writing only with approval

Five rules RequestTailor is built on:

  1. Rule 1 · The logbook

    Files are the truth.

    One file per request, read and written byte for byte. Diffs work without special tools; the app is only a view on the folder.

  2. Rule 2 · No check-in

    No account, ever.

    Download, open, send. Fully usable offline, no connection to our servers.

  3. Rule 3 · Clearance from the controller

    Writing to production only with approval.

    As an air traffic controller you give clearance for exactly one flight. An AI agent that wants to write to production waits for yours – and never sees a secret value.

  4. Rule 4 · Weight and balance

    Performance has a budget.

    Before every flight you calculate, you do not guess. Cold start, memory, large responses and keystrokes have limits, and missing one breaks the build.

  5. Rule 5 · Honest about the limits

    What is free stays free.

    The core is licensed under Apache 2.0 and has no paid features. And what is not built yet is shown here as “In the works”, not as a promise.

Behind RequestTailor is the CloudDNA team: 24 people from southern Burgenland who have been building and testing interfaces for years – to SAP and far beyond. If you want to try RequestTailor on your own system, write to us.

“Your repo. Your requests.” Not a slogan – it is how we work ourselves.

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

    Requests as OpenCollection YAML, one file per request ↑Product · RequestTailor core repository, CLAUDE.md (Produktprinzip „Dateien sind die Wahrheit“), crates/rt-format, website/docs/collections · checked on 2026-11-22

  2. 2

    One Rust core for desktop, web, CLI and MCP ↑Product · RequestTailor core repository, CLAUDE.md (Produktprinzip „Parität über alle Oberflächen“, Technische Leitplanken) · checked on 2026-11-22

  3. 3

    Byte-identical round trip, 86 Bruno collections ↑Product · RequestTailor core repository, testdata/collections/bruno, crates/rt-format (Round-Trip-Tests) · checked on 2026-11-22

  4. 4

    No account, offline, no connection to CloudDNA ↑Product · RequestTailor core repository, CLAUDE.md (Produktprinzipien 2 und 7), website/docs/privacy · checked on 2026-11-22

  5. 5

    MCP server rt mcp with rules per environment ↑Product · RequestTailor core repository, crates/rt-cli/src/mcp, crates/rt-cli/README.md (MCP server), crates/rt-cli/tests/gate_w8.rs · checked on 2026-11-22

  6. 6

    Performance budgets as release gates ↑Product · RequestTailor core repository, perf/budgets.toml, perf/README.md · checked on 2026-11-22

  7. 7

    Core under Apache 2.0, without paid features ↑Product · RequestTailor core repository, CLAUDE.md (Lizenzgrenze), LICENSE, TRADEMARKS.md · checked on 2026-11-22

  8. 8

    Free, Pro, Team and Enterprise editions (concept) ↑Product · RequestTailor product concept (internal), section “Editions and prices” · checked on 2026-11-22

Frequently asked

Questions about the story.

Who is behind RequestTailor?
CloudDNA GmbH from Loipersdorf in southern Burgenland, founded by Martin Koch – former airline pilot and air traffic controller, in SAP integration since 2006 and SAP Champion. With 24 people, CloudDNA builds a family of software, the Tailors.
Why is Free free of charge and open source?
Because an API client that keeps requests as files in the repo only deserves trust if you can use it without an account or a paywall and read its code. The core is licensed under Apache 2.0. Later, only what needs servers and operations will be paid for: sync, real time, a vault, SSO.
What does “Wir bauen das” mean?
CloudDNA is turning from a service provider (“We deliver”) into a product builder: developers work as forward deployed engineers directly with the customer and, as product owners, are responsible for the product beyond the project.
What are the Tailors?
A family of software by CloudDNA, most siblings on a shared foundation, the Tailor-Plattform: among others for APIs (RequestTailor), SAP Fiori and UI5 (FrontTailor) and SAP Cloud Integration (iFlowTailor).

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

Contact

Requests in the repo instead of an account? Talk to us.

Free is free and stays free. For an early copy, for Enterprise, for the OData plugin on your SAP system or for a wish for Pro and Team: write to me. I reply within one working day, personally.

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