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 →
Manifesto

Sources.

“Blazing fast.” “Enterprise-ready.” “AI-powered.” – developer tools promise a lot and prove little. For an API client whose principle is “files are the truth”, that would be embarrassing. So every statement on this website has a source: product statements point to the file in the core repository as of main branch of the core as of 22 November 2026, before the first release (waves 1 to 8), the vendor to a link and a date. The core repository is still private and will be published with the first release; until then the sources are paths without a link.

All siblings of the Tailor family share the habit. For us it also means: what is planned is shown as planned – Pro, Team and Enterprise carry “In the works”.

Product

  1. One Rust core for desktop, web, CLI and MCP

    RequestTailor is an API client with a Rust core that runs natively, as WebAssembly in the browser, as the rt command line and as an MCP server. Desktop, web, CLI and MCP use the same core; a conformance suite runs identically against the native and the WebAssembly core. Every commit builds macOS, Windows, Linux and wasm32 and checks the iOS compilation.

    RequestTailor core repository, CLAUDE.md (Produktprinzip „Parität über alle Oberflächen“, Technische Leitplanken) · checked on 2026-11-22

  2. Core under Apache 2.0, without paid features

    The public core is licensed under the Apache License 2.0 and on its own builds the complete Free edition. It contains no licence check, no placeholders for Pro features and no login dialog; Pro code lives in a separate repository. No dependency with a copyleft licence; cargo-deny and an npm licence check enforce this. The name and logo “RequestTailor” are not covered by Apache.

    RequestTailor core repository, CLAUDE.md (Lizenzgrenze), LICENSE, TRADEMARKS.md · checked on 2026-11-22

  3. No account, offline, no connection to CloudDNA

    No account, ever: download, open, send. Fully functional offline. The Free edition opens no connection to CloudDNA servers, does not check for updates and sends no telemetry; telemetry would only ever come with consent. Fairness guarantee: what is free once never moves behind a paywall.

    RequestTailor core repository, CLAUDE.md (Produktprinzipien 2 und 7), website/docs/privacy · checked on 2026-11-22

  4. Performance budgets as release gates

    App cold start under 500 ms (median from process start to the first usable frame, release build), idle memory under 150 MB (app plus webview processes as the operating system counts them), a 100 MB response renders and scrolls without stutter (p95 frame interval at most 20 ms), sending in at most two keystrokes from app start. The budgets are measured automatically on macOS, Linux and Windows; exceeding one or missing a measurement fails the build. Measured for sending: one keystroke (Mod+Enter), because the app reopens the last collection and the last request.

    RequestTailor core repository, perf/budgets.toml, perf/README.md · checked on 2026-11-22

  5. macOS app, web app, rt for macOS and Linux

    The desktop app is available for macOS (signed and notarised), the web app runs in the browser as WebAssembly, the rt command line for macOS and Linux (x86_64 and aarch64), plus a Docker image and a GitHub Action. There are no desktop installers for Windows and Linux; use the web app or rt there. Not included yet: a hosted web app and automatic updates. Status: before the first release.

    RequestTailor core repository, launch/RELEASE-NOTES.md (Entwurf für das erste Release), crates/rt-cli/README.md · checked on 2026-11-22

  6. Requests as OpenCollection YAML, one file per request

    A request is a readable text file in the OpenCollection format (YAML). Diffs work without special tools; the app is only a view of the folder. Only the rt-format module knows the format; own data goes into extensions of opencollection.yml or into companion files.

    RequestTailor core repository, CLAUDE.md (Produktprinzip „Dateien sind die Wahrheit“), crates/rt-format, website/docs/collections · checked on 2026-11-22

  7. Byte-identical round trip, 86 Bruno collections

    Reading and writing gives byte-identical files. This is tested on a corpus of 86 Bruno collections (MIT licence) kept unchanged in the repository. Writers leave unchanged parts of a file byte-identical; what a writer cannot do is refused by the read-back check.

    RequestTailor core repository, testdata/collections/bruno, crates/rt-format (Round-Trip-Tests) · checked on 2026-11-22

  8. Git in the app, without a staging area

    Git without a staging area: commit with a message and chosen files, branches, pull and push, resolving conflicts. Anything that changes working files (checkout, pull, resolve) refuses while there are unsaved changes. Natively via gitoxide, in the browser via isomorphic-git, with network access there through the rt agent companion.

    RequestTailor core repository, crates/rt-git (gitoxide), CLAUDE.md (App, Welle 4) · checked on 2026-11-22

  9. Secret scanner before every commit

    A commit with plain-text credentials fails with a message naming file and line. rt scan checks the same in pipelines and Git hooks. A finding can only be suppressed line by line with rt-scan:allow or rt-scan:allow-next-line.

    RequestTailor core repository, crates/rt-app (secret_scan), crates/rt-cli/README.md (rt scan) · checked on 2026-11-22

  10. Import from six sources with a loss report

    Importers for Postman, Insomnia, OpenAPI 3.0 to 3.2, cURL, HAR and .http files, one module per source. Every import delivers a loss report: what could not be carried over, with the request it was in. Scripts are taken over unchanged; the report names unsupported script APIs.

    RequestTailor core repository, crates/rt-format/src/import, testdata/import/SOURCES.md · checked on 2026-11-22

  11. Variables in six layers with origin

    Layered variables with origin, precedence as in Bruno: global < collection < environment < folder < request < runtime. For every value you can see which layer it comes from.

    RequestTailor core repository, crates/rt-core (vars::Scope), website/docs/environments · checked on 2026-11-22

  12. Secrets in the keychain and from external vaults

    Secret values are never in collection files: natively in the operating system’s keychain (macOS Keychain, Windows Credential Manager, Secret Service on Linux), on the web encrypted in browser storage; the repository holds only the reference. External secrets from 1Password, HashiCorp Vault, AWS Secrets Manager, Azure Key Vault and Google Secret Manager via the providers’ command lines; values only in memory, masked in reports.

    RequestTailor core repository, CLAUDE.md (Produktprinzip 3), crates/rt-cli/README.md (externe Secrets), website/docs/environments · checked on 2026-11-22

  13. OAuth 2.0, AWS SigV4, client certificates

    Basic, bearer and API key; OAuth 2.0 with client credentials, password, authorization code with PKCE, device code and SAML 2.0 bearer (implicit read-only); AWS Signature Version 4, checked against AWS’s test vectors; client certificates per collection and environment (native only). OAuth tokens are kept natively in the keychain; the user interface only sees expiry and scope.

    RequestTailor core repository, crates/rt-core (model::auth), crates/rt-format/src/auth, testdata/sigv4 · checked on 2026-11-22

  14. Large responses stay in the core

    Large responses stay on the Rust side in a response store; the user interface only fetches the visible lines. That is how a 100 MB response renders and scrolls within budget. Bodies are pretty-printed and can be folded.

    RequestTailor core repository, CLAUDE.md (App, ResponseStore), perf/README.md · checked on 2026-11-22

  15. Script sandbox: QuickJS in WebAssembly

    Pre-request scripts, post-response scripts and tests run in QuickJS, executed as WebAssembly in wasmi – the same engine natively, in the browser and in the CLI. No file or network access except through the request API. Scripts only run in collections you trust (asked once per collection and device). Variable changes stay in the session; scripts never write files.

    RequestTailor core repository, crates/rt-script (api.d.ts, README) · checked on 2026-11-22

  16. Shims for bru.*, pm.* and insomnia

    Bruno, Postman and Insomnia scripts keep running through shims on the one script API. The coverage table lists per API whether it is supported, partial or unsupported; an unsupported API throws a clear error instead of a meaningless TypeError. On import every script stays unchanged.

    RequestTailor core repository, crates/rt-script/SHIM-COVERAGE.md · checked on 2026-11-22

  17. Runner, rt run, JUnit and JSON, exit code 4

    Assertions and variable actions without JavaScript; one runner for app, web and rt run. rt run writes JUnit and JSON reports and exits with code 4 when a test or an assertion fails (0 success, 1 transport error, 2 usage error, 3 request could not be prepared).

    RequestTailor core repository, crates/rt-core (runner, assert), crates/rt-cli/README.md (Exit codes) · checked on 2026-11-22

  18. rt mock and rt docs

    rt mock answers requests with the examples saved with the requests: method and path pick the route, query, headers and body pick among several examples; loopback only by default. rt docs writes a static HTML page of a collection, without scripts and without third-party requests; secret values never appear.

    RequestTailor core repository, crates/rt-cli/src/mock.rs und docs.rs, launch/wave8/RELEASE-NOTES.md · checked on 2026-11-22

  19. gRPC, WebSocket, SSE and GraphQL

    gRPC unary and streaming from .proto files or via server reflection, messages as JSON, metadata as headers; WebSocket with saved messages and a session log of every frame; server-sent events as a live list; GraphQL as a body with query and variables. Sessions run in the core on the desktop and through the companion in the web app; secret values are masked in session logs.

    RequestTailor core repository, crates/rt-core (stream), crates/rt-grpc, launch/wave8/RELEASE-NOTES.md · checked on 2026-11-22

  20. MCP server rt mcp with rules per environment

    rt mcp exposes a collection over stdio as tools: list_requests, get_request, list_environments, send_request, run_folder. Each environment has a rule (nothing, read, write) and a production flag; the default is read-only. Writing requests against production wait for approval in the app’s banner or with rt approve or rt deny; rt approvals lists what is waiting. Every call is written to a local audit log. Agents never see secret values, only their names; an automated test covers the whole path.

    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

  21. MCP client with saved tests

    Test MCP servers: stdio on desktop and CLI, Streamable HTTP everywhere. Tool calls can be saved as tests next to the collection (companion files *.mcp.yaml); rt mcp-test runs them in a pipeline.

    RequestTailor core repository, crates/rt-app (mcp_client), crates/rt-cli/src/mcp_test.rs · checked on 2026-11-22

  22. AI assistant, off until configured

    No provider hard-wired: your own Anthropic key or an OpenAI-compatible endpoint, also a local model. Off until you set it up. All secret values are removed before every call; answers are suggestions that are never saved on their own. The assistant creates requests, explains responses and suggests tests.

    RequestTailor core repository, crates/rt-app (ai), website/docs/privacy · checked on 2026-11-22

  23. Plugins only as WebAssembly, with permissions

    A plugin is a .wasm file with an embedded manifest; no native code. It runs in the wasmi interpreter with a fresh instance per call, a fuel limit and 64 MiB of memory. You see its permissions (network with hosts, storage, variables) before installing; plugins never see secret values. The plugin API is public and versioned.

    RequestTailor core repository, crates/rt-plugin/API.md, plugins/README.md · checked on 2026-11-22

  24. OData plugin for S/4HANA, CAP and RAP

    The OData plugin reads $metadata and shows entities, properties and navigations; a query builder assembles $filter, $select, $expand, $orderby, $top, $skip and $count. Writing requests fetch the CSRF token themselves, set If-Match from the ETag, bundle into $batch and know drafts. Landscapes DEV, QAS and PRD with sap-client become environments. Tested against an own OData test service with synthetic data (S/4 V2, V4 RAP, CAP V4 and V2). SAP knowledge lives only in the plugin, not in the core; if you don’t choose it at first start, you see no SAP.

    RequestTailor core repository, plugins/odata, website/sap, website/docs/odata · checked on 2026-11-22

  25. The rt agent companion for the web app

    So that the web app can send requests without CORS limits, open gRPC and WebSocket sessions, use Git over the network and fetch external secrets, rt agent runs locally: loopback only, with Host and Origin checks, pairing via a one-time code, token only in memory. It hands out external secrets only with --allow-secrets.

    RequestTailor core repository, crates/rt-cli/src/agent, crates/rt-cli/README.md (Sicherheitsmodell) · checked on 2026-11-22

  26. Free, Pro, Team and Enterprise editions (concept)

    Free: everything one person or a Git team can do locally – all protocols, Git, scripts, runner, MCP, AI with your own key, OData basics. Pro: end-to-end-encrypted sync between your own devices, a managed AI quota, SAP comfort (importing BTP service keys, destinations as environments). Team: real-time workspaces, roles, a shared vault. Enterprise: SSO and SCIM, audit export, policies, self-hosting, a licence file for air-gapped use. Pro, Team and Enterprise are planned and not built yet. The product owner confirmed the prices on 22 Nov 2026; they are on the editions page.

    RequestTailor product concept (internal), section “Editions and prices” · checked on 2026-11-22

  27. Screenshots from the web app with sample data

    The screenshots show the web app with the user interface’s mock backend and sample collections. All data in them is made up; desktop and web share the same user interface.

    RequestTailor core repository, apps/web (Mock-Backend ?backend=mock), examples · checked on 2026-11-22

Vendor

  1. CloudDNA GmbH – SAP Silver Partner

    CloudDNA describes itself as an SAP BTP partner from Austria for the DACH region and an SAP Silver Partner; it supports SAP projects in Austria, Germany and Switzerland, in industry, retail and the public sector. Focus areas according to its website: integration, architecture and clean core, Fiori and UX, full-stack development with ABAP RAP and CAP, agility and DevOps, and training. Martin Koch is listed there as founder & managing director and SAP Champion.

    clouddna.at, start page and team · checked on 2026-11-05

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

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

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.