Transmute - SWIFT MT to ISO 20022, both ways, nothing stored or logged

Hi Product Hunt. My company builds Transmute, an API that converts SWIFT MT messages to and from ISO 20022. Banks are in the middle of a multi-year migration from the old MT text format to ISO 20022 XML, which means a lot of software now has to speak both at once. The tools that existed were either heavyweight middleware you buy through a sales cycle, or libraries that had gone quiet years ago. They also typically had very low free tiers, which we feel have the most generous free tier available. Three decisions shaped the build: Nothing is stored. Message bodies are processed in request-scoped memory and are never persisted and never logged. The database keeps metadata only: type, size, duration, status, warning counts. A finished request leaves exactly one row behind. This is a structural property of the code, not a config flag, which makes the compliance conversation with a bank much shorter than it usually is. Nothing is dropped silently. Format conversion is lossy in both directions. Every lossy or assumed step comes back as a deterministic, severity-graded warning in the response, so you can see what the conversion had to decide instead of finding out at reconciliation time. Mappings are data, not code. Field mappings live in declarative tables rather than per-field branching, so the annual Standards Release lands as a data update instead of a rewrite. Today it covers 81 directed conversion pairs across 14 MT types and 10 ISO 20022 families, plus normalize-to-JSON and OFX/QFX/QBO/CSV output for accounting tools. There is a free tier at 1,000 conversions a month, no card, and signup is an email link. Happy to answer anything about the mapping engine, the statelessness guarantee, or what conversions you need that aren't there yet. That last one genuinely drives what gets built next. "SWIFT" is a trademark of S.W.I.F.T. SCRL. Transmute converts SWIFT MT messages; it is not affiliated with, endorsed by, or certified by SWIFT.